Google Compliance
Consent Mode v2 Validator
Paste your URL below. We'll check if all 4 required consent types are set, defaults are denied, updates fire correctly, and GA4 receives the GCS parameter.
Real browser scan
We launch a headless Chromium browser and load your page exactly like a real visitor would.
Instant analysis
Every network request, cookie, and dataLayer push is intercepted and analyzed in real-time.
Actionable findings
Get severity-scored results with specific fix instructions. Share the report via a unique link.
What we check
4 required consent types
Validates ad_storage, analytics_storage, ad_user_data, and ad_personalization are all present.
Default denied state
Checks that the consent default command sets all types to "denied" before user interaction.
Update mechanism & timing
Verifies consent update fires after user interaction and before GA4 config command.
GCS parameter
Confirms GA4 requests include the Google Consent Signal (GCS) parameter proving consent mode is active.
How to read results
Each check is pass or fail. Failures mean Google Ads cannot model conversions for your account.
Common issues we find
Missing ad_user_data and ad_personalization
These two types were added in Consent Mode v2. Many sites still only set ad_storage and analytics_storage. Fix: add all 4 types to your default command.
Defaults set to "granted" instead of "denied"
Consent types default to granted, meaning cookies fire before user choice. Fix: set all consent defaults to "denied" in your CMP or GTM template.
GA4 config fires before consent default
The gtag config command runs before the consent default, making consent mode ineffective. Fix: ensure consent default fires first in your tag sequence.