eWebinar has a built-in cookie consent system that renders a cookie consent banner alongside its hosted registration pages and alongside widgets that place cookies. This. however, is not a widget you install: it's a team-level setting that's applied wherever eWebinar collects data on behalf of your team.
You can use eWebinar's built-in banner, defer to an external tool you already run, or disable the banner entirely.
Where to configure it
- Open Profile menu → Scripts
- Scroll to the Cookie setting section.
- Pick a Banner mode:
| Mode | What it does |
|---|---|
| Off | No banner. All scripts and pixels fire unconditionally. Use only if your audience isn't subject to GDPR/CCPA/PIPEDA and you understand the legal implications, or if your own site's consent flow already covers eWebinar's cookies.. |
| Show banner | eWebinar renders its own cookie banner at the bottom of registration and watch pages, as well as on widgets that place cookies. You customize the text. Non-essential scripts and tracking pixels only fire after the visitor accepts. |
| External banner | You already use OneTrust, Cookiebot, or a similar tool. Paste their banner snippet in the provided field. eWebinar respects the consent state set by that tool instead of showing its own banner, and waits for your existing consent manager to fire a "consent given" event before placing cookies. |
What's affected by consent
- Custom scripts added under Scripts (e.g. Facebook Pixel, Google Analytics), gated when the visitor declines.
- Third-party chat widgets (Drift, Intercom, Zendesk) that set cookies, gated.
- eWebinar's own essential cookies (wherever eWebinar controls the page: the eWebinar-hosted registration page, the watch room, and widgets), always allowed regardless of consent.
Widgets render their own UI and may collect cookies. On widgets installed inside your own site (for example, a Card embedded in a blog post), the external-banner mode is the right choice because your site's cookie consent banner is the source of truth.
GDPR banner settings apply at the team level, not per webinar. One setting covers every registration page and widget your team publishes.
Related articles