Google Consent Mode v2: What Marketers Need to Know in 2025

As of March 2024, Google requires Consent Mode v2 for any site that wants to use personalized advertising features in the European Economic Area (EEA). If you haven't updated your implementation, your remarketing audiences are degrading silently, your conversion modeling is less accurate, and your Google Ads campaigns are operating with incomplete data.

This guide covers everything marketers and analytics professionals need to know about Consent Mode v2 in 2025: what changed from v1, how to implement it correctly with GTM and your CMP, how to test your implementation, and what happens if you don't comply.

What Is Google Consent Mode?

Google Consent Mode is a framework that allows your Google tags (Analytics, Ads, Floodlight, etc.) to adjust their behavior based on the user's consent choices. Instead of completely blocking tags when consent is denied, Consent Mode lets tags fire in a restricted, cookieless manner — sending "pings" to Google that contain no personally identifiable information but still provide aggregated measurement signals.

This is fundamentally different from the binary "block all tags" approach used by most cookie banners. With Consent Mode, Google can use machine learning to model the conversions and behavior of users who denied consent, filling in the gaps in your data without compromising privacy.

What Changed in v2

Consent Mode v2 introduced two new consent parameters that didn't exist in v1:

• ad_user_data: Controls whether user data can be sent to Google for advertising purposes. When denied, Google won't use any first-party data you collect for ad targeting.
• ad_personalization: Controls whether ads can be personalized for the user. When denied, remarketing and personalized advertising features are disabled for that user.

These join the existing v1 parameters:

• analytics_storage: Controls whether analytics cookies can be set (e.g., the GA4 _ga cookie).
• ad_storage: Controls whether advertising cookies can be set (e.g., Google Ads conversion cookies).
• functionality_storage: Controls cookies for site functionality (language preferences, etc.).
• personalization_storage: Controls cookies for personalization features.
• security_storage: Controls cookies essential for security (authentication, fraud prevention).

Without the new ad_user_data and ad_personalization parameters, Google Ads cannot use any of your conversion data or audiences for personalized advertising in the EEA — even if the user has granted consent through your cookie banner.

Implementation Steps

Implementing Consent Mode v2 requires coordination between your Consent Management Platform (CMP), Google Tag Manager, and your GA4/Google Ads tags. Here's the step-by-step process:

Step 1: Update Your CMP

Check if your CMP (Cookiebot, OneTrust, Usercentrics, CookieYes, etc.) supports Consent Mode v2. Most major CMPs added v2 support in Q1 2024. Contact your CMP vendor or check their documentation for the specific configuration steps. The CMP needs to send all four consent signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) to the GTM dataLayer.

Step 2: Set Default Consent State

In GTM, create a tag that sets the default consent state before any other tags fire. This tag should use the Consent Initialization - All Pages trigger (which fires before the standard "All Pages" trigger). The default state for EEA visitors should deny all consent parameters:

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

The wait_for_update parameter tells Google tags to wait up to 500ms for the CMP to load and provide the actual consent state. This prevents tags from firing with denied consent before the user has a chance to interact with the banner.

Step 3: Handle Consent Updates

When the user interacts with your cookie banner (accepting or rejecting specific categories), the CMP should push a consent update to the dataLayer. GTM then updates the consent state for all tags:

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

Step 4: Verify in GTM Preview Mode

Open GTM Preview mode and navigate your site. In the Preview panel, you should see:

1. A "Consent" tab in the tag details showing the initial consent state (all denied).
2. After interacting with the consent banner, the consent state should update to reflect the user's choices.
3. Tags should fire or remain blocked based on the current consent state.
4. All four v2 parameters (ad_storage, analytics_storage, ad_user_data, ad_personalization) should appear in the consent details.

Advanced vs Basic Consent Mode

Google distinguishes between two implementation levels:

• Basic Consent Mode: Tags are completely blocked when consent is denied. No data is sent to Google at all. This is the simpler implementation but provides no modeled data.
• Advanced Consent Mode: Tags fire in a restricted, cookieless mode when consent is denied. Google receives anonymized "pings" that enable behavioral and conversion modeling. This recovers 40-70% of the measurement data that would otherwise be lost.

For most businesses, Advanced Consent Mode is the recommended approach because it provides significantly better data quality while still fully respecting user consent choices. The cookieless pings sent in denied mode contain no personal data and cannot be used to identify individual users.

What Happens Without Consent Mode v2

If you're serving ads in the EEA without Consent Mode v2, the consequences are significant and immediate:

• Remarketing audiences stop growing: Google Ads can't add new users to your remarketing lists, causing audience sizes to shrink over time.
• Conversion data is incomplete: Without proper consent signals, conversions from EEA users may not be attributed to your campaigns.
• Smart Bidding degrades: Google's automated bidding strategies rely on conversion data. Less data means less accurate bidding and higher costs.
• No behavioral modeling: Google can't model the behavior of users who denied consent, leaving a larger gap in your analytics data.

Testing Your Implementation

After implementing Consent Mode v2, validate your setup using these methods:

1. GTM Preview Mode: Check the Consent tab for each tag to verify all four parameters are present and updating correctly.
2. Chrome DevTools Network tab: Filter by collect requests and look for the gcs parameter in the GA4 collection URL. The value should change based on consent state.
3. Google Tag Assistant: The Tag Assistant Chrome extension shows consent status for each Google tag on the page.
4. GA4 Realtime Report: Verify that events are still being received (potentially as modeled data) even when consent is denied in Advanced mode.

Key Takeaways

• Consent Mode v2 is mandatory for personalized advertising in the EEA since March 2024.
• The two new parameters (ad_user_data and ad_personalization) must be implemented alongside the existing consent signals.
• Advanced Consent Mode (cookieless pings when denied) recovers 40-70% of lost measurement data through modeling.
• Most major CMPs support v2 — check with your vendor for specific configuration steps.
• Always verify your implementation using GTM Preview Mode and Chrome DevTools before going live.