Skip to content
TAGBRUT

Consent Mode v2: basic or advanced, and how do you fix tracking after a cookie banner change?

Guide7 min readUpdated November 4, 2026

In short

Consent Mode v2 passes each visitor's cookie choice to Google through four signals: ad_storage, analytics_storage, ad_user_data and ad_personalization. In basic mode, Google tags wait for that choice: nothing is sent before it, or after a refusal. In advanced mode, they load on arrival and send cookieless measurements while the visitor declines. Google Ads and GA4 can then model part of the declined conversions. At TAGBRUT, we deploy advanced mode, with the default consent state set to denied before Google Tag Manager loads.

In this guide

Basic or advanced mode: what changes

Basic modeAdvanced mode
When Google tags loadAfter the visitor's choiceOn arrival, with the default set to denied
Before the choice and after a refusalNo data sent, not even the consent stateCookieless measurements that carry the consent state
Google Ads conversion modelingGeneral model, less detailedModel specific to your account, more detailed
GA4 behavioral modelingNo: GA4 requires tags to load in every casePossible once volume thresholds are met
Main riskBidding that learns from a fraction of your trafficA default set too late, letting cookies through before the choice

Modeling does not switch on for every account. In Google Ads, you need 700 ad clicks over 7 days, per country and domain grouping. In GA4, you need at least 1,000 events per day with consent denied, for 7 days. You also need 1,000 users per day who accept, on at least 7 of the last 28 days. Below these levels, modeling will not close the gap between Google Ads and GA4.

Advanced mode is still a compliance decision: cookieless measurements are sent before the visitor chooses. Have it approved by your data protection officer (DPO) or legal counsel, just like the banner wording.

After a banner change: six checks

A new banner, a consent management platform (CMP) update or a caching plugin is enough to break the chain. Conversions drop with no error message. Six checks will show it.

  1. The default state comes before any Google tag. In Tag Assistant, the default consent state must appear before the container loads, with no warning that a tag read the consent state before a default was set. A default set by a Custom HTML tag in GTM arrives too late: it must sit on the page, before the GTM snippet, or go through the CMP's official template.
  2. Every request carries the consent state. In the Network tab, the gcs parameter of GA4 requests reads G100 when everything is denied and G111 after acceptance. The gcd parameter encodes the state of all four signals, including ad_user_data and ad_personalization. The letter l marks a signal that was never set. Our gcs and gcd decoder translates these values signal by signal.
  3. Refusal is respected. After "Reject all", in a browser with every cookie for the domain cleared, no _ga or _gcl_au cookie should appear.
  4. Acceptance updates the state on the page. Requests sent after the "Accept" click must switch to G111, without waiting for the next page.
  5. The default covers every region. A default limited to the list of European Economic Area countries can miss territories with their own region codes, such as the French overseas departments (RE, GP, MQ, GF). GDPR still applies there.
  6. The gap is measured before and after. Compare Google Ads clicks with GA4 sessions by landing page, and conversions over the two weeks before and after the change. It is the only way to put a number on what the banner cost you.

What we found at a B2B SaaS company

An e-voting software company, generating B2B leads, believed it was compliant: the banner was in place, and so was Consent Mode. Yet 64% of Google Ads clicks opened no GA4 session. Consent Mode ran in basic mode, and consent came too late on the landing page. We moved to advanced mode, with the default set before GTM, and rewired 14 tags to fire from the landing page. Modeling of declined conversions is possible again: bidding now learns from all the traffic.

Read the full case study

Frequently asked questions

Is Consent Mode v2 mandatory?

The law requires you to collect consent; Consent Mode v2 is a Google requirement. For users in the European Economic Area, the UK and Switzerland, Google asks you to pass their choices on to it. Consent Mode v2 is the intended way to do so: without these signals, Google restricts the use of its tags for measurement, remarketing and personalization for that traffic. Elsewhere, Google does not require it, but local law may still require a cookie banner.

Why did my Google Ads conversions drop after a new cookie banner?

Often for one of these reasons: a missing default consent state, or one set after tags load; an unintended switch to basic mode; a banner deferred by a caching plugin; or banner categories mapped to the wrong signals. To isolate the cause, check in Google's Tag Assistant that the default state comes before the tags, then read the gcs and gcd parameters of requests after a refusal and after acceptance. Then compare conversions over the two weeks before and after the change.

Do Cookiebot, OneTrust, Didomi or Axeptio work with Consent Mode v2?

Yes. These banners can pass all four signals, provided the Consent Mode option is enabled and each banner category is mapped to the right signal. The setting lives in the banner, but it has to be checked on the page, request by request. For non-Google tags such as the Meta pixel, the banner relies on its list of allowed vendors, not on ad_storage.

How many conversions do you lose with basic Consent Mode?

It depends on your refusal rate and your user journey. In France, the cookie refusal rate reported by internet users reached 39% in June 2022 (IFOP surveys for the CNIL, the French data protection authority). In basic mode, these visitors are invisible to Google, which can only apply a general model. At a B2B SaaS company audited by TAGBRUT, 64% of Google Ads clicks opened no GA4 session: not a conversion loss as such, but the share of traffic nobody was measuring. Advanced mode does not recover everything: modeling requires minimum volumes.

Does Consent Mode v2 cover Meta, LinkedIn and Microsoft Ads?

No. Consent Mode only controls Google tags. Meta and LinkedIn tags must be made conditional on the banner choice, in Google Tag Manager or in the banner itself. Microsoft Ads has its own consent mode for its UET tracking tag. Note that the UET tag's "insights" option loads Microsoft Clarity, which sets its own cookies.

When to call in an expert

  • Your conversions dropped after a change of banner, CMS or caching plugin, with no other explanation.
  • The gap between Google Ads clicks and GA4 sessions is large, and you cannot explain it page by page.
  • Your banner comes from a WordPress plugin, loads late, or loads after GTM.
  • Meta, LinkedIn or Microsoft Ads must follow the same choice as Google tags.
  • Your site is a single-page application, where every screen change must carry the right state.

The diagnosis is free: you get the gap quantified page by page and the list of fixes, in writing, within 2 business days of account access.

For a first check in two minutes, test your site with the tracking self-check, or read your consent signals with the gcs and gcd decoder.

Get my free audit

Sources (6)
Get my free audit
Your session, live
    Consent: Pending See details