Consent Mode v2 Explained: Everything Website Owners Should Know

Consent Mode v2 is the framework that tells Google's tags, GA4, Google Ads, Floodlight, how to behave based on what a visitor actually agreed to. Mandatory since March 2024 for EEA and UK traffic, it's the reason your tags don't have to choose between full data collection and full compliance.

Without it, a visitor who declines cookies gives you nothing at all. With it, Google can still model conversions from cookieless, non-identifying signals, recovering a real share of the data you'd otherwise lose entirely.

Here's what it actually does, the two implementation levels, and the mistakes that quietly break it even when Tag Assistant shows green.

01Consent Mode v2 Explained Simply

YeezyPay's guide defines it precisely: it's a signaling framework that tells Google's tags how to behave depending on what a user has consented to, working through four parameters, two original and two added specifically in v2.

Osano's guide adds an important clarification: consent mode itself doesn't provide a consent banner or widget. It interacts with your CMP, whichever one displays the cookie banner and records choices, and translates those choices into signals Google's tags can actually read.

02Why This Became Mandatory

Digital Applied's May 2026 guide traces the actual legal driver: it's the EU's Digital Markets Act, not GDPR directly. The EU designated Google a gatekeeper in late 2023, triggering a March 6, 2024 compliance deadline that made all four consent signals mandatory for continued access to Google Marketing Platform advertising features in the EEA.

The same guide notes a separate, related obligation worth knowing: since January 16, 2024, publishers using Google AdSense, Ad Manager, or AdMob to serve ads to EEA and UK users must also use a Google-certified consent management platform, a distinct requirement that often lands on the same team at the same time.

03Basic Mode vs Advanced Mode

CookieScript's guide draws the practical line clearly: in Basic Mode, all tags stay blocked until consent is given, meaning zero data and zero modeling if a visitor declines. Advanced Mode lets tags load in a cookieless, denied state, sending anonymized pings that feed Google's modeling algorithms instead.

ConsentPixel's guide states the mainstream recommendation directly: Advanced Mode is preferred by most implementations, since it preserves conversion modeling for every opt-out visitor rather than losing that signal entirely. If your account relies on value based bidding, this modeled data is exactly what keeps Smart Bidding functioning for consent-declined users.

04The Four Required Parameters

CookieNox's guide breaks down what each one actually controls: ad_storage and analytics_storage were part of the original version. ad_user_data, new in v2, controls whether user data can be sent to Google for advertising purposes, and ad_personalization controls whether data can be used for personalized remarketing.

ConsentPixel's guide, referenced above, is blunt about a common shortfall: implementing only the original two parameters is not sufficient. Many sites and CMPs still miss ad_user_data and ad_personalization entirely, which is not a compliant v2 implementation.

05What Breaks When It's Missing

YeezyPay's guide, referenced above, lays out the practical fallout with real numbers: Search Network RLSA audiences require 1,000 active users, Display Network requires 100, and Lookalike segments in Demand Gen need a 1,000-user seed list. Without proper consent signals, these audiences quietly shrink until they no longer meet minimum size requirements.

This connects directly to what our Demand Gen campaigns guide covers, without functioning Consent Mode v2, Demand Gen campaigns relying on Lookalike audiences simply can't run for affected users.

06How to Set It Up

Usercentrics' guide outlines the common path: connect your consent banner to Google's tag infrastructure so choices pass through automatically, add a few lines to your Google Tag Manager setup to initialize Consent Mode before any tags fire, and confirm your CMP has Google Consent Mode enabled, usually a toggle rather than custom code.

Google's own developer documentation is specific about sequencing: define the default consent state before any user interaction, then update that state based on the visitor's actual choice, ensuring updates are tracked before any page transitions occur.

07Basic Implementation Example

Here's the core structure of setting default consent state before your tags load, following Google's own recommended pattern.

// Place BEFORE your GA4/Google Ads tag loads
gtag('consent', 'default', {
  'ad_storage': 'denied',
  'analytics_storage': 'denied',
  'ad_user_data': 'denied',
  'ad_personalization': 'denied',
  'wait_for_update': 500
});

// After the visitor makes a choice via your CMP:
gtag('consent', 'update', {
  'ad_storage': 'granted',
  'analytics_storage': 'granted',
  'ad_user_data': 'granted',
  'ad_personalization': 'granted'
});

08Implementation Checklist

A short list to confirm before assuming your setup is actually compliant.

09Is Your Consent Mode v2 Setup Actually Working?

Answer a few quick questions to check your current implementation.

10FAQs on Consent Mode v2