Google Consent Mode v2 in 2026: Strict vs Advanced Implementation & EEA Compliance

1. The 4 Fundamental Consent Signals

Consent Mode v2 introduced two mandatory new parameters in addition to the classic storage keys: `ad_user_data` (authorizing PII transmission to Google for advertising purposes) and `ad_personalization` (authorizing behavioral remarketing lists).

These exist alongside the legacy parameters: `ad_storage` (advertising cookies) and `analytics_storage` (analytics cookies). All four must be initialized to 'denied' by default before any tracking scripts execute.

// Initialize default consent states before Google Tag Manager loads
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}

gtag('consent', 'default', {
  'ad_storage': 'denied',
  'ad_user_data': 'denied',
  'ad_personalization': 'denied',
  'analytics_storage': 'denied',
  'wait_for_update': 500 // Allow CMP up to 500ms to resolve prior consent
});

gtag('set', 'ads_data_redaction', true);
gtag('set', 'url_passthrough', true);

2. Advanced vs. Basic Consent Mode: Architectural Tradeoffs

In Basic Consent Mode, tags are blocked from executing entirely until the visitor explicitly grants consent. If consent is rejected, zero requests leave the browser. This provides maximum privacy guarantees but eliminates Google's machine learning conversion modeling for non-consenting users.

In Advanced Consent Mode, tags load immediately upon pageview, but if consent is 'denied', they transmit cookieless pings without persistent identifiers. Google uses these non-identifying pings to mathematically reconstruct modeled conversions with up to 90% accuracy in Google Ads and GA4.

3. Handling the Consent Update Trigger

When a user accepts cookies on your Consent Management Platform (CMP), the CMP fires an update command. Crucially, your Google Tag Manager triggers must listen for this update to fire dependent tags without requiring a page refresh.

// Executed when user accepts Marketing & Analytics categories in CMP
gtag('consent', 'update', {
  'ad_storage': 'granted',
  'ad_user_data': 'granted',
  'ad_personalization': 'granted',
  'analytics_storage': 'granted'
});

// Push custom event so GTM trigger fires on dynamic grant
window.dataLayer.push({
  event: 'consent_updated',
  consent_level: 'full'
});