TRACKING SPECIALIST — BARIS ASA · LONDON
Synctag
Start the check → TRACKING SPECIALIST — BARIS ASA · LONDON

READING ROOM › FIELD NOTE › NOTE-035

NOTE-035 · FIELD NOTE FILED 13 NOV 2026 · REVISED 21 NOV 2026 F-201

Google Consent Mode v2 explained: basic vs advanced, what it changes in GA4 and Ads, and how to check it.

ABSTRACT — Consent Mode v2 passes the visitor's cookie choice to Google's tags. Basic blocks them until the visitor answers; advanced loads them with consent denied and sends cookieless pings. What each does to GA4 and Google Ads, what it does not do, and a five-minute check.

Baris Asa, tracking consultant, London · Last checked: 13 November 2026

Google Consent Mode v2 is how your cookie banner tells Google’s tags what the visitor agreed to, so the tags behave to match. It does not show a banner and it does not make you compliant. Basic mode blocks Google’s tags until the visitor answers; advanced loads them with consent denied and sends cookieless pings that let GA4 and Google Ads estimate the sales they cannot see. Which mode you run decides how much of the declined share is estimated. v2 added two signals, ad_user_data and ad_personalization, to the original two. A wiring fault can cancel that, whichever mode you pick.

If you came here because conversions fell when the banner went live, the number to compare is your shop’s orders against GA4 or Google Ads for one closed week. Some gap is normal once visitors can say no. A step down in the week the banner launched points to wiring, F-201 , and the conversion drop note separates the two.

This page is the map. Each question has its own note, linked where it comes up. No partnership, affiliate or commission arrangement with any consent tool named here.

Google’s description: consent mode passes your users’ consent status to Google, and tags adjust their behaviour to match (Google Ads Help: about consent mode). Your own banner collects the choice. Consent Mode relays it.

Google’s tag documentation lists seven consent types. Four do the work for GA4 and Google Ads (Google: consent mode overview):

TypeWhat denied does
analytics_storageAnalytics stops reading and writing first-party analytics cookies
ad_storageNo new advertising cookies written, existing ones not read
ad_user_dataTurns off user_id and hashed first-party data for enhanced conversions
ad_personalizationTurns off remarketing in Google Ads and Display & Video 360

The last two are what “v2” added. For EEA traffic, Google’s EEA page says advertisers must follow its EU user consent policy, collect consent and share the signals to keep using measurement, personalisation and remarketing (Google Ads Help: consent mode updates for the EEA). It names the EEA and says nothing about the UK, so what you owe UK visitors is a question for whoever advises on your cookie obligations. How to set the defaults for GB in practice: the setup order note.

What is the difference between basic and advanced?

BasicAdvanced
Google tags before the visitor answersBlockedLoad, consent denied by default
Visitor declinesNothing sentConsent state and cookieless pings
Visitor acceptsFull measurementFull measurement
Ads modelling of declined salesGeneral modelModel built on your account
GA4 modelling of declined visitorsNot possiblePossible, thresholds apply

Google: in basic, “no data is transferred to Google at all” when the visitor does not consent. Cookieless pings in advanced carry a timestamp, user agent, referrer, whether an ad click was in the URL, a boolean consent state and a random number per page load (Google: consent mode overview).

Which to pick, and how to tell which one you run from a test window: basic vs advanced, which one costs you conversions. Pings before an answer are a privacy-policy decision as much as a tag one.

Three things, per Google (Analytics Help: consent mode):

  • Cookies stop. With analytics storage denied, GA4 does not read or write first-party analytics cookies. GA4 cannot use its own cookie to link that visitor’s visits.
  • Pings fill some gaps. In advanced mode, cookieless pings let GA4 use conversion modelling and behavioural modelling. In basic mode, Google says GA4 gets no behavioural modelling for users who decline.
  • Google Signals stops for that traffic. With advertising storage denied, Signals “will not accumulate data for this traffic”.

Behavioural modelling has thresholds: Google’s page sets at least 1,000 denied events a day for 7 days and 1,000 consented daily users on 7 of the last 28 days, and says meeting them does not guarantee eligibility (behavioural modelling). Google says meeting them does not guarantee modelling, and low-volume sites commonly will not meet them, so plan on observed data only. Google also says GA4 cannot model when consent is collected through the IAB TCF. Which GA4 reports then show declined visitors, and which never do: GA4 events missing for visitors who decline cookies.

Declined sales can be modelled. Google Ads needs 700 ad clicks over 7 days per country and domain grouping, then a training period, before modelled conversions show in the Conversions column (Google Ads Help: consent mode modelling). Google says basic is “based on a general model” and advanced “provides an advertiser-specific model” (about consent mode). The 700-click threshold applies to both. If the account is past it, consent mode has been running for 7 days or more and you still can’t find any modelled conversions, there is no separate column to look for; where modelled conversions show up in Google Ads, and why they may not yet walks through the Diagnostics messages.

Two more effects to know. With ad_user_data denied, enhanced conversions have no hashed data for that visitor (setup method). With ad_personalization denied, that visitor stays out of remarketing.

  • Show a banner or decide your legal position. Google’s EEA page says advertisers must collect consent from EEA end users and share the signals.
  • Control Meta, TikTok or other non-Google tags. Those need their own consent check in the container: Cookiebot and GTM wrong consent state.
  • Fix a wrong setup. If tags fire before the default, or a region row misses GB, you lose consented sales as well. Whether your CMP’s template covers it: consultant or CMP setup.
  • Reach the server by itself. With server-side GTM the setup stays in the web container: Consent Mode v2 with server-side GTM.

Five minutes, per Google’s own check (Tag Manager Help: verify consent mode implementation):

  1. Open your site in Tag Assistant from a region where your default is denied, and accept all on the banner.
  2. Open the earliest Consent event. The four parameters should be set, and the Consent tab’s “On-page Default” column should show Denied.
  3. Open the latest Consent event. “On-page Update” should show Granted.
  4. In the Tags tab, each tag should have fired or been blocked as your settings say.
  5. In Google Ads, open the conversion action’s Diagnostics tab and look for “Consent mode is implemented”. Google lists two statuses, “Consent mode is implemented” and “Consent mode is implemented and modeling is active”, and says either can take 48 hours, sometimes 2 weeks, to appear.

If step 2 shows no default, or a tag read consent before one was set, that is F-201 . The full walk-through with failing examples: how to check Consent Mode v2 is working.

Where to go next

Your questionRead
Conversions fell when the banner went liveWhat is normal and what is a fault
Basic or advancedWhich one costs you conversions
Building it in GTMDefaults, region, wait, update
Cookiebot says it is on but tags misbehaveWrong consent state
What a review should hand backConsent Mode v2 audit
Want it set up or repairedConsent Mode service

Agencies can bring me in under their own name through white-label.

Sources

Read on 13 November 2026:

— B.A., filed from London

CONNECTED RECORDS F-201

REVISION HISTORY — revised 21 NOV 2026.

← back to the reading room