Google Consent Mode v2 Is Breaking Your Analytics: Here's How to Fix It

If your Google Analytics 4 reports have been looking off for EU traffic lately (lower conversion rates, gaps in audience data, remarketing lists that stopped growing), there's a good chance Google Consent Mode v2 is the culprit. Not because it's broken, but because you probably haven't implemented it yet.

Since March 2024, Google requires Consent Mode v2 for any website using Google Ads, GA4, or other advertising products that serves users in the European Economic Area (EEA) or UK. Without it, Google silently stops collecting meaningful data from those users. No error message. No warning in your dashboard. Just... less data.

What's actually happening

Here's the timeline of what went wrong for most websites:

• The EU's Digital Markets Act (DMA) designated Google as a "gatekeeper" in September 2023
• Under the DMA, Google must get explicit consent before combining user data across services for advertising
• Google's solution: require websites to implement Consent Mode v2 with two new parameters (ad_user_data, ad_personalization)
• Deadline: March 2024. After that, websites without Consent Mode v2 lose the ability to build audiences, track conversions, and run remarketing for EU users
• Most websites missed the deadline or implemented it incorrectly. Their data has been degraded ever since.

How to tell if you're affected

Check these signals:

• GA4: Compare EU traffic metrics (sessions, conversions) between Q1 2024 (before) and now. If there's a cliff, Consent Mode is likely the cause.
• Google Ads: Check if your EU remarketing audiences have stopped growing or shrunk significantly.
• Google Ads: Look at conversion tracking for EU campaigns. If modeled conversions disappeared, you're missing Consent Mode signals.
• Tag Assistant: Run Google Tag Assistant on your site and check if consent signals are being sent. If you see 'consent: not set' for ad_user_data or ad_personalization, you're not on v2.

The fix: 3 options, from fastest to most manual

Option 1: Use a CMP with built-in support (5 minutes)

The fastest path. A consent management platform like AutoCMP has Google Consent Mode v2 built in. Add one script tag to your site, and it automatically:

• Sets all 7 consent types to 'denied' by default on page load
• Updates consent state when the user makes their choice
• Sends the correct gtag('consent', 'update', ...) calls to Google's tags
• Handles both the consent banner UI and the Consent Mode signaling in a single integration

You don't need to touch your Google tags. You don't need to edit your GTM container. The CMP handles the signaling layer automatically.

Option 2: Manual gtag.js implementation (30 minutes)

If you want to implement it yourself, add consent defaults before your Google tags load:

gtag('consent', 'default', {
  'ad_storage': 'denied',
  'ad_user_data': 'denied',
  'ad_personalization': 'denied',
  'analytics_storage': 'denied',
  'wait_for_update': 500
});

Then, when your cookie banner gets consent, fire the update:

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

The critical pieces: the ad_user_data and ad_personalization parameters are what make it "v2." If you only have ad_storage and analytics_storage, you're still on v1 and Google won't count it.

Option 3: GTM Consent Overview (1 hour)

If you use Google Tag Manager, you can configure Consent Mode through GTM's built-in Consent Overview settings. This involves setting consent requirements on each tag and using your CMP's GTM template (or a custom variable) to feed consent state. It works, but it's more complex and easier to misconfigure than Options 1 or 2.

Basic vs Advanced mode: which to pick

When implementing Consent Mode, you'll choose between two modes:

• Basic mode: Google tags don't load at all until consent is given. No data flows to Google before consent. Strictest privacy, but you lose all data from users who reject cookies.
• Advanced mode: Google tags load before consent but send cookieless pings (no cookies set). Google uses these pings for behavioral modeling to estimate conversions you'd otherwise lose. More data, slightly less strict on privacy.

Common mistakes to avoid

• Setting consent defaults AFTER Google tags load. The defaults must come first, or tags fire before consent state is set
• Forgetting ad_user_data and ad_personalization. Without both, Google considers it v1, not v2
• Setting everything to 'granted' by default. This defeats the entire purpose and violates GDPR
• Not testing with Google Tag Assistant. Verify that consent signals actually flow through to Google's servers
• Implementing Consent Mode without a consent banner. Consent Mode is a signaling layer, not a consent solution

The bottom line

If you're running Google Analytics or Google Ads and serving EU users, Consent Mode v2 isn't optional. Every day without it is a day of degraded conversion data, broken remarketing, and incomplete analytics. The fix takes 5-30 minutes depending on your approach.

For a deeper dive into all 7 consent types and implementation details, see our complete Google Consent Mode v2 guide.