Google measurement
Check whether Google Consent Mode v2 is actually working on your site — all four signals, the right default, and the post-consent update — so your ads and analytics stay compliant and accurate.
No credit card required ? Instant insights
The Google Consent Mode Checker verifies that your gtag configuration respects consent signals and only fires marketing tags with the correct mode applied.
It tracks how consent state flows to Google services so you know whether gtag.js, analytics, and ads respect user choices.
Consent Mode v2 (required by Google since 2024) adds two signals on top of the originals: ad_user_data and ad_personalization, alongside ad_storage and analytics_storage.
The checker confirms all four signals are present and flip to the correct state after the banner — the most common gap is sites still running v1 without the two new v2 signals.
Being configured isn't the same as working. We load your site as a fresh visitor and check the real default state, the banner interaction, and the post-consent update.
Typical failures we surface: the consent default set after tags load, no consent update event from the CMP, or tags firing before consent regardless of the chosen mode.
Google penalizes sites that claim to honor Consent Mode but still leak user identifiers or preload tags without honoring the chosen mode.
Broken Consent Mode v2 also degrades EEA/UK remarketing and conversion modeling — a direct revenue hit, not just a compliance one.
Basic blocks Google tags entirely until consent; Advanced loads them in a cookieless, consent-aware state and sends pinged signals. Each behaves differently before consent.
The checker shows which model your site is running and whether its pre-consent behavior matches that model — so you're not silently sending data you think you're withholding.
We capture the gtag initialization, consent updates, and resulting network hits to Google endpoints, correlating them with the consent banner decisions.
Signals such as gtag('consent', 'update') payloads, cookies, and measurement_id hits are evaluated to ensure the right mode remains in effect — and you can schedule the check so a deploy that breaks it pages you.
How we differ
CookieInspector couples Consent Mode telemetry with actionable alerts so misconfigurations get fixed before a campaign launches.
Run the page through the CookieInspector Google Consent Mode Checker. We load your site in a real browser, capture the gtag('consent', 'default') and ('consent', 'update') calls, and confirm whether ad_storage, analytics_storage, ad_user_data and ad_personalization flip to the right state after the banner — so you can see Consent Mode v2 actually firing, not just configured.
The most common causes are: the gtag consent default is set after tags load instead of before, the CMP isn't sending a consent update event, ad_user_data/ad_personalization (the v2 signals) are missing, or tags fire pre-consent regardless of the chosen mode. The checker shows exactly which signal is missing or mistimed.
Consent Mode v2 is Google's required framework (since 2024) for passing a user's consent choice to Google Ads and Analytics. It adds two signals — ad_user_data and ad_personalization — on top of the original ad_storage and analytics_storage. Without it, EEA/UK remarketing and conversion data degrade.
Yes. Checking Consent Mode on any public URL is free — no signup, no install. Paid plans add scheduled monitoring and alerts so you're told when a deploy breaks Consent Mode.
You can use GA4's DebugView or Tag Assistant, but those only show your own session. The CookieInspector checker verifies Consent Mode the way a fresh visitor experiences it — default state, banner interaction, and the post-consent update — and flags pre-consent leaks GA4's own tools won't surface.
Related tools & guides