Google Consent Mode v2: Complete Setup Guide for GTM

What Is Consent Mode v2?

Google Consent Mode v2 is an updated framework for handling cookie consent in compliance with GDPR and other privacy laws. It became mandatory in March 2024 for all Google Ads and GA4 users in the EU and UK.

Without it configured, Google stops tracking most of your traffic properly. GA4 shows massive drops in sessions and conversions. Google Ads can't optimize campaigns because it's not receiving conversion data. Your ROAS tanks, not because campaigns are performing worse, but because the data is broken.

How Consent Mode v2 Works

When someone visits your site, your cookie banner asks for consent. Consent Mode tells Google's tags (GA4, Google Ads, etc.) whether the user accepted or rejected cookies.

Based on consent status, tags adjust their behavior:

• User accepts cookies: GA4 and Google Ads tags work normally, full tracking.
• User rejects cookies: Tags fire in "cookieless mode", sending anonymous pings without setting cookies. Google uses modeling to estimate conversions.

This keeps you compliant with GDPR while still sending some data to Google, allowing the algorithm to function (though with less accuracy).

Do You Need Consent Mode v2?

Yes, if you:

• Serve traffic from EU or UK
• Use Google Ads or GA4
• Have a cookie banner on your site

Even if you're a UK-only business, you need it. Even if most traffic is from the US but some is from Europe, you need it. Google enforces this globally for any account serving EU/UK traffic.

How to Set Up Consent Mode v2 in GTM

Step 1: Choose Your Cookie Banner

You need a GDPR-compliant cookie banner that integrates with Consent Mode. Popular options:

• Cookiebot (paid, easy GTM integration)
• OneTrust (enterprise, expensive)
• Termly (affordable, solid integration)
• CookieYes (budget option)

Most modern cookie banner tools have built-in Consent Mode support. Check their docs for GTM integration guides.

Step 2: Add Consent Initialization Tag

In GTM, create a new tag with the following setup:

• Tag Type: Consent Initialization - Google tags
• Consent Settings: Default values before user interacts with banner
• Default analytics_storage: denied
• Default ad_storage: denied
• Default ad_user_data: denied (v2 requirement)
• Default ad_personalization: denied (v2 requirement)
• Trigger: Consent Initialization - All Pages

This sets the default consent state to "denied" for everyone. Then, when someone accepts cookies, the banner updates these values to "granted".

Step 3: Configure Your Cookie Banner Integration

Your cookie banner needs to send consent signals to GTM. Most modern banner tools do this via the gtag('consent', 'update') command.

When someone clicks "Accept All", the banner should fire:

gtag('consent', 'update', {
  'analytics_storage': 'granted',
  'ad_storage': 'granted',
  'ad_user_data': 'granted',
  'ad_personalization': 'granted'
});

When someone clicks "Reject All", it should fire:

gtag('consent', 'update', {
  'analytics_storage': 'denied',
  'ad_storage': 'denied',
  'ad_user_data': 'denied',
  'ad_personalization': 'denied'
});

Check your cookie banner's documentation for specific setup instructions. Most have a GTM integration section.

Step 4: Update GA4 and Google Ads Tags

Your GA4 Config tag and Google Ads conversion tags don't need changes. They automatically respect Consent Mode once it's configured. However, you should verify "Consent" is set to "No additional consent required" in each tag's settings (this is usually the default).

Step 5: Test Consent Mode

Use GTM Preview Mode to test:

1. Clear your cookies and open your site in Preview Mode
2. Before interacting with the banner, check the Consent tab in Preview panel—should show all consent types as "denied"
3. Click "Accept All" on your banner
4. Check Consent tab again—should show all types as "granted"
5. Verify GA4 and Google Ads tags fire correctly after consent is granted

If consent updates correctly and tags fire after acceptance, your setup is working.

Common Consent Mode Mistakes

• Missing ad_user_data or ad_personalization: v2 requires four consent types, not just two. If you only configure analytics_storage and ad_storage, you're not v2 compliant.
• Setting default to "granted": For GDPR compliance, default must be "denied" until user explicitly accepts. Starting with "granted" violates GDPR.
• Banner doesn't update consent: Cookie banner shows but never sends consent signals to GTM. Check banner integration—it should fire gtag('consent', 'update') on user action.
• Not testing both accept and reject paths: Test what happens when someone rejects cookies. Tags should still fire in cookieless mode, but without setting cookies.

What Happens After Setup?

Once Consent Mode is working:

• Users who accept: Full tracking, normal data quality.
• Users who reject: Google receives anonymous pings and uses conversion modeling to estimate performance. Your reported conversions will be slightly lower, but more compliant and still useful for optimization.
• Google Ads: Can optimize campaigns even with partial consent data thanks to modeling. Better than losing all data.

Related Guides