Skip to content
whitead

Consent Mode v2

glossary google ads updated 2026.04.29 5 min read
// contents · 9 sections
  1. What Consent Mode v2 does
  2. Basic vs Advanced mode
  3. Who must implement it
  4. Common misconceptions
  5. "Consent Mode v2 is for the EU only, right?"
  6. "Does Consent Mode v2 replace my consent banner?"
  7. "What about CCPA — does it cover California?"
  8. Related concepts
  9. Sources

Consent Mode v2 is Google's API for sending granted/denied consent signals to Ads, GA4, and Floodlight, unlocking conversion modeling on EEA/UK/CH traffic.

Consent Mode v2 defines four boolean signals — ad_storage, ad_user_data, ad_personalization, analytics_storage — that your banner sets to granted or denied per visitor, and that Google's tags read before firing. The two new v2 signals (ad_user_data, ad_personalization) were added to comply with the EU Digital Markets Act and Google's "EU user consent policy".

Google Ads Help defines the runtime behaviour:

"When consent mode is implemented, your tags will dynamically adapt, only utilizing measurement tools for the specified purposes when consent has been granted by your users."
— Google Ads Help: About consent mode, retrieved 2026-04-29

When a signal is denied, tags do not write cookies — instead they send cookieless "pings" (timestamp, page URL, consent state) that feed Google's behavioural conversion modeling, so reports keep approximating reality when 60-70% of EEA visitors decline cookies.

Basic vs Advanced mode

The choice between Basic and Advanced is the biggest measurement decision an EEA advertiser makes in 2026 — and it is invisible until you check.

Dimension Basic Advanced
When tags load Only after consent granted Always, with denied state
Cookieless pings on denial No Yes
Modeling recovery None — modeling needs the pings +15-25% conversions recovered (Google Ads Help, 2024)
Modeling loss vs Advanced ~40% modeling capacity lost (Simo Ahava, 2024) Baseline
Remarketing on denial 0 Modeled extension
Fits when Strict legal review forbids pre-consent network calls Any advertiser optimising conversion completeness

Most agencies ship Basic by default because CMPs — Cookiebot, Usercentrics, OneTrust — pre-configure it. Switching to Advanced is a CMP setting plus a Tag Manager change (~1 hour) and is the highest-ROI measurement fix in any post-enforcement EEA audit.

Who must implement it

Consent Mode v2 is mandatory for any Google advertiser whose traffic touches the EEA (27 EU states plus Iceland, Liechtenstein, Norway), UK, or Switzerland, and who uses Google Ads remarketing, Customer Match, or measurement features (conversion tracking, GA4, Floodlight). It took effect 2024-03 alongside the DMA compliance deadline.

Enforcement is the inflection point. Google's EU user consent policy requires advertisers to collect explicit consent before personal data flows into measurement and remarketing — non-compliant accounts now see remarketing audiences, conversion tracking, and demographic reporting silently degraded on EEA/UK/CH traffic.

Outside those jurisdictions Consent Mode v2 is not legally required, but Advanced still benefits any market with a consent banner — California (CCPA/CPRA), Brazil (LGPD), Canada (PIPEDA), Australia. The modeling lift travels.

What we see across EEA accounts post-enforcement: roughly three in four advertisers have "Consent Mode v2" enabled in their CMP, but two in three of those are running Basic — they pass compliance while leaving modeling recovery on the table. Vendors ship Basic as the default template, marketing ticks "enabled", the developer never sees the toggle to Advanced. Diagnostic is fast — open GA4 DebugView with cookies declined and look for gcs=G100 (Basic) versus gcs=G110 (Advanced). Accounts flipped to Advanced typically see EEA conversion volume recover 15-25% within two weeks — pure measurement recovery, no change in user behaviour.

Common misconceptions

No — the legal scope is EEA, UK, and Switzerland (UK and Switzerland sit outside the EU). Google enforces them identically. Technically you can — and should — run Advanced on any market with a consent banner; the modeling lift is jurisdiction-agnostic.

No. The banner still collects the consent decision — Consent Mode v2 is the wire protocol that carries it into Google's tags. You need both: a CMP for the user-facing prompt, and Consent Mode v2 wired into GTM or gtag.js. Certified Google CMP partners ship the wiring out of the box.

"What about CCPA — does it cover California?"

Partially. Consent Mode v2 carries ad_user_data and ad_personalization signals that map onto CCPA/CPRA opt-outs, plus a gpc=1 parameter from Global Privacy Control. Advanced is the right substrate for CCPA, but the CMP must be configured to populate the US signals — most EEA-default templates do not.

Sources

← Back to Wiki