Google Consent Mode v2: What You Need to Know

Why Google Consent Mode v2 Matters

Since March 2024, Google has required all advertisers targeting users in the European Economic Area (EEA) to implement Consent Mode v2. Without it, Google Ads cannot process new user data from the EEA, meaning remarketing lists stop growing, conversion measurement degrades, and campaign optimization suffers.

Consent Mode v2 bridges the gap between privacy compliance and advertising performance. It communicates your users' consent choices to Google services in real time, allowing Google to adjust its behavior accordingly.

The Two New Consent Signals

Consent Mode v2 introduced two consent parameters that did not exist in v1:

• ad_user_data — Controls whether user data can be sent to Google for advertising purposes (conversions, audience building).
• ad_personalization — Controls whether Google can use the data for personalized advertising (remarketing, similar audiences).

These join the existing analytics_storage and ad_storage signals. All four must be implemented for full compliance.

Basic Mode vs Advanced Mode

Google offers two implementation approaches:

Basic Mode

Google tags are completely blocked until the user grants consent. No data is sent to Google for non-consenting users. This is the simplest approach and the safest from a compliance standpoint, but it means you lose all measurement data for users who decline cookies.

Advanced Mode

Google tags load immediately but operate in a restricted mode when consent is denied. Instead of setting cookies, they send anonymized "pings" to Google — small packets of data that contain no personally identifiable information. Google uses these pings to model conversions and estimate the data that would have been collected had consent been granted.

Advanced Mode can recover up to 70% of conversion data that would otherwise be lost, making it the preferred choice for advertisers who need robust measurement.

Implementation with a CMP

The simplest way to implement Consent Mode v2 is through a Consent Management Platform (CMP) that has built-in support. GetCookies integrates directly with Google Consent Mode v2:

1. Install the GetCookies script on your website.
2. Enable Google Consent Mode v2 in your GetCookies dashboard.
3. Choose Basic or Advanced mode.
4. GetCookies automatically communicates consent signals to Google tags based on each visitor's choices.

No manual GTM configuration or custom JavaScript is required.

Implementation via Google Tag Manager

If you prefer a manual approach using GTM:

1. Set default consent states in your GTM container's initialization tag to denied for all parameters.
2. Configure your CMP to fire a consent update command when a user grants consent, setting the appropriate parameters to granted.
3. Ensure the consent update fires before any Google tags that depend on those signals.
4. Test using GTM's Preview mode and the Google Tag Assistant to verify signals are sent correctly.

What Happens Without Consent Mode v2

Businesses that have not implemented Consent Mode v2 face concrete consequences:

• Google Ads audiences stop including new EEA users.
• Remarketing campaigns cannot target users who visit your site from the EEA.
• Conversion tracking becomes incomplete, degrading automated bidding strategies like Target CPA and Target ROAS.
• Google Analytics 4 data from the EEA is impacted.

Getting Started

If you have not implemented Consent Mode v2 yet, the fastest path is to use a CMP with native support. GetCookies handles the integration automatically, so you can focus on your business rather than technical consent plumbing. For advertisers, the performance impact of not implementing is significant and grows every day you wait.