Cookie Consent

When the banner appears

Zitegen adds a cookie-consent banner to your published site as soon as you connect an integration that injects a site-wide script — Google Analytics, Tag Manager, Meta Pixel, a chat widget, and so on. There is no switch to turn it on. It follows from what you have connected.

A site with no such integration gets no banner at all. Connect one and the banner starts appearing on your next publish; disconnect the last one and it stops.

What Accept and Reject do

Until a visitor chooses, the gated scripts are on the page but inert — they are parked inside an element the browser does not execute, so nothing loads and no cookies are set. Choosing Accept brings them to life immediately, without a page reload.

Choosing Reject dismisses the banner and the scripts simply never run. That visitor is not tracked, and any gated chat or booking widget never appears for them.

Either choice is remembered in the visitor's browser and honoured on every later visit, so the banner is shown once, not on every page. Clearing site data resets it.

What is gated, and what isn't

These wait for Accept:

• Google Analytics 4, Google Ads, Google Tag Manager, and Meta Pixel
• Omnisend, and HubSpot's tracking script
• Crisp, Tawk.to, Pipedrive LeadBooster, and the Calendly badge — unless you opt them out, see below

These are never gated, and load for every visitor:

• Your Search Console verification tag — a static tag that identifies the site, with nothing to observe about the visitor
• Anything you place on a page yourself: Stripe and Paddle buttons, an inline Calendly scheduler, a Mailchimp signup form
• Code Snippets — see the warning below

Letting chat and booking load without consent

A chat bubble is a support channel you deliberately added, not a way of measuring visitors — and gating it means the many people who reject or ignore the banner can never reach you. So the four functional widgets each have a Load without cookie consent switch in their dialog: Crisp, Tawk.to, Pipedrive LeadBooster, and the Calendly badge.

Turn one on and that widget loads for everyone straight away, while your analytics stay behind the banner. It is off unless you turn it on, and it is per-integration: switching it on for Tawk.to leaves everything else alone.

These providers do set their own cookies, so whether this fits your privacy policy is your decision to make.

Previews don't show it

Preview and Development deploys carry no third-party scripts at all — a click of your own would otherwise land in your real analytics or your real chat inbox. Because nothing is loaded, no banner is shown either. To see the banner as visitors do, look at a published production site.

Current limits

• The banner cannot be turned off, restyled, or reworded, and it appears for every visitor regardless of where they are.
• There are no per-category choices — it is one Accept or Reject covering everything gated, not separate toggles for analytics and marketing.
• It does not write a privacy policy or a cookie policy for you, and it is not legal advice. What your site needs is between you and your own obligations.