Consent Mode v2 Validator
Validate your Google Consent Mode v2 configuration
How It Works
Paste your consent config
Copy your gtag("consent", "default", {...}) code block and paste it in.
Validate consent types
The tool checks for all required Consent Mode v2 types and valid values.
Review recommendations
See which consent types are missing, incorrectly set, or using deprecated patterns.
Consent Mode v2 Validator
What Is Google Consent Mode v2 and Why Is It Mandatory?
Google Consent Mode v2 is mandatory for all European Economic Area (EEA) advertisers from March 2024. It adds two new consent types — ad_user_data and ad_personalization — on top of analytics_storage and ad_storage. Businesses that fail to implement Consent Mode v2 correctly risk losing access to GA4 audience features and Smart Bidding capabilities for EEA users.
The Four Required Consent Types in Consent Mode v2
- analytics_storage — Controls whether GA4 can use cookies for measurement.
- ad_storage — Controls whether Google Ads tags can use cookies for ad targeting.
- ad_user_data (NEW in v2) — Controls whether user data can be sent to Google for advertising purposes.
- ad_personalization (NEW in v2) — Controls whether personalised advertising is permitted.
How Consent Mode v2 Works With Your CMP
The default consent call must run before the GTM container loads. If your CMP fires the default consent after GTM initialises, the first set of page load tags already fire in an unconsented state, violating GDPR. Validate your Consent Mode configuration here, then verify timing with GTM Preview mode.