Since March 2024, Google requires Consent Mode v2 for ad personalisation in the EEA. Sites missing it can lose conversions tracking and audience features without any visible error. Paste your URL and find out in seconds — no sign-up, works on every platform.
The scan analyses your live page HTML for the technical markers regulators and Google look for:
| Signal | Why it matters |
|---|---|
| Consent default state | Consent Mode v2 must fire a default consent state (granted or denied) for ad_storage and analytics_storage before any tags load. |
| Consent update mechanism | Your CMP must push an update when the visitor chooses — otherwise Google never learns consent was given. |
| ad_user_data & ad_personalization | The two v2-only parameters. Without them, EEA ad personalisation and audience building stop working. |
| URL passthrough | url_passthrough and ads data redaction preserve measurement accuracy when consent is denied. |
| Trackers before consent | Even perfect Consent Mode code doesn't help if analytics or ad scripts still fire before the visitor consents — the exact pattern behind the SHEIN €150M decision. |
gtag('consent', 'default', {...}) before any other gtag or GTM tag fires — ideally inline in the <head>.ad_user_data and ad_personalization must appear in both the default and update calls. Most broken setups simply predate March 2024.Full walkthrough: the EU cookie consent guide 2026 covers Consent Mode v2 implementation step by step.
A Google requirement, effective March 2024, that sites in the European Economic Area send structured consent signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) before Google Ads and measurement products process user data. Without valid v2 signals, ad personalisation and conversion modelling degrade in the EEA.
The strict requirement applies to users in the EEA (plus the UK and Switzerland under equivalent rules), but the same implementation is global — the signals travel with your tags wherever visitors come from. Implementing once covers every market.
Yes. This checker fetches your public page HTML and detects the v2 consent patterns server-side. Nothing is installed on your site, and no account is needed. For runtime behaviour (what actually fires in a browser), also verify in Google Tag Assistant.
Yes. The checker analyses the served HTML of any public URL, so it works identically on WordPress, Shopify, Wix, Squarespace, Webflow, Next.js or hand-coded sites regardless of which consent platform you use.