Background: Why Consent Mode Matters

The EU's General Data Protection Regulation (GDPR) and similar privacy laws worldwide have made consent management a critical requirement for digital advertising. When users decline cookie consent, traditional tracking methods fail — creating gaps in conversion data.

Google's Consent Mode addresses this by adjusting how Google tags behave based on user consent status. When consent is denied, Google uses modeled conversions to estimate the missing data — recovering up to 70% of lost conversion signals.

What is Consent Mode?

Consent Mode is a framework that allows advertisers to indicate whether users have consented to cookies for analytics and advertising purposes. Based on this signal, Google tags adjust their behavior:

• Consent granted: Normal tracking — full cookie-based measurement
• Consent denied: Cookieless measurement — Google uses aggregated, modeled data to estimate conversions and user behavior

What's New in Consent Mode v2

Version 2 introduces two new consent parameters:

These join the existing v1 parameters:

• ad_storage — enables storage of advertising cookies
• analytics_storage — enables storage of analytics cookies
• functionality_storage — enables storage for site functionality
• personalization_storage — enables storage for personalization
• security_storage — enables storage for security

Implementation Guide

Option 1: Using a Consent Management Platform (CMP)

The easiest approach is to use a Google-certified CMP that integrates natively with Consent Mode:

• Cookiebot, OneTrust, TrustArc, Usercentrics, Didomi, etc.
• Configure your CMP to send consent signals to the Google Data Layer
• The CMP automatically sets the Consent Mode parameters based on user choices

Option 2: Manual Implementation

If you're not using a CMP, you can implement Consent Mode directly:

Step 1: Set default consent state (before tags load):

<!-- Set default consent to denied before any Google tags -->
<script>
  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
  });
</script>

Step 2: Update consent when user makes a choice:

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

// Or update specific parameters based on user choices
// e.g., user consents to analytics but not personalization
gtag('consent', 'update', {
  'analytics_storage': 'granted',
  'ad_storage': 'granted',
  'ad_user_data': 'denied',
  'ad_personalization': 'denied'
});

How Modeled Conversions Work

When consent is denied, Google uses machine learning to model conversions based on:

• Aggregated data from consenting users with similar behavior patterns
• Historical conversion data from your account
• Browser and device signals
• Time and geographic patterns

Google reports that modeled conversions can recover up to 70% of the data lost when users deny consent. This varies by industry and traffic volume — accounts with more historical data get better modeling results.

Impact on Google Ads Performance

• Bidding optimization: Smart Bidding strategies (tCPA, tROAS, Maximize Conversions) rely on conversion data. Without Consent Mode, denied-consent users create data gaps that degrade bidding performance.
• Audience targeting: When ad_personalization is denied, users are excluded from remarketing lists and similar audiences.
• Conversion reporting: Modeled conversions appear in your Google Ads reports alongside observed conversions, giving a more complete picture.

Verification & Monitoring

1. Use the Google Tag Assistant Chrome extension to verify consent signals are firing correctly
2. Check Google Ads → Conversions to see if modeled conversions appear alongside observed ones
3. Monitor conversion volume trends — a sudden drop may indicate a consent implementation issue

Conclusion

Consent Mode v2 is no longer optional — it's a requirement for running Google Ads in regions with privacy regulations. Proper implementation ensures you remain compliant while maximizing data recovery through modeled conversions. If you haven't upgraded from v1 yet, do so immediately — Google now requires v2 for European Economic Area (EEA) traffic.