Google Consent Mode V2: Complete Setup Guide for 2026

Since March 2024, Google requires Consent Mode V2 for any website running Google Ads or Analytics in the European Economic Area. Without it, your remarketing audiences shrink, conversion data becomes unreliable, and your ad campaigns lose effectiveness. Here's how to set it up correctly.

What Is Google Consent Mode V2?

Consent Mode is a Google API that adjusts how Google tags (Analytics, Ads, Floodlight) behave based on user consent. When a user declines cookies, instead of losing all data, Consent Mode sends "consent pings" — cookieless signals that Google uses for conversion modeling.

V2 introduces two new required parameters:

• ad_user_data: Controls whether user data can be sent to Google for advertising
• ad_personalization: Controls whether personalized advertising is allowed

Combined with the existing V1 parameters:

• analytics_storage: Controls Google Analytics cookies
• ad_storage: Controls Google Ads cookies

Why It Matters

Implementation Methods

Method 1: Google Tag Manager (Recommended)

1. Enable Consent Overview: In GTM, go to Admin → Container Settings → enable "Enable consent overview"
2. Set default consent state: Add a Consent Initialization tag that sets all four parameters to "denied" by default for EEA visitors
3. Connect your CMP: Your Consent Management Platform should fire an update command when the user grants consent
4. Verify with Tag Assistant: Check that consent states change correctly when users accept or reject

Method 2: Manual Implementation (gtag.js)

<!-- Set defaults BEFORE loading gtag.js -->
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}

// Default: deny everything for EEA
gtag('consent', 'default', {
  'ad_storage': 'denied',
  'ad_user_data': 'denied',
  'ad_personalization': 'denied',
  'analytics_storage': 'denied',
  'wait_for_update': 500   // ms to wait for CMP
});
</script>

<!-- Load gtag.js AFTER consent defaults -->
<script async src="https://www.googletagmanager.com/gtag/js?id=GA-XXXXX"></script>

<!-- When user consents, update: -->
<script>
gtag('consent', 'update', {
  'ad_storage': 'granted',
  'ad_user_data': 'granted',
  'ad_personalization': 'granted',
  'analytics_storage': 'granted'
});
</script>

CMP Integration

Your consent banner must communicate with Consent Mode. Most major CMPs support this natively:

Testing and Verification

1. Google Tag Assistant: Check consent state changes in real-time
2. Chrome DevTools: Monitor Network tab for consent parameters in Google requests
3. Google Analytics Debug View: Verify events arrive with correct consent status
4. PrivacyChecker: Scan your site to verify Google tags respect consent state

Common Mistakes

• Loading gtag.js before setting defaults: The consent default must execute BEFORE the Google tag loads
• Missing ad_user_data or ad_personalization: V2 requires all four parameters — missing two means V1 only
• Not setting wait_for_update: Without it, tags may fire before the CMP loads
• Granting by default for EU users: Violates GDPR — default must be "denied" in EEA
• Not testing reject flow: Verify that declining cookies actually sets parameters to "denied"

Run a PrivacyChecker scan to verify your Consent Mode V2 implementation and ensure Google tags behave correctly with and without consent.