Is your CMP actually wired to Consent Mode v2?
Enter your domain. We'll check whether Google Consent Mode v2 is present in your dataLayer, whether the new ad_user_data and ad_personalization signals are set, and whether tags respect them.
Free · no login · we load your site in a real browser and record what fires before consent.
Most checkers read the page. Ours watches it.
- We inspect the live dataLayer for Consent Mode default and update states — not just whether a banner exists.
- We check for the two signals Google made mandatory: ad_user_data and ad_personalization. Missing them means shrinking audiences and blind bidding.
- We confirm whether tags actually defer until consent is granted, or fire regardless.
- In our UK clinic probe, 0 of 8 sites had Consent Mode v2 configured — even the ones with a CMP. This tells you which side you're on.
It's Google's framework for adjusting tag behaviour based on user consent. v2 added two required signals — ad_user_data and ad_personalization — that Google needs to use EEA/UK data for personalised ads and remarketing, and to model the conversions consent hides.
Not necessarily. A banner controls the UI; Consent Mode is the signalling layer underneath it. Many CMPs are installed without ever wiring the Consent Mode default/update states into GTM. That's exactly what this tool detects.
Google falls back to conservative behaviour: fewer conversions counted, smaller remarketing audiences, and Smart Bidding optimising on partial data. We can wire it up properly — see our Consent Mode v2 service.
Found something you don't like?
We fix exactly this — consent enforcement, Consent Mode v2, and server-side tracking. Book a call or start with a scan.