Google Consent Mode v2 Explained: What It Means for Your Analytics

What Is Google Consent Mode v2?

Google Consent Mode v2 is a framework requiring sites that use Google Ads and/or Google Analytics 4 (GA4) with EEA/UK traffic to signal two additional consent states: ad_user_data and ad_personalization. These sit alongside Consent Mode v1's original signals, ad_storage and analytics_storage, for four consent parameters in total.

In practice, this means your consent banner needs to capture four separate choices instead of a single accept/decline toggle — a visitor might consent to analytics measurement while declining personalized ads, for instance. Your site then relays each of those choices to Google in real time via your tag configuration.

Why Google Introduced This: Regulatory Pressure Tied to the DMA

Consent Mode v2 exists because of regulatory pressure, not product preference. The EU's Digital Markets Act (DMA) imposes stricter consent requirements on how large platforms handle data used for ad personalization and remarketing. Google Ads — which relies on behavioral signals to build remarketing audiences and serve personalized ads — falls under that scope.

Since March 2024, Google has required Consent Mode v2 for sites running personalized Google Ads campaigns to EEA and UK audiences. Without the right consent signals in place, Google won't serve personalized or remarketing ads to those visitors. The underlying legal obligation comes from GDPR and the DMA; Consent Mode v2 is simply the technical mechanism Google built to capture and transmit that consent.

What Happens to Your GA4 Data When Visitors Decline Consent?

When a visitor declines consent, Google doesn't just drop their data from your reports — it uses conversion modeling, a statistical estimation technique, to fill in the resulting gaps. If a visitor declines analytics_storage, Google can still register that some event happened (a purchase, a form submission) without being able to tie it to that specific individual, since no tracking cookie was permitted. Google estimates likely conversions for the non-consenting cohort based on patterns from consenting users, and labels this estimated data separately in your reports as "modeled" conversions.

That preserves some visibility into non-consenting behavior, but it's an estimate, not a direct measurement — and its accuracy depends on having enough consented traffic for Google's models to work from. High-traffic sites generally see more reliable modeling than smaller, niche ones.

The Practical Burden: What Site Owners Must Implement

None of this happens automatically. Sites using Google Ads and GA4 in the EEA/UK need to build out real consent infrastructure:

What GA4 + Google Ads Users Need to Implement

• A consent banner or consent management platform (CMP): a clear interface letting visitors grant or withhold each of the four consent states before your Google tags fire.
• Tag configuration: wiring your Google Ads and GA4 tags (typically via Google Tag Manager) to pass the correct consent states dynamically based on each visitor's choice.
• Testing: confirming consent signals reach Google correctly and that modeled conversions show up as expected in GA4.
• Ongoing maintenance: updating the setup whenever your privacy policy, tracking stack, or tag configuration changes.

Even sites that already had a cookie banner before Consent Mode v2 often need to rework their tag manager setup to emit these specific signals and gate tag firing on them correctly.

A Cookie-Free Alternative to the Consent Mode Machinery

One distinction worth being precise about: Consent Mode v2 is a requirement tied specifically to Google Ads and GA4, not a universal standard every analytics tool must implement. If your goal is measuring website traffic, conversions, and user behavior — not running Google Ads personalization or remarketing — you may not need this consent-signaling machinery at all.

Cookie-free analytics works from a different foundation: without persistent cookies or cross-site identifiers, it doesn't trigger the specific GDPR consent requirements that Consent Mode v2 was built to satisfy. That doesn't mean privacy law stops applying — you still evaluate your own compliance obligations — but it does mean you can get accurate traffic and conversion data without four consent signals to configure and maintain. See our guide on privacy-friendly analytics for how this works in practice.

The Bottom Line

Consent Mode v2 is a real requirement for sites running Google Ads and GA4 to EEA/UK audiences — but it's a Google-specific compliance mechanism, not a universal analytics law. If your goal is basic traffic and conversion measurement, a cookie-free analytics tool sidesteps this specific engineering burden entirely. Which path fits depends on whether Google Ads personalization is part of your marketing stack.