Which parts of Bizzabo require consent under GDPR?

The persistent attribution cookies — bz_visitor (30–90 days) and bz_utm_* series (30 days) — require explicit marketing consent. Session cookies that maintain multi-step registration form state are functionally necessary and qualify for the ePrivacy strictly necessary exemption without consent.

What data does Bizzabo collect through its event registration widget?

Bizzabo collects attendee name, email, job title, company, and ticket selection. For paid events it processes payment details via Stripe-based flows. UTM parameters and referral source are captured in persistent cookies to attribute registrations to marketing campaigns.

How does ConsentStack manage Bizzabo consent for event websites?

ConsentStack splits Bizzabo into two layers. Essential registration session cookies load unconditionally. The marketing attribution cookies — bz_visitor and bz_utm_* — are blocked until the visitor grants marketing consent. This lets ConsentStack protect attendee privacy without breaking the registration flow.

What tracker domains does Bizzabo use?

ConsentStack has catalogued tracker domains for Bizzabo including bizzabo.com. These are the network destinations Bizzabo's scripts contact, which a consent platform blocks until a visitor agrees.

Bizzabo - Event Tracking & Cookie Consent

Back to Vendor Library

Overview

Bizzabo is an enterprise event management and marketing platform designed for large-scale professional conferences, trade shows, summits, and corporate events. It is used by event organizers to manage registration and ticketing, attendee communications, agenda and speaker management, on-site check-in, and post-event analytics. Bizzabo was acquired by Wix in 2022 and operates as its enterprise events division.

Event organizers embed Bizzabo registration widgets and agenda displays on their event websites, driving attendee registrations directly from the event marketing site while tracking campaign effectiveness through built-in attribution analytics.

What This Script Does

Script loading: Bizzabo loads JavaScript from cdn.bizzabo.com and associated CDN endpoints, keyed to the event organizer's account and specific event ID. For full event websites built on Bizzabo's platform, all JavaScript is served from Bizzabo infrastructure.

Registration and ticketing widget:

Renders a multi-step registration form collecting attendee name, email address, job title, company, and ticket type selection
Handles coupon code validation, group registration flows, and waitlist management
Collects payment information for paid ticketing events via integrated Stripe-based payment processing
Sets session cookies on the bizzabo.com domain to maintain registration flow state across multi-step forms

Analytics and attribution cookies:

bz_visitor — First-party persistent cookie, 30–90 days, stores an anonymized visitor identifier to track registration funnel progression and attribute registrations to marketing campaigns
bz_session — First-party session cookie, tracks the current session including pages viewed, registration steps completed, and referral source
bz_utm_[param] — First-party persistent cookies, 30 days, capture UTM campaign parameters (source, medium, campaign, term, content) on first visit to attribute event registrations to specific marketing channels
LocalStorage may cache agenda selections and session personalization state for logged-in attendees

Sponsor and exhibitor tracking:

Bizzabo's exhibitor module may fire tracking pixels when attendees view sponsor-related content, supporting lead capture for event sponsors
If sponsor pixel firing is configured, this constitutes third-party data sharing that extends beyond the organizer's own analytics

Data transmitted: Registration data is sent to api.bizzabo.com. Analytics events stream to Bizzabo's reporting infrastructure. If Salesforce, HubSpot, or Marketo integrations are active, attendee data may be synced to the organizer's CRM immediately upon registration.

Consent & Compliance

Bizzabo is categorized as functional and marketing.

Functional (registration widgets): Session cookies required to maintain multi-step registration form state are functionally necessary for the event registration service and may qualify for the ePrivacy strictly necessary exemption.
Marketing (attribution tracking): The persistent visitor identifier (bz_visitor) and UTM capture cookies (bz_utm_*) are marketing functions requiring explicit consent under GDPR/ePrivacy. These are not necessary for the registration to succeed.
GDPR: Attendee registration data (name, email, employer) constitutes personal data. The organizer is the data controller; Bizzabo operates as a data processor. A DPA should be executed. Sharing attendee data with event sponsors requires a separate legal basis, typically attendee consent obtained at registration.
CCPA/CPRA: If registration data is shared with sponsors as part of a paid sponsorship arrangement, this may constitute a sale requiring disclosure and opt-out rights.

Should You Block This Without Consent?

Conditional. The core registration form session cookies are functionally necessary and should not be blocked. However, the persistent attribution cookies (bz_visitor, bz_utm_*) require consent under GDPR/ePrivacy and should be suppressed until marketing consent is granted. Configure your CMP to allow essential Bizzabo session cookies while blocking the analytics and attribution cookie initialization.

Is Bizzabo GDPR compliant?

Bizzabo typically loads functional and marketing trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Bizzabo can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Bizzabo, not on Bizzabo itself.

Visit website