Consent Mode v2 Live Validator
Scan any page for Google Consent Mode v2 — default-denied posture for EEA/UK, whether all four signals are present, and a recognised consent banner.
How to use
Enter a page address
Any public page that loads the Google tag or Google Tag Manager.
We read the served source
We check for the Consent Mode v2 default call, all four signal keys, and a recognised consent banner.
Get a plain-English readout
Default-denied posture, which signals are missing, and a best-effort Basic vs Advanced read.
Automated estimate, not a formal audit. This reads the code your page serves at page-load — it cannot see the dataLayer after a real banner interaction, and if your CMP injects Consent Mode via a separate loaded script, some checks may under-report. Treat a green light as "nothing obviously broken in the served source", then confirm live in Tag Assistant.
What we check
- The Consent Mode v2 default call — whether it is present and defaults to denied before a visitor makes a choice.
- All four Consent Mode v2 signal keys:
ad_storage,ad_user_data,ad_personalizationandanalytics_storage. - Whether a recognised consent banner is present on the page at all.
- A best-effort read on Basic vs. Advanced Consent Mode implementation, from the served HTML alone.
- Reads only the code served at page-load — it cannot see the dataLayer after a real banner interaction, and CMPs that inject Consent Mode via a separately loaded script may under-report. Treat a green result as a starting point, then confirm live in Tag Assistant.
Related tools
- CMP Detector & Cookie Banner Grader — Grade the banner itself — which platform, and the manual checks this validator cannot automate
- Enhanced Conversions Readiness Checker — Consent Mode v2 default-denied posture is a prerequisite this checker also verifies
- GA4 vs Google Ads Discrepancy Explainer — A broken Consent Mode setup is one of the most common causes of GA4/Ads mismatches
Last updated: 19 August 2026 · Built by the CWA Europe PPC team.