Consent & cookie banner

Marketing

When you use ad tracking, your booking page shows a cookie consent banner so visitors can choose whether to be tracked. Their choice controls all of Preb's conversion tracking for that visitor — the in-browser tags and the server-side conversion events. This page explains what consent does, when the banner appears, and how to manage it.

Consent & tracking

Preb tracks conversions in two layers, and both are switched by the visitor's consent:

  • In-browser tracking — the Meta Pixel and your Google Tag Manager container — loads only for visitors who accept marketing cookies.
  • Server-side tracking — the Meta Conversions API and Google conversion events — also fires only for visitors who accepted. The visitor's consent choice is recorded with their lead and booking, so later funnel events (a closed sale, a cancellation) are only reported for people who said yes. When Preb sends a conversion to Google, the visitor's consent choice is attached to that upload, so Google knows it was permitted.

A visitor who declines — or never answers — sends nothing to Meta or Google, in any form. This is what keeps your tracking lawful in the EU: German courts have awarded booking-page visitors four-figure damages for tracking without consent, so "no consent, no signal" protects you, not just them.

Why server events still outnumber browser events

Among visitors who consent, the in-browser Pixel can still be lost to ad blockers and browser tracking protection — the server-side events aren't. So Meta's Events Manager usually shows more server events than browser events. That gap is expected; Meta deduplicates the overlap.

When the banner appears

The banner is powered by a built-in consent management platform (Termly), and it appears only where it has a job to do:

  • Any tracking configured — a Meta pixel or access token, a Google Analytics measurement ID, a Tag Manager container, or a Google Ads connection: your booking pages show the banner, because visitor consent is what allows that tracking to run.
  • No tracking configured: your booking pages show no banner at all. Nothing consent-requiring runs on them, so visitors book without any cookie prompt — a clean, friction-free page.

When a visitor accepts the marketing / advertising category, Preb switches on tracking for them; if they decline, everything stays off.

Embedded on your own site: no Preb banner

Inside an embedded widget Preb never shows this banner — your site's own cookie banner owns the decision and hands it to the widget. See Consent inside embeds.

Showing or suppressing it

When ad tracking is configured, the banner shows on your hosted booking pages. You can hide it for a specific event type if you collect consent another way. (This setting applies to hosted pages only — an embedded widget never shows the banner.)

Open the event type

Go to Event types and open the one you want to change.

Find Privacy & Compliance

Open the Privacy & Compliance settings for that event.

Turn on “Hide cookie banner”

Toggle Hide cookie banner to remove the banner from that booking page.

Hiding the banner is your responsibility

Hiding the cookie banner may affect your compliance with privacy regulations. Only turn it off if consent is genuinely collected somewhere else. When the banner is hidden, visitors on that page have no way to grant consent — so no tracking runs for them at all, in-browser or server-side.

Landing page first, then the hosted booking page

A visitor who accepted cookies on your website has not consented on app.preb.co — that is a different site, and browsers keep the two decisions apart. So when your ad sends people to your landing page and a button opens your hosted Preb booking page, they see Preb's banner there and have to decide again. Two things follow:

  • Do not hide the banner just to avoid the second prompt. Hidden banner means no consent, and no consent means nothing reaches Meta or Google for that visitor — the booking is still made, but the ad platforms never learn about it.
  • Hand the consent over. The landing-page snippet from your event type's Embed → Anzeigen-Conversions erfassen section reads your own banner (Termly, Cookiebot, or a window.prebMarketingConsent = true flag your banner sets) and, when marketing consent exists, appends preb_consent=granted to your booking links. The hosted booking page then records that consent and does not ask again. Only a grant ever travels; your cookie tool remains the record of consent.
  • Embed the widget instead when you can. Inside an embedded widget Preb shows no banner; your own cookie banner hands the decision to the widget, so the visitor decides exactly once. See Consent inside embeds.

How consent gates tracking

Here's the full chain, end to end:

  1. A visitor lands on your booking page. If ad tracking is configured, the consent banner appears (unless you hid it for that event type).
  2. They accept or decline the marketing / advertising category.
  3. If they accept, Preb loads the in-browser Meta Pixel and your Google Tag Manager container, and their leads, bookings, and later funnel events are reported to Meta and Google server-side.
  4. If they decline (or ignore the banner), nothing fires — no browser tags, no server events.

So consent is the on/off switch for all conversion tracking. To set up the tags themselves, see Meta Pixel & Conversions API and Google Tag Manager.