Is your site sending Consent Mode v2 signals? Check free — right here.

Q: Does Consent Mode v2 apply outside the EU?

The strict requirement applies to users in the EEA plus the UK and Switzerland, but the same implementation is global — the signals travel with your tags wherever visitors come from. Implementing once covers every market.

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.

Try:

Compliance score

–%

See current Pro tools — $79/year per website →

What the check looks at

The scan analyses your live page HTML for static markers associated with Consent Mode v2:

Static signal	Why it matters
Consent default-state markers	Look for `default` consent settings associated with `ad_storage` and `analytics_storage`.
Consent update markers	Look for an `update` mechanism that should run when a visitor chooses.
ad_user_data & ad_personalization markers	Detect the two v2-only parameter names in the served source.
URL passthrough markers	Detect `url_passthrough` and ads-data-redaction references.
Tracker and consent-platform markers	Compare known tracker strings with consent-platform signatures in the same HTML.

Important: source markers do not prove tag order, network blocking, consent choices or runtime data handling. Test those behaviours separately in browser developer tools.

Fair warning: passing today doesn't mean passing tomorrow. Tag managers change, scripts get added, CMP settings drift. The free scanner supports manual rechecking; hosted daily monitoring and pass-to-fail email alerts are planned, not included in Pro.

How to fix a failing result

Set the default state early. Call gtag('consent', 'default', {...}) before any other gtag or GTM tag fires — ideally inline in the <head>.
Include the two v2 fields. ad_user_data and ad_personalization must appear in both the default and update calls. Most broken setups simply predate March 2024.
Wire your CMP to consent mode. Cookiebot, Usercentrics, Complianz and most major CMPs have a Consent Mode integration — enable it rather than pushing consent yourself.
Verify after every tag change. This is the step everyone skips, and exactly why monitoring exists.

Full walkthrough: the EU cookie consent guide 2026 covers Consent Mode v2 implementation step by step.

Frequently asked questions

What is Google Consent Mode v2?

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.

Does Consent Mode v2 apply outside the EU?

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.

Can I check Consent Mode v2 without installing anything?

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.

Does this work on Shopify, Wix, Squarespace or Webflow?

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.