Consent Mode V2 for Google Ads: Setup Guide (2026)

Google Consent Mode v2 is a consent-signaling layer that adjusts how Google tags (Google Ads, GA4, Floodlight) behave based on a user's consent choices - and as of March 2024, Google requires the two new v2 signals (ad_user_data and ad_personalization) for any advertiser serving users in the EEA, UK, or Switzerland. Without Consent Mode v2 properly deployed, Google Ads loses conversion measurement, audience building degrades, and remarketing lists shrink for EU/UK/CH traffic.

Consent Mode v2 is not optional for advertisers with European traffic. Google has tied its enforcement to the Digital Markets Act (DMA) and broader EU privacy requirements. This guide covers what changed from v1, the two implementation modes (basic vs advanced), the CMP and GTM setup patterns, how to verify it is working, and the common mistakes that break measurement. For the measurement infrastructure that Consent Mode feeds, see our guides to server-side tagging and GA4 for startup marketing.

TL;DR: Consent Mode V2 Essentials

• Two new consent signals: ad_user_data (controls whether user data can be used for advertising) and ad_personalization (controls whether ads can be personalized). Both are required for EEA/UK/CH traffic.
• Basic mode: Tags load but are blocked until consent is granted. No cookies or identifiers for non-consented users. Google fills gaps with conversion modeling.
• Advanced mode: Tags fire with consent signals sent as defaults before user interaction. Google receives cookieless pings for modeling even when consent is denied.
• CMP required: You need a Google-certified Consent Management Platform (Cookiebot, OneTrust, Usercentrics, Didomi, etc.) to capture and relay consent to Google tags.
• Verify with Tag Assistant: The consent tab in Tag Assistant is the source of truth for whether your v2 signals are reaching Google correctly.

What Is Consent Mode V2?

Consent Mode is Google's mechanism for a website or app to communicate user consent choices to Google tags. When a user lands on your site and interacts with a consent banner, the Consent Mode API sends a set of consent signals (granted or denied) for each consent type. Google tags then adjust their behavior accordingly - firing with full measurement capabilities for consented users, or firing in a constrained, cookieless mode for users who denied consent.

Consent Mode v1 shipped in 2020 with four consent types: analytics_storage, ad_storage, functionality_storage, and personalization_storage. Consent Mode v2 (enforced as of March 2024) added two new consent types:

The v2 signals are the ones Google now mandates. If you deployed Consent Mode v1 but never added ad_user_data and ad_personalization, your EEA/UK/CH measurement is degraded and your audience-building is effectively broken in those regions. For a high-level comparison of how consent and server-side approaches intersect, see our guide to Meta CAPI (the same signal-to-platform pattern applies for both ecosystems).

Why Consent Mode V2 Matters for Google Ads and GA4

Without the v2 signals present, Google responds at the infrastructure level:

Consent state also gates enhanced conversions: when consent is withheld, the hashed customer data is not sent, so a correct Consent Mode v2 setup is a prerequisite for accurate enhanced conversion measurement.

• Conversion measurement drops: Google Ads and GA4 cannot reliably attribute conversions from users who declined consent. Conversion counts for EEA traffic can drop sharply without the modeling backfill that Consent Mode enables.
• Audience building breaks: Remarketing lists, Customer Match, and similar audience features stop populating for users who have not granted the new consent types. If a user visits from Germany and denies cookies, without the v2 signals that user cannot be added to any audience list.
• Personalization is blocked: Any ad feature that relies on user-level signals (Smart Bidding signals, audience targeting, ad personalization) stops functioning for non-consented users.

Google's conversion modeling - the algorithmic backfill that estimates conversions lost to consent gaps - only activates when Consent Mode signals are present, even for users who deny consent. In other words, telling Google "this user denied consent" is better than telling Google nothing, because the denial signal unlocks the modeling that fills the measurement gap.

Basic Mode vs Advanced Mode

Consent Mode v2 supports two implementation approaches. The choice depends on your legal risk tolerance and how much conversion modeling you want Google to perform.

