Back to DigiConsent

Google Consent Mode Setup – Complete GCM v2 Integration Guide

Google Consent Mode (GCM) is a powerful framework that allows Google tags to adjust their behavior based on user consent choices. Instead of completely blocking Google Analytics, Google Ads, and other Google services when users decline cookies, Consent Mode enables these tools to operate in a limited, privacy-preserving manner while still providing valuable (though aggregated) data. DigiConsent provides seamless integration with Google Consent Mode v2, ensuring your analytics and advertising remain functional while respecting user privacy choices.

This comprehensive guide explains what Google Consent Mode is, why it matters, how to configure it in DigiConsent, and how to verify it’s working correctly.

Understanding Google Consent Mode

Google Consent Mode fundamentally changes how consent works with Google’s measurement and advertising tools.

Traditional Cookie Consent

In traditional cookie consent implementations:

  • User declines analytics/marketing cookies
  • All analytics and advertising scripts are blocked completely
  • You collect zero data from users who decline
  • Google Analytics shows no information about non-consenting users
  • Conversion tracking stops working entirely for declined users

This approach is privacy-compliant but results in significant data loss, making it harder to understand your full audience and optimize marketing.

How Consent Mode Works

With Google Consent Mode enabled:

  • Google tags load but adjust their behavior based on consent status
  • When users decline cookies, tags operate in a limited mode
  • No cookies or identifiers are stored without consent
  • Google uses modeling and aggregation to fill data gaps
  • You maintain privacy compliance while getting useful (modeled) insights

Think of it as Google’s tags having two modes: full functionality with consent, privacy-preserving limited functionality without consent.

Consent Mode v2 Updates

In 2024, Google introduced Consent Mode v2 with two additional consent parameters:

Original parameters (v1):

  • analytics_storage: Controls analytics cookies (Google Analytics)
  • ad_storage: Controls advertising cookies (Google Ads, remarketing)

New parameters (v2):

  • ad_user_data: Controls whether user data can be sent to Google for advertising purposes
  • ad_personalization: Controls whether data can be used for personalized advertising (remarketing)

Consent Mode v2 is required for EEA and UK audiences as of March 2024. DigiConsent fully supports v2 with all four parameters.

Benefits of Google Consent Mode

Implementing Consent Mode provides significant advantages over traditional blocking approaches:

Reduced Data Loss

Without Consent Mode, declining users are completely invisible in your analytics. With Consent Mode, Google uses:

  • Conversion modeling: Estimates conversions from non-consenting users based on behavioral patterns
  • Aggregated measurement: Provides aggregated insights without individual tracking
  • Machine learning: Fills gaps using ML models trained on consenting user behavior

This typically recovers 60-85% of the insights you would lose with traditional blocking, while maintaining privacy compliance.

Maintained Marketing Performance

For Google Ads campaigns:

  • Conversion tracking continues: Even when users decline, Google can model conversions
  • Better optimization: Google Ads algorithms have more complete data for optimization
  • Remarketing lists: Can still function using aggregated signals
  • Smart Bidding: Remains effective with modeled conversion data

Compliance with Privacy Regulations

Consent Mode is designed to be privacy-compliant:

  • No cookies are set without consent
  • No personal data is sent without consent
  • Respects GDPR, ePrivacy, and other regulations
  • Provides the required user control over data collection

Google has designed Consent Mode specifically to work within privacy law requirements, and it’s widely accepted as compliant when properly implemented.

The Four Consent Mode Parameters

Understanding each parameter helps you configure Consent Mode correctly.

analytics_storage

Controls whether cookies can be used for analytics purposes (Google Analytics).

When granted:

  • Google Analytics cookies (_ga, _gid, etc.) are set
  • Individual user behavior is tracked
  • Full Analytics reporting is available
  • User journeys and sessions are tracked normally

When denied:

  • No analytics cookies are set
  • Pings are sent to Google without cookies or identifiers
  • Google uses modeling to estimate analytics metrics
  • Data appears as aggregated insights, not individual users

Maps to DigiConsent category: Analytics Cookies

ad_storage

Controls whether cookies can be used for advertising purposes.

When granted:

  • Advertising cookies are set (_gcl_*, _gac_*, IDE, etc.)
  • Conversion tracking works normally
  • Remarketing audiences are built
  • Attribution data is collected

When denied:

  • No advertising cookies are set
  • Conversion events are sent without user identifiers
  • Google models conversions and attributes them to campaigns
  • Remarketing uses aggregated signals instead of individual tracking

Maps to DigiConsent category: Marketing Cookies

ad_user_data

Controls whether user data (from your site) can be sent to Google for advertising purposes.

When granted:

  • User data (email addresses, phone numbers, etc.) can be sent to Google
  • Enhanced conversions can use hashed user data
  • Customer Match audiences can be created
  • More accurate conversion tracking with user-provided data

