Consent Mode v2 and Enhanced Conversions in 2026: the real setup guide

Two Google features now sit at the foundation of every functional ad account in 2026: Consent Mode v2 and Enhanced Conversions. The first determines whether your data flows legally. The second determines whether the data that does flow is good enough for the bidder to learn from. Get them both wrong, and you’re flying blind in an auction that’s 12% more expensive than last year. Get them both right, and your reported conversions stabilize while your competitors’ degrade.

Most accounts I audit in 2026 are running one of them correctly. Almost none are running both correctly. This is the guide to fixing that.

What’s actually changed in 2026

Three enforcement-level changes from Google over the past 12 months that broke setups that worked fine in 2024:

1. Consent Mode v2 is now strictly enforced for traffic from the EEA, UK, and Switzerland. Ad accounts without proper Consent Mode v2 signals get audience features automatically disabled. As of March 2026 this includes Customer Match, RLSA bidding, and detailed demographics for non-consenting traffic.

2. Enhanced Conversions for Leads expanded to cover more conversion types and is now Google’s official recommended path for any account where the conversion happens after the click (B2B, services, high-consideration purchases).

3. Browser-side cookie restrictions tightened — Safari ITP, Firefox ETP, and Chrome’s partial third-party cookie deprecation collectively dropped browser-side conversion attribution by 30-50% depending on traffic mix. The gap is now too large to ignore.

If your last Consent Mode and Enhanced Conversions audit was before 2025, your account is almost certainly under-counting conversions by a material margin.

Consent Mode v2: what it actually does

Consent Mode v2 is a signaling layer between your consent banner and Google’s tags. It tells Google’s tags whether the user has granted consent for ad personalization (ad_user_data, ad_personalization) and analytics storage (analytics_storage, ad_storage).

Two operating modes:

• Basic Consent Mode: Tags don’t fire at all without consent. You lose all data from non-consenting users.
• Advanced Consent Mode: Tags still fire for non-consenting users, but without cookies — sending “cookieless pings” with no personal identifiers. Google then uses statistical modeling to estimate conversions from that anonymous traffic.

Advanced Consent Mode is the right setting for almost every account in 2026. The conversion modeling recovers 15-30% of conversions that would otherwise be lost from non-consenting traffic. Basic Consent Mode leaves that recovery on the table.

The four consent signals to pass

Consent Mode v2 expects four discrete signals:

Signal	Controls
ad_storage	Cookies for advertising purposes
ad_user_data	Whether user data can be sent to Google for advertising
ad_personalization	Whether the user’s data can drive personalized ads
analytics_storage	Cookies for analytics

Each signal should be set to granted or denied based on the user’s actual consent choice for that purpose. A consent banner that lumps “all cookies” into one toggle is no longer compliant — users must be able to grant analytics while denying advertising, and Consent Mode v2 expects to receive that granularity.

Common Consent Mode v2 setup mistakes

What goes wrong, in order of frequency:

• Default state set to granted — for EEA traffic this is non-compliant; default must be denied until the user actively consents
• Banner fires Consent Mode update too late — tags fire with the old state, conversions miss the consent signal
• The four signals are conflated — many CMPs only pass ad_storage, missing the three other required signals introduced in v2
• Test mode left on — debug signal in production data
• No URL parameter passthrough (url_passthrough: true) — gclid is lost between pageviews for non-consenting traffic, breaking the entire conversion modeling system

Tools that get the four signals right in 2026: Cookiebot, Iubenda, Termly, OneTrust, Usercentrics, Klaro. Custom-built banners almost always get at least one of the above wrong unless engineered specifically for Consent Mode v2.

Enhanced Conversions: what it actually does

Enhanced Conversions sends hashed first-party identifiers (email, phone, name, address) alongside conversion events. Google then matches those identifiers against signed-in user accounts to attribute conversions that would otherwise be lost to cross-device journeys, cookie restrictions, or non-consenting traffic.

Two flavors:

Enhanced Conversions for Web

For conversions that happen on your website — purchases, signups, form submissions. Configured via Google Tag Manager or gtag.js. Captures the user identifier (typically email from a checkout form) at the moment of conversion and passes it hashed alongside the conversion event.

Setup quality matters significantly here. Misconfigured Enhanced Conversions for Web shows in the Google Ads diagnostic as “recording” but with a low match rate (under 40%). Properly configured: 70-90% match rate. The difference is roughly 20-30% more attributed conversions on the same traffic.

Enhanced Conversions for Leads

For conversions that happen after the click — B2B sales-qualified leads, services consultations, high-consideration purchases that close offline. The flow:

1. Lead form on the site captures email
2. Email passed to Google with the conversion event (lead form submission)
3. When the lead converts to a closed deal, your CRM sends an offline conversion upload that ties the closed deal back to the original lead
4. Google attributes the closed-deal revenue back to the original ad click

Enhanced Conversions for Leads is the single highest-ROI optimization for B2B and services accounts in 2026. It’s also the one most accounts skip because the setup spans Google Ads + GTM + CRM + a daily upload job. The accounts that do set it up properly are typically running 2-3x better ROAS than competitors running on form-fill optimization alone.

The clean 2026 setup, end-to-end

For an account starting from scratch or rebuilding from a broken setup:

Step 1: Consent banner that passes proper Consent Mode v2 signals

• Default state: all four signals denied
• Banner UI: granular per-purpose toggles (advertising, analytics, personalization)
• On user choice: fire gtag('consent', 'update', {...}) with the user’s actual choices
• Set url_passthrough: true and ads_data_redaction: true in the default configuration

Step 2: Google Tag Manager configured for Advanced Consent Mode

