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

READING ROOM › SYMPTOM FILES › SYM-024

SYMPTOM FILE SYM-024 FILED 05 NOV 2026 · REVISED 21 NOV 2026

Consent Mode v2 basic vs advanced: which one costs you conversions.

ALSO FILED AS
  • “Consent Mode v2 basic vs advanced”
  • “basic vs advanced consent mode”
  • “does basic consent mode lose conversions”
  • “should I use basic or advanced consent mode”
  • “how to tell if consent mode is basic or advanced”
  • “advanced consent mode cookieless pings”
  • “switch from basic to advanced consent mode in GTM”

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

Basic Consent Mode blocks Google’s tags until the visitor answers the banner. Advanced loads them with consent denied and sends cookieless pings: small signals with no cookies attached. Basic costs more conversions, but only from visitors who decline. Google estimates the sales it can’t see, and in basic that estimate is rougher in Google Ads and missing in GA4. Visitors who accept are measured the same in both.

So the mode decides how much of the declined slice comes back as modelled conversions. It doesn’t decide whether your set-up works. A banner whose answer never reaches the tags loses consented sales too, in either mode, and that is F-201 . If your conversions fell when the banner went live and you want to know how much of the fall is normal, start with Conversions dropped after implementing Consent Mode v2. This note answers one question: basic or advanced.

BasicAdvanced
Google tags before the visitor answersBlockedLoad, consent denied by default
Visitor declinesNothing sent, not even the consent stateConsent state and cookieless pings
Visitor acceptsFull measurementFull measurement
Google Ads modelling of declined salesGeneral modelModel built on your account
GA4 modelling of declined visitorsNot possiblePossible; thresholds necessary, not sufficient
CONSENT MODE · what Google receives in each mode · summarised from Google's consent mode documentation, read 5 November 2026

Two things, both from visitors who decline.

Google Ads models their sales with less to go on. Google describes the basic-mode model as “general” and “less detailed”, and the advanced-mode model as specific to the advertiser. In basic, Google learns nothing from your declined visitors, so it can only estimate them from patterns outside your account.

GA4 loses them outright. Google says cookieless pings are what enable GA4’s behavioural and conversion modelling, and its modelling requirements ask for Google tags that load before the consent dialog appears, in all cases. Basic sends no pings. Declined visitors, their sessions and their purchases are absent from GA4, with no estimate to fill the gap.

Two things basic doesn’t cost you. Remarketing audiences: ad_personalization is the consent for personalised advertising, and modelling estimates conversions, not people, so neither mode puts a visitor who declined into an audience. Enhanced Conversions: Google turns off the hashed customer data whenever ad_user_data is denied, whatever the mode (F-402 ).

How much is the difference worth on your account?

The ceiling is the sales of your declined visitors, not your decline rate. Your decline rate is in your consent platform’s dashboard (the accept and reject report). Google’s own modelling page notes that visitors who consent are typically two to five times more likely to convert than those who don’t. So a 20 per cent decline rate usually puts well under 20 per cent of sales in play, and advanced recovers part of that slice, not all of it.

Volume is the second limit. Google Ads models conversions for consent mode only once an account reaches 700 ad clicks over 7 days, per country and domain grouping, and then trains before anything appears. Google doesn’t say whether the general model in basic has the same floor. My working rule: if a country’s campaigns sit well under that threshold and the decline rate is low, the switch can wait.

Above it, you can measure what advanced adds. In Google Ads, Goals, Summary, choose All conversions, select the conversion action, then open its Diagnostics tab. Google reports the uplift as modelled conversions divided by observed ones, per domain and country, refreshed weekly. It can appear from about 7 days after implementation, it stays visible for 4 weeks after modelling starts, and uplift under 1 per cent isn’t shown. If that tab shows no status or no uplift table, the usual reasons are covered in Consent Mode v2 modelled conversions: why Google Ads isn’t showing any.

Which mode am I running?

Two minutes, Chrome, no developer needed.

  1. Open the site in a fresh incognito window, from the UK or EEA (or a VPN there). Elsewhere a default scoped to those regions correctly gives granted. Don’t touch the banner.
  2. Open DevTools, Network, and filter for collect.
  3. Read what you see before answering the banner:
    • Nothing appears in the list until you click accept: basic, provided the requests after accept carry gcs=G111. No gcs even after accept means the tags are blocked with no Consent Mode at all.
    • Requests carrying gcs=G100: advanced. G100 means advertising and analytics storage both denied, and it only appears in advanced mode.
    • Requests carrying gcs=G111, or no gcs at all: the tags aren’t waiting for consent. That isn’t a mode, it’s F-201 .
  4. Reject, then keep browsing. Advanced keeps sending G100 hits. Basic stays silent.

gcs sits in the request URL: click the request and read the Payload tab. Google doesn’t document its values and they can change, so treat it as a quick read and confirm in Tag Assistant’s Consent tab. If DevTools isn’t your thing, this is a two-minute job for whoever runs your tags.

In Google Tag Manager the same answer sits in the tag settings. Google tags (GA4 and Google Ads) set to “Require additional consent for tag to fire”, or fired only by a consent-accepted event, mean basic. Google tags left on their built-in consent checks, behind a default set on the Consent Initialization trigger, mean advanced. One exception overrides the tag settings: if the consent platform blocks the Google tag or the whole GTM container until consent, you are in basic whatever the tags say, and the DevTools check is the one to trust. Consent platforms don’t all start in the same mode. The defaults for four of them are in Cookiebot vs CookieYes vs Usercentrics vs Complianz.

When whoever owns your privacy policy decides nothing should reach Google before a yes. Google’s setup guide leaves that choice to “your company’s guidelines”. The cookieless pings set no cookies, but they do carry a timestamp, the browser’s user agent, the referrer, the consent state, a random number per page load and whether an ad click id was in the URL. Make the decision once, on purpose, and write down who made it.

Where a meaningful share of visitors decline, roughly one in six or more, and the account clears Google’s threshold, I set up advanced. Modelling needs data to work from. Advanced gives it some.

How to switch from basic to advanced in GTM

  1. Set the default. On the Consent Initialization trigger, set all four signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) to denied, scoped by region to the UK (GB) and the EEA, with wait_for_update around 500 milliseconds so the banner can answer first.
  2. Release the Google tags. On the GA4 and Google Ads tags, remove the additional consent requirement and replace any consent-accepted trigger with the normal one. Google’s tags have built-in consent checks and adjust themselves to the signals.
  3. Keep everything else gated. Meta, TikTok and other non-Google tags don’t read Consent Mode. They keep their additional consent check, or advanced mode sends them visitors who declined.
  4. Fire the update on the answer for all four signals, accept and reject, and on return visits.
  5. Re-run the check above. G100 before you answer, G111 after accept, G100 hits continuing after reject.

If you hand the switch to someone else, steps 1 to 5 are what a Consent Mode v2 implementation should cover, and the step 5 result for accept and reject is what you should get back in writing.

Running a server container? The server-side half is in Consent Mode v2 with server-side GTM.

What neither mode fixes

If step 3 showed G111 from the UK, or no gcs at all, the mode isn’t your problem. Choosing a mode is the smaller decision. A default that loads after the tags, an update that never fires, or a region list that misses GB costs consented sales as well as declined ones, and it looks the same in basic or advanced. That is filed under F-201 , with the Tag Assistant checks to prove it. Recovering matches for the visitors who accepted is F-402 .

Common questions

Basic blocks Google’s tags until the visitor answers the banner; advanced loads them with consent denied and sends cookieless pings. Basic loses more, and only from visitors who decline: they send Google nothing, so Google Ads models those sales with a general model and GA4 can’t model them at all. Advanced sends cookieless pings while consent is denied, which lets Google Ads build a model on your own account’s data and makes GA4 behavioural modelling possible. Visitors who accept are measured the same way in both.

From the UK or EEA, open the site in a fresh incognito window, don’t touch the banner, and filter Chrome DevTools, Network, for collect. No request to Google Analytics until you accept, then requests carrying gcs=G111, means basic. Requests before you answer carrying gcs=G100 mean advanced. Requests before you answer carrying G111, or no gcs at all, mean the tags aren’t waiting for consent: a wiring fault, F-201 , not a mode. Google doesn’t document gcs values, so confirm in Tag Assistant’s Consent tab.

Yes, if all four signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) reach the tags. Google documents both basic and advanced as Consent Mode set-ups. The choice between them is about modelling, not about whether Google accepts the set-up. Basic gives Google Ads a general model for declined visitors; advanced gives it one built on your account.

Will switching to advanced bring my conversions back straight away?

No. Google Ads models only once an account reaches 700 ad clicks over 7 days per country and domain grouping, then trains before modelled conversions appear in the Conversions column. GA4 needs at least 1,000 denied events a day for 7 days and 1,000 consented daily users on 7 of the previous 28 days; Google says meeting those doesn’t guarantee eligibility and training can take longer. Google Ads shows the result as an uplift in the action’s Diagnostics, from about 7 days after implementation.

Do cookieless pings contain personal data?

Google says they set no cookies and carry a timestamp, the user agent, the referrer, the consent state, a random number per page load and whether an ad click id was in the URL. Whether that is acceptable before a visitor answers is a decision for whoever owns your privacy policy. Google’s own setup guide tells you to check your company’s guidelines when picking basic or advanced.

The wider picture, with every Consent Mode question in one place, is in Google Consent Mode v2 explained.

Sources

Read on 5 November 2026:

  • Google tag platform, consent mode overview (basic blocks Google tags until the visitor interacts with the banner; nothing sent before consent, not even the default state; advanced loads tags with denied defaults; general versus advertiser-specific model; what cookieless pings contain; ad_user_data and ad_personalization definitions; ad_user_data denied turns off hashed data for enhanced conversions)
  • Google Analytics Help, consent mode in Google Analytics (cookieless pings enable behavioural and conversion modelling; basic doesn’t get modelled data for declined users)
  • Google Ads Help, about enhanced conversions (hashed first-party data from consented users)
  • Google Ads Help, about consent mode (basic versus advanced comparison; “general model (less detailed modeling)” versus “advertiser-specific model (more detailed modeling)”; impact results after 7 full days)
  • Google Ads Help, about consent mode modelling (700 ad clicks over 7 days per country and domain grouping; training period; modelled conversions in the Conversions column; consented users typically two to five times more likely to convert)
  • Google Ads Help, about consent mode impact results (uplift is modelled divided by observed conversions; per domain and country; weekly; shown for 4 weeks after modelling starts; under 1 per cent not shown; Goals, Summary, Diagnostics)
  • Google Analytics Help, behavioural modelling for consent mode (1,000 denied events a day for 7 days; 1,000 consented daily users on 7 of the previous 28 days; tags must load before the consent dialog, in all cases; training can take longer)
  • Google tag platform, set up consent mode on websites (check your company’s guidelines to pick an implementation; region-specific defaults; wait_for_update)
  • Tag Manager Help, consent configuration (built-in consent checks; “Require additional consent for tag to fire”)
  • Simo Ahava, Consent Mode V2 for Google tags (gcs values G100 to G111; G100 only possible in advanced mode; gcs and gcd are internal parameters that can change)

← back to the reading room