Cookie Consent
Your public site, your landing pages and the attendee app show a cookie banner to every new visitor. The visitor's choice decides whether analytics and advertising tools may set cookies and use the visit. This page explains what visitors see, what each category allows, and what the banner doesn't govern.
Access: the banner has no settings in the dashboard. Admins decide which tools it manages in Settings → Integrations.
What visitors see
On a visitor's first page view, a dialog covers the page until they choose. Like the other attendee-facing pages, it's in Romanian:
- The headline Ținem la confidențialitatea ta (We care about your privacy) and a short text: cookies help the site understand how it can help the visitor and give them a better experience, and the visitor chooses what to allow.
- Acceptă toate (Accept all) allows both optional categories.
- Doar necesare (Only necessary) refuses both.
- Setează preferințe (Set preferences) opens Preferințele tale (Your preferences), with one switch per category and the buttons Salvează selecția (Save selection) and Acceptă toate.
You can't change the banner's text or language, and it doesn't link to your cookie policy.
The banner appears on the public site (webinars.yourdomain.com), on landing pages and in the attendee app (live.yourdomain.com). It doesn't appear on the live watch page: there the banner and the cookie settings button are hidden. A visitor who opens a watch page directly isn't asked, and only strictly necessary items load until they choose somewhere else. The dashboard doesn't show the banner.
The categories
| Category | What it covers |
|---|---|
| Strict necesare (Strictly necessary), marked Mereu active (Always active) | Always on. The platform's own browser storage (the saved choice itself, the visitor's registration and sign-in for live features, campaign parameters for attribution), plus the items listed in Loaded before any choice. |
| Analiză & Performanță (Analytics & Performance) | Microsoft Clarity, and Google's analytics signal for tags in your Google Tag Manager container. |
| Publicitate & Marketing (Advertising & Marketing) | Lets the Meta Pixel and TikTok Pixel set their advertising cookies (such as _fbp, _fbc and _ttp) and use the visit for ad targeting, and grants Google's advertising signals. |
Visitors can allow analytics without advertising, or the other way round.
What loads under each category
The banner manages four tools. Each one loads only when an admin has turned on its integration in Integrations:
| Tool (integration card) | When it loads | What the choice changes |
|---|---|---|
| Google Tag Manager container | On every page, as strictly necessary | The Consent Mode signals the container receives (see below) |
| Meta Pixel (Meta / Facebook Ads) | On every page, as strictly necessary, in a consent-withheld mode | Publicitate & Marketing switches it to full mode |
| TikTok Pixel (TikTok Pixel + Events API) | On every page, as strictly necessary, in a consent-withheld mode | Publicitate & Marketing switches it to full mode |
| Microsoft Clarity | Only after the visitor allows Analiză & Performanță, and only on the public site and landing pages. It never runs in the attendee app. | Whether it loads at all |
Google Analytics, Google Ads and similar tools aren't platform integrations. They run only if you add them as tags inside your own Google Tag Manager container.
Loaded before any choice
- Meta Pixel and TikTok Pixel. Each loads on every page and reports a page view before the visitor chooses, and also after they choose Doar necesare. Until the visitor accepts Publicitate & Marketing, they run in a consent-withheld mode meant to stop them from setting their advertising cookies. Meta and TikTok still receive the visitor's IP address, browser details and the page address.
- Google Tag Manager container. Loads on every page with all Consent Mode signals set to denied until the visitor chooses. What happens next depends on the tags inside your container.
Google Consent Mode v2
When Google Tag Manager is set up, the platform sets Google's four Consent Mode signals to denied before your container loads, and asks Google's tags to wait up to half a second for a saved choice. It then updates the signals when the visitor chooses, and on every later page view based on the saved choice:
| Visitor allows | Signals set to granted |
|---|---|
| Analiză & Performanță | analytics_storage |
| Publicitate & Marketing | ad_storage, ad_user_data, ad_personalization |
Google's own tags in your container adjust to these signals. Any other tag you add to the container needs its own consent condition, which you set up in Google Tag Manager. The Meta Pixel, TikTok Pixel and Microsoft Clarity don't go through your container and don't read these signals; the banner switches them directly.
Without Google Tag Manager, no Consent Mode signals are sent.
Microsoft Clarity consent signal
Clarity loads only after the visitor allows Analiză & Performanță. As soon as it loads, it sends Microsoft an explicit consent signal, which Microsoft expects for visitors in the EEA, the UK and Switzerland. If the visitor later turns analytics off in the preferences, the banner tells Clarity that consent was withdrawn before it reloads the page.
One choice across your subdomains
The choice is saved in a cookie named rx_cookie_consent on your main domain (for example .yourdomain.com). The same choice applies on webinars.yourdomain.com, live.yourdomain.com and landing pages on your domain, so visitors aren't asked again on each one.
- A saved choice lasts 12 months (360 days). After that, or if the visitor clears their cookies, the banner appears again. It also appears again if the platform updates the banner version.
- The cookie holds only the choices, the time they were made and the banner version.
- The choice is stored only in the visitor's browser and isn't recorded in the contact's consent history, so the dashboard has no record of who accepted or refused cookies. The one related value the platform keeps is a flag on each registration saying whether advertising cookies were accepted at the moment the person registered. Nothing uses that flag.
Domains with a two-part ending
The cookie is set on the last two parts of the host name, such as yourdomain.com. On a domain whose ending has two parts, such as example.co.uk, that would be co.uk, which browsers refuse. The choice then isn't remembered and the banner keeps coming back. Talk to support before launching on such a domain.
Changing a choice later
After the first choice, a small cookie button sits on the left edge of the screen on every page that shows the banner, except the watch page. Its label, shown on hover, is Setări cookie-uri (Cookie settings). It opens the preferences with the visitor's current choices.
The Politica de cookies (Cookie policy) and Cookies links in the footers open your cookie policy page. They don't reopen the choices.
When a visitor saves the preferences after turning off a category that was on, the page reloads. Before the reload, Clarity is told consent was withdrawn, and the Meta and TikTok pixels return to their consent-withheld mode. Cookies these tools already set stay in the browser until they expire or the visitor deletes them.
What the banner doesn't control
- Server-side conversion events. With Meta's Conversions API set up in the Meta integration, the platform sends Meta a server-side page view each time a funnel page loads. With Meta's Conversions API or TikTok's Events API set up, it sends a conversion event for each registration. These are sent on the basis of legitimate interest, whatever the visitor chose in the banner. For a specific person, restricting processing stops the registration events; page views can't be stopped for one person.
- Landing-page visit counting. Funnel pages load a first-party counting pixel that records unique visitors with a pseudonymous identifier derived from the visitor's IP address and browser, on every visit.
- Turnstile bot protection. If you've set it up, pages with a funnel form load it before any choice.
- The video player. When a session streams from YouTube, the watch page embeds the regular YouTube player, which loads as soon as the page opens.
- Anything in a page's own HTML. Images, fonts, embedded frames and other resources a landing page loads from other services load before any choice. Google Fonts are the exception: RestartiX serves them from the page's own domain, so the visitor's browser never contacts Google for them.
- Tracking code pasted into a page. When you save a page, the editor removes only some tracking code: script tags that load from
googletagmanager.comorconnect.facebook.net, and<noscript>tracking images from Meta, Google or TikTok. Inline tracking code, such as the standard Meta Pixel, Google Tag Manager or TikTok Pixel code, stays in the page and runs for every visitor, whatever they chose. Don't paste tracking code into pages; add it through Integrations instead. See Landing Pages. - Behavioral tracking. Whether an attendee's chat messages, poll votes and other live activity are added to their activity history depends on a separate consent given at registration, not on the analytics cookie choice. See GDPR.
Your responsibilities
- Make sure your published cookie policy matches the behavior on this page. Your public site serves a built-in cookie policy at
/politica-cookies, and a template is in Legal documents. - Keep track of which tools you've turned on in Integrations, and of the tags in your Google Tag Manager container.