• All Google tags (GA4, Google Ads, Floodlight) set to “wait for consent” in GTM
• Conversion linker tag firing on all pages with appropriate consent state
• Consent state debugged in Tag Assistant before going live

Step 3: Enhanced Conversions for Web enabled

• Email field captured at conversion (checkout, signup, contact form)
• Email passed via the user_data parameter on conversion events
• Hashing handled automatically by GTM or gtag — never send unhashed email
• Match rate verified at 70%+ in Google Ads conversion diagnostics

Step 4: Enhanced Conversions for Leads for any B2B / services account

• Lead form captures email and a unique conversion ID
• gclid (or wbraid/gbraid for app traffic) stored alongside lead in CRM
• Daily offline conversion upload pipes closed-deal revenue back via the OCI API
• Conversion value column populated with actual deal value

Step 5: Server-side tagging as the durable backbone

• Google Tag Manager Server-Side container running on your own subdomain
• All Google events (GA4, Ads conversion, Enhanced Conversions) routed server-side
• First-party domain mitigates Safari/Firefox cookie restrictions
• Server-side is also the foundation for first-party data activation on other platforms

Step 6: Verification and ongoing monitoring

• Google Ads conversion diagnostics weekly — Enhanced Conversions match rate, Consent Mode v2 signal coverage
• GA4 BigQuery export reviewed monthly for consent state distribution
• Conversion volume YoY tracked separately for consenting vs. non-consenting traffic
• Consent banner CMP version updated when v3 or vendor updates ship

How this connects to broader paid media performance

A correctly configured Consent Mode v2 + Enhanced Conversions stack does three things downstream that compound:

• Better conversion volume = better Smart Bidding learning. The bidder sees more conversions, learns faster, optimizes more accurately. This directly mitigates the 12% YoY CPC inflation.
• Customer Match audiences refresh from clean signal. Customer Match feeders that pull from GA4 conversion events benefit from the recovered 20-30%.
• Cross-platform attribution gets closer to truth. When Google sees more of its true conversions, your attribution stack doesn’t over-credit channels that happen to be browser-side reliable (organic, direct) at the expense of Google Ads.

Accounts that fix the data plumbing first typically see all of their other ad platforms improve too, because the upstream measurement is what was broken.

Common audit findings in 2026

The patterns I see in account audits this year, roughly ranked by frequency:

• 70% — Consent banner exists but Consent Mode v2 isn’t actually wired (signals never fire, or default to granted)
• 60% — Enhanced Conversions for Web “recording” but match rate below 40% (typically: email being passed in the wrong field, or hashed twice)
• 80% — Enhanced Conversions for Leads not set up at all for B2B accounts that should have it
• 50% — url_passthrough and ads_data_redaction not enabled, breaking conversion modeling for non-consenting traffic
• 40% — Server-side tagging configured but consent state not passed through to server
• 30% — Conversion events firing twice (browser + server) without proper deduplication

Each is a fixable issue with a measurable ROAS impact. The compound impact when all are fixed is typically a 30-50% improvement in reported conversion volume and a similar improvement in effective CPA.

A 30-day Consent + Enhanced Conversions fix project

For an account where you suspect both are misconfigured:

• Days 1-5: Diagnostic. Run Google Tag Assistant in production with debug mode. Verify the four consent signals are passing in the correct state. Check Enhanced Conversions match rate in Google Ads.
• Days 6-15: Consent banner rebuild if needed. Migrate to a v2-compliant CMP if the current one is patched together. Verify URL passthrough and data redaction settings.
• Days 16-22: Enhanced Conversions for Web. Confirm email capture at conversion. Confirm hashing handled correctly. Verify match rate climbs above 70%.
• Days 23-30: Enhanced Conversions for Leads (if applicable). Set up CRM-side offline conversion uploads. Map lead-to-deal pipeline back to Google Ads.

Expected outcome: conversion volume in Google Ads stabilizes or increases 15-30%, Smart Bidding rebalances over 2-4 weeks, effective CPA falls 10-20% as the bidder gets cleaner signal.

FAQ: Consent Mode v2 and Enhanced Conversions

Is Consent Mode v2 required outside the EEA? Strictly required only for EEA, UK, and Switzerland traffic. But Google is using it as the de facto signal for ad personalization gating globally — accounts running v2 properly get better feature access even on US traffic. Just turn it on everywhere.

Will Enhanced Conversions still work after third-party cookies are deprecated? Yes — Enhanced Conversions uses first-party hashed identifiers, not third-party cookies. It’s specifically Google’s recommended path for the post-cookie environment.

What’s the difference between Enhanced Conversions and the Conversions API for Meta? Functionally similar — both send server-side hashed identifiers to recover conversions lost to browser-side restrictions. Different platforms, different setup. Meta CAPI is the Meta equivalent.

Do I need both browser-side and server-side conversion tracking? Yes — they serve different purposes. Browser-side captures the event with full context; server-side ensures it reaches Google reliably. Deduplication keys (event_id, transaction_id) prevent double-counting.

Will my conversion volume go up or down after enabling Enhanced Conversions? Up, in almost every case. Enhanced Conversions recovers previously-lost conversions; it doesn’t create new ones. Expect 15-30% reported volume increase as the match starts working.

The honest 2026 framing

Consent Mode v2 and Enhanced Conversions aren’t optimization tactics anymore — they’re foundational plumbing. An account without them in 2026 is operating with 30-50% less conversion data than the bidder needs, paying 12% more per click than last year, and competing against accounts that have both wired correctly.

The setup takes 2-4 weeks of focused work. The payback is permanent and compounds with every other paid media investment. If only one project moves to the top of the 2026 backlog, this is it.