Google Consent Mode v2: Complete Setup Guide

What is Google Consent Mode v2?

Consent Mode is a signaling layer between your cookie consent banner and Google's tags. When a user makes a consent choice (accept or reject), your consent management platform sends that decision to Google via the gtag('consent', 'update', ...) command. Google's tags then adjust their behavior accordingly:

• If consent is granted: tags operate normally, setting cookies and collecting full data
• If consent is denied: tags either don't fire at all (basic mode) or send cookieless pings without setting cookies (advanced mode)

The "v2" update added two new consent types, ad_user_data and ad_personalization, to comply with the EU Digital Markets Act (DMA) requirements imposed on Google as a designated gatekeeper.

Why Google requires Consent Mode v2

The EU's Digital Markets Act (DMA), effective March 2024, designates Google as a "gatekeeper" for several core platform services. Under the DMA, Google must obtain explicit consent before combining user data across services (Search, YouTube, Maps, Ads) for advertising purposes.

To meet this obligation, Google now requires websites using its advertising tools to implement Consent Mode v2. If you don't, Google restricts your ability to:

• Build new audience segments for remarketing
• Use conversion tracking for EU/EEA users
• Access detailed analytics data for EU visitors
• Use Google's behavioral modeling for consent gaps

Basic vs Advanced Consent Mode

Google offers two implementation approaches:

Which should you choose?

Basic mode is the safest choice if you want no data flowing to Google before consent. Some DPAs and privacy advocates consider this the most compliant approach.

Advanced mode gives Google more data to work with for behavioral modeling, resulting in more complete analytics and conversion reporting. The cookieless pings sent before consent don't contain identifiers or set cookies, but they do transmit information like timestamp, user agent, and referrer.

The 7 consent types in Consent Mode v2

Consent Mode v2 uses seven parameters to communicate consent status to Google:

The two new v2 parameters, ad_user_data and ad_personalization, are what differentiate v2 from v1. Without these, Google considers your Consent Mode implementation incomplete.

How to implement Consent Mode v2

There are three main approaches:

Option 1: Use a CMP with built-in support

The simplest approach. A consent management platform like AutoCMP handles the entire integration: setting default consent states on page load, updating consent when the user makes a choice, and mapping cookie categories to Google's consent types. No manual code required.

Option 2: Manual implementation via gtag.js

Set default consent states before your Google tags load, then update them when the user consents:

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

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

Option 3: Google Tag Manager

GTM has built-in Consent Mode support via the "Consent Overview" in tag settings. You configure which consent types each tag requires, then use your CMP's GTM template to send consent signals. This is the most common approach for sites already using GTM.

How AutoCMP handles Consent Mode automatically

AutoCMP has Google Consent Mode v2 built in. When you add the AutoCMP script to your site, it automatically:

• Sets all consent types to 'denied' by default on page load (before any Google tags fire)
• Maps your cookie consent categories to Google's 7 consent types
• Sends gtag('consent', 'update', ...) when the user makes their choice
• Pushes consent events to the dataLayer for GTM integration
• Supports both basic and advanced mode (configurable in dashboard)
• Works with GA4, Google Ads, Floodlight, and all gtag-based products

Frequently asked questions

Does Consent Mode replace a cookie banner?

No. Consent Mode is a signaling mechanism, not a consent solution. You still need a cookie banner to collect user consent. Consent Mode simply communicates the user's choices to Google's tags.

What happens to my Google Ads data without Consent Mode v2?

Without Consent Mode v2, Google cannot use data from EU users for audience building, remarketing, or conversion measurement. Your campaigns will still run, but measurement and optimization will be significantly limited for EU traffic.

Is Consent Mode compliant with GDPR?

Consent Mode itself is a technical framework, and compliance depends on how you implement it. In basic mode (no data before consent), it aligns well with GDPR. In advanced mode, the cookieless pings sent before consent are a gray area that some DPAs may scrutinize. The safest approach is basic mode combined with a fully compliant consent banner.

Do I need Consent Mode for non-EU users?

Google only requires Consent Mode for users in the EEA and UK. However, implementing it globally is a good practice as more regions adopt similar requirements and Google may expand the mandate.

What is the "wait_for_update" parameter?

The wait_for_update parameter (in milliseconds) tells Google tags to wait for a consent update before firing. This gives your CMP time to check for returning visitors' saved consent preferences. A value of 500ms is typical.