Basic Mode

In basic mode, Google tags are blocked entirely until the user interacts with the consent banner and grants consent. No cookies, no identifiers, and no pings are sent for non-consented users. Once consent is granted, tags fire normally with full measurement. Google applies conversion modeling to estimate the conversions that were blocked during the pre-consent period, but the modeling signal is weaker because Google has no data from the non-consented users at all.

Basic mode is simpler to implement and carries lower privacy risk, but recovery of lost conversions through modeling is typically less complete than in advanced mode.

Advanced Mode

In advanced mode, Google tags fire immediately on page load - but they fire with the default consent state (typically "denied" for all types) before the user has interacted with the banner. Google receives cookieless, non-identifying pings for all users, consented or not. When a user later grants consent, the tags update with "granted" signals and full measurement begins. For users who never consent, Google still has the cookieless ping, which powers more accurate conversion modeling.

Advanced mode provides more complete measurement but requires a stronger legal basis, as tags fire (albeit in a constrained, cookieless configuration) before explicit consent. Consult your legal counsel before choosing advanced mode.

CMP Integration: Google-Certified Consent Management Platforms

Consent Mode v2 requires a Consent Management Platform (CMP) to capture user choices and relay them to Google tags. The CMP handles the consent banner UX, records user preferences, and calls the Consent Mode API to update the consent state. Google maintains a list of certified CMP partners that have been tested for v2 compatibility:

• Cookiebot (Usercentrics-owned, popular in EU markets)
• OneTrust (enterprise-grade, broad regulatory coverage beyond GDPR)
• Usercentrics (Cookiebot's parent, with its own enterprise CMP)
• Didomi (French CMP, strong in EU e-commerce)
• Commanders Act (French CDP-and-CMP hybrid, strong server-side consent support)

Most Google-certified CMPs now ship Consent Mode v2 support as a default or one-click configuration. If your CMP is not on Google's certified list, its consent signals may not be recognized, and the v2 requirements will not be satisfied - even if the consent banner looks correct to the user.

GTM Setup Pattern for Consent Mode V2

The most common deployment pattern uses Google Tag Manager (GTM) as the orchestration layer:

1. Implement the CMP template in GTM: Most certified CMPs provide a GTM community template that handles the consent-banner display and Consent Mode API calls. Install the template, configure your CMP account ID, and set the default consent state to "denied" for all consent types (including the two new v2 types).
2. Set default consent in GTM's Consent Overview: In GTM's Admin > Container Settings, enable "Enable consent overview" and set the default values for each consent type. The v2 types - ad_user_data and ad_personalization - must be present in this configuration.
3. Configure the consent update trigger: The CMP template fires a consent update event when the user makes a consent choice. GTM must have a corresponding trigger that catches this event and updates the consent state for all affected tags. Without this trigger, tags remain in their default state indefinitely.
4. Add consent checks to individual tags: In each Google tag (GA4 Configuration, Google Ads Conversion, Floodlight, remarketing), add the relevant built-in consent checks. GA4 Config tags need analytics_storage and ad_storage. Google Ads conversion tags need ad_storage and ad_user_data. Remarketing tags need ad_personalization.
5. Configure Google Ads Linker: The Ads Linker tag in GTM handles first-party cookie linking for Google Ads conversion measurement. It must be configured to respect consent signals so it does not set cookies for non-consented users.

Verifying Consent Mode V2 Is Working

Three verification checkpoints:

1. Tag Assistant (tagassistant.google.com): Connect your site, click the "Consent" tab in the Tag Assistant interface. This tab shows every consent signal sent to Google, the default state on page load, and any updates triggered by user consent choices. If ad_user_data and ad_personalization are not visible in this tab, Consent Mode v2 is not deployed correctly.
2. Google Ads diagnostics: In Google Ads > Tools > Diagnostics, look for consent-related warnings. Google Ads surfaces alerts when consent signals are missing for campaigns targeting EEA/UK/CH regions.
3. Browser DevTools: Open the Network tab in your browser's DevTools, look for requests to googleadservices.com or doubleclick.net, and inspect the URL parameters. Consent signals are passed as gcd (Google Consent Default) and gcs (Google Consent State) parameters on tag requests. If these are missing, the tags are firing without consent information.

Common Consent Mode V2 Mistakes

• Default = granted: Setting the default consent state to "granted" for all consent types violates GDPR and equivalent regulations. The default must be "denied" until the user actively opts in. Google's enforcement explicitly checks for this.
• No CMP or un-certified CMP: Without a Google-certified CMP relaying v2 signals, Consent Mode is effectively absent regardless of what other infrastructure is in place.
• Missing the v2 signals: The most common issue is deploying Consent Mode with only the v1 consent types (analytics_storage, ad_storage) and never adding ad_user_data and ad_personalization. The deployment looks functional but Google Ads measurement and audiences degrade silently for EEA/UK/CH traffic.
• Incomplete tag coverage: Adding consent checks to GA4 but not to your Google Ads conversion tags leaves the ads-side measurement gap completely unaddressed. Every Google tag that handles user data must have the corresponding v2 consent checks.
• Ignoring the Ads Linker: The Google Ads Linker tag in GTM handles first-party cookie-based conversion linking. Without consent-aware configuration, it continues setting cookies for non-consented users, which violates the consent signals you are otherwise correctly sending.

For a broader view of attribution methodology choices that depend on clean consent signals, see our first-touch vs last-touch attribution comparison.

Consent mode is one piece of a larger shift. Our third-party cookie deprecation migration checklist shows how it fits with first-party data and server-side tracking.

Frequently Asked Questions

What Is the Difference Between Consent Mode V1 and V2?

Consent Mode v1 (2020) covered four consent types: analytics_storage, ad_storage, functionality_storage, and personalization_storage. v2 added two new types - ad_user_data (controls whether user data goes to Google for advertising) and ad_personalization (controls whether ads can be personalized). Google enforces these v2 signals for EEA, UK, and Switzerland traffic as of March 2024.

Is Consent Mode V2 Required for All Google Ads Accounts?

It is required for any Google Ads account targeting or receiving traffic from users in the EEA, UK, or Switzerland. If your campaigns do not reach those regions, Consent Mode v2 is not enforced, though deploying it regardless is recommended for future-proofing.

What Happens If I Do Not Deploy Consent Mode V2?

Google Ads conversion measurement degrades for EEA/UK/CH traffic, audience building stops populating from non-consented users, and remarketing lists shrink. Google also surfaces compliance warnings in the Ads dashboard and may restrict ad serving to users in those regions.

Which Cmps Support Consent Mode V2?

Google-certified CMPs including Cookiebot, OneTrust, Usercentrics, Didomi, and Commanders Act all support Consent Mode v2. Most provide GTM community templates and one-click v2 configuration. Verify your CMP is on Google's certified partner list before relying on it for compliance.

Should I Use Basic or Advanced Consent Mode?

Advanced mode sends cookieless pings for non-consented users, which powers more complete conversion modeling, but requires a stronger legal basis because tags fire before explicit consent. Basic mode blocks all tags until consent is granted, which is simpler legally but provides less measurement recovery. The choice depends on your legal risk tolerance and how much measurement completeness you need. Consult legal counsel for your specific jurisdiction.

Key Takeaways

• Consent Mode v2 adds ad_user_data and ad_personalization - both now required by Google for EEA/UK/CH traffic.
• Without it, conversion measurement, audience building, and remarketing degrade for European traffic in Google Ads and GA4.
• Deploy through a Google-certified CMP with GTM as the orchestration layer. Set defaults to "denied" and relay consent updates via the Consent Mode API.
• Verify with Tag Assistant's Consent tab. If ad_user_data and ad_personalization are absent, v2 is not working.
• Choose basic mode for simpler compliance, advanced mode for stronger measurement. Do not set defaults to "granted."