Design a cookie banner. Check it before you build it.
Configure layout, theme, consent granularity and copy across four regulatory regimes — and see both the visitor experience and the compliance consequence in real time.
No sign-up. If you preview your own site, we read its home page once and keep nothing.
See the banner on your own website
We read your home page once, find your trackers and show what the banner would block. Nothing is stored.
Customise
Jurisdiction — changes defaults, required controls and copy.
Live on the page
Sample trackers. Preview your own site to see yours.
- Firing
Google Tag Manager
necessary
- Held until consent
Google Analytics
analytics
- Held until consent
Hotjar
analytics
- Held until consent
Meta Pixel
marketing
- Held until consent
Google Ads
marketing
- Held until consent
Intercom
functional
1 of 6 firing
Google Consent Mode v2
- ad_storage: denied
- ad_user_data: denied
- ad_personalization: denied
- analytics_storage: denied
- functionality_storage: denied
- personalization_storage: denied
- security_storage: granted
You just designed it. We'll make it work.
A banner is the easy part. We block every tag until people say yes, wire Google Consent Mode v2 and keep proof of each choice. Tell us about your site and we'll set it up with you.
Four regimes, one surface
Switch between GDPR, CCPA, DPDP and LGPD and watch the default state, required controls and copy change with the jurisdiction.
Live compliance feedback
Every configuration is checked as you edit, so a design that would fail an audit tells you before it reaches a sprint.
Real consent records
Interact with the preview and see the exact audit record the interaction would produce — including the case where nothing is recorded at all.
Questions about the playground
It is the same experience model — layouts, granularity, regional defaults and the resulting consent record — running in your browser. Your configuration never leaves it; a website address you preview is read once and not stored. The playground sets no cookies of its own; a site you preview loads in a frame as it would for any visitor.
Because the requirement changes. Opt-in regimes such as GDPR and DPDP require refusing to be as easy as accepting, so the reject action is promoted to a full button. CCPA is a notice-and-opt-out regime, where a clear "Do Not Sell or Share" route is what matters.
Not from the playground — it keeps nothing, which is the point: no account and no storage. It is a place to settle layout, granularity and copy before implementation; the same choices become the configuration ConsentCenter Cookie Consent is initialised with once your property is onboarded.
GPC is handled by the runtime rather than the banner design, because it must be honoured before the banner renders. The playground focuses on the experience layer; GPC support is built into ConsentCenter Cookie Consent itself.
Ship the banner you just designed
ConsentCenter Cookie Consent adds the parts a playground can't show: continuous scanning, real script blocking, GPC handling and an audit trail behind every choice.