When denied:

  • No user-provided data is sent to Google for advertising
  • Enhanced conversions are limited
  • Customer Match features are restricted

Maps to DigiConsent category: Marketing Cookies

ad_personalization

Controls whether data can be used for personalized advertising (remarketing).

When granted:

  • Remarketing lists can be built and used
  • Personalized ads are shown based on user behavior
  • Dynamic remarketing works fully

When denied:

  • Users won’t be added to remarketing lists
  • No personalized ads based on site behavior
  • Only generic, non-personalized advertising

Maps to DigiConsent category: Marketing Cookies

Consent Mode Implementation Methods

Google Consent Mode can be implemented in two ways. DigiConsent supports both.

Basic Consent Mode

In Basic mode:

  • Google tags don’t load until user provides consent
  • Upon consent, tags load and send consent signals
  • Simpler implementation but some data loss
  • No measurement before consent is given

Use Basic mode when:

  • You prefer tags not to load at all without consent
  • You want the simplest implementation
  • You’re okay with some data gaps for non-consenting users

Advanced Consent Mode (Recommended)

In Advanced mode:

  • Google tags load immediately with all consents set to “denied” by default
  • Tags operate in cookieless mode until consent is given
  • When consent is granted, tags update and begin normal operation
  • Provides better data coverage through modeling
  • No cookies are set before consent (still privacy-compliant)

Use Advanced mode when:

  • You want maximum data coverage (recommended)
  • You’re running Google Ads and need conversion modeling
  • You want the full benefits of Consent Mode

DigiConsent uses Advanced Consent Mode by default, as it provides the best balance of privacy compliance and data utility.

Configuring Google Consent Mode in DigiConsent

DigiConsent makes Consent Mode configuration straightforward.

Step 1: Enable Google Consent Mode

  1. Navigate to DigiConsent > Settings > Google Consent Mode
  2. Toggle Enable Google Consent Mode to ON
  3. Select Consent Mode v2 (recommended and required for EEA/UK)
  4. Choose Advanced Implementation (recommended)

Step 2: Map Consent Categories

DigiConsent automatically maps your cookie categories to Consent Mode parameters:

  • Analytics Cookies → analytics_storage
  • Marketing Cookies → ad_storage, ad_user_data, ad_personalization
  • Functional Cookies → Not mapped (optional)
  • Necessary Cookies → Always allowed

When a user accepts Analytics cookies, DigiConsent sets analytics_storage: 'granted'. When they accept Marketing cookies, DigiConsent sets ad_storage: 'granted', ad_user_data: 'granted', and ad_personalization: 'granted'.

Step 3: Configure Default States

Set the default state for each parameter before the user makes a choice:

For GDPR compliance (EEA/UK):

  • analytics_storage: denied
  • ad_storage: denied
  • ad_user_data: denied
  • ad_personalization: denied

This ensures explicit opt-in consent as required by GDPR.

For non-GDPR regions:

You may set defaults to “granted” if your local regulations permit implied consent, but “denied” is the safer, more privacy-respecting default.

Step 4: Set Regional Configurations

Consent Mode v2 supports region-specific settings. You can configure different default states for different geographic regions:

// EEA countries default to denied
gtag('consent', 'default', {
  'ad_storage': 'denied',
  'analytics_storage': 'denied',
  'ad_user_data': 'denied',
  'ad_personalization': 'denied',
  'region': ['AT', 'BE', 'BG', 'HR', ...] // EEA country codes
});

// Other regions might allow different defaults
gtag('consent', 'default', {
  'ad_storage': 'granted',
  'analytics_storage': 'granted',
  'ad_user_data': 'granted',
  'ad_personalization': 'granted',
  'region': ['US', 'CA'] // Example
});

DigiConsent handles regional configuration automatically based on your settings.

Step 5: Verify Google Tag Implementation

For Consent Mode to work, your Google tags must be properly implemented:

Google Tag Manager (GTM):

  • Install Google Tag Manager on your site
  • Add Google Analytics and Google Ads tags through GTM
  • Ensure GTM is configured to listen for consent mode signals
  • DigiConsent automatically communicates with GTM

Direct gtag.js implementation:

  • If using gtag.js directly (not through GTM), ensure it’s installed
  • DigiConsent will inject consent signals before your gtag.js script

Testing Google Consent Mode

After configuration, thorough testing ensures Consent Mode is working correctly.

Browser Console Testing

Use browser developer tools to verify consent signals:

  1. Open your website in Chrome
  2. Open Developer Tools (F12 or Cmd+Option+I)
  3. Go to the Console tab
  4. Clear cookies and reload the page
  5. Type dataLayer in the console and press Enter
  6. Look for consent default events showing all consents as “denied”
  7. Accept cookies in the banner
  8. Check dataLayer again for consent update events with “granted” status

    9. You should see events like:

    {event: 'consent', 'default', ad_storage: 'denied', analytics_storage: 'denied', ...}
{event: 'consent', 'update', ad_storage: 'granted', analytics_storage: 'granted', ...}

    Google Tag Assistant

    Google’s Tag Assistant Chrome extension helps verify Consent Mode:

    1. Install Tag Assistant Chrome extension
    2. Navigate to your website
    3. Open Tag Assistant
    4. Click “Connect”
    5. Clear cookies and reload
    6. Tag Assistant shows consent status for each tag
    7. Verify tags are firing in “Consent Mode” state before consent
    8. Accept cookies and verify tags update to full functionality

      9. Network Tab Verification

      Inspect network requests to confirm cookieless operation:

      1. Open Developer Tools → Network tab
      2. Clear cookies and reload page
      3. Filter for “google-analytics.com” or “googletagmanager.com”
      4. Examine requests before consent—they should include gcs (Google Consent State) parameters
      5. Verify no cookies are being set in Application → Cookies
      6. Accept consent and verify cookies now appear

        7. Google Analytics Real-Time Reports

        Check Google Analytics to verify data collection:

        1. Open Google Analytics Real-Time report
        2. Visit your site without giving consent
        3. Verify event still appears in Real-Time (as modeled ping)
        4. Give consent and verify transition to full tracking

          5. Troubleshooting Common Issues

          Issue: Consent Mode Not Working

          Symptoms: Tags don’t respect consent choices, or consent signals aren’t firing.

          Solutions:

          • Verify Consent Mode is enabled in DigiConsent settings
          • Ensure Google tags (GTM or gtag.js) are properly installed
          • Check that DigiConsent consent script loads before Google tags
          • Clear browser cache and cookies, test in incognito mode
          • Check browser console for JavaScript errors

          Issue: Cookies Setting Before Consent

          Symptoms: Google Analytics or Ads cookies appear before user consents.

          Solutions:

          • Verify you’re using Advanced Consent Mode with default denied states
          • Check that consent defaults are set before Google tags load
          • Ensure no duplicate Google tag implementations that bypass consent
          • Look for hardcoded gtag.js scripts that don’t respect consent

          Issue: Google Ads Conversions Not Tracking

          Symptoms: Conversions disappear entirely in Google Ads after implementing Consent Mode.

          Solutions:

          • Give Consent Mode time (Google needs 7+ days to build modeling)
          • Verify conversion tags are firing (check Tag Assistant)
          • Ensure you’re using Advanced Consent Mode (Basic mode loses more data)
          • Check that ad_storage is granted when marketing cookies are accepted

          Best Practices for Consent Mode

          • Use Advanced Implementation: Provides better data coverage through modeling
          • Default to denied in GDPR regions: Ensures compliance with opt-in requirements
          • Use v2 parameters: Required for EEA/UK, provides better control
          • Test thoroughly: Verify consent signals fire correctly before and after consent
          • Monitor data quality: Watch Google Analytics for data gaps and modeling accuracy
          • Document implementation: Keep records of your Consent Mode configuration for compliance audits
          • Keep DigiConsent updated: Consent Mode requirements evolve; stay current

          Understanding Modeled Data

          When users decline cookies but you have Consent Mode enabled, Google uses machine learning to model their behavior:

          How modeling works:

          • Google analyzes patterns from consenting users
          • Machine learning identifies similar behavioral patterns in non-consenting users
          • Conversions and engagement are estimated based on these patterns
          • Aggregated data is provided without individual user tracking

          Modeled data limitations:

          • Less accurate than directly measured data
          • Requires sufficient consenting user volume for accurate modeling
          • Some reports may show incomplete data
          • User-level reporting is not available for modeled users

          Despite limitations, modeled data is significantly better than no data and maintains your ability to optimize campaigns and understand audience behavior while respecting privacy.

          Consent Mode Configuration Checklist

          Use this checklist to ensure proper Consent Mode setup:

          • Google Consent Mode enabled in DigiConsent
          • Consent Mode v2 selected
          • Advanced implementation configured
          • Default states set to “denied” for GDPR compliance
          • Cookie categories properly mapped to consent parameters
          • Google Tag Manager or gtag.js properly installed
          • DigiConsent script loads before Google tags
          • Tested in browser console (dataLayer verification)
          • Verified with Google Tag Assistant
          • Confirmed no cookies before consent in Network/Application tabs
          • Checked Google Analytics Real-Time reports
          • Documented configuration for compliance records

          Google Consent Mode represents the future of privacy-compliant measurement and advertising. By properly configuring DigiConsent to work with Consent Mode v2, you ensure your website respects user privacy choices while maintaining the analytics and marketing capabilities needed to run your business effectively. The key is thorough configuration and testing to verify that consent signals flow correctly to Google’s systems.

          Similar Articles

Back to DigiConsent