Consent Mode v2 wired correctly: six links from the banner to Google Ads and GA4
Filed
Baris Asa, Synctag, tracking specialist, London · Last checked:
If conversions fell by about your banner’s decline rate after Consent Mode v2 went live, that is the banner working. If they fell by much more, one of six links between the banner and Google Ads is broken. Wired correctly, the banner stores each answer, the site tells Google’s tags “no answer yet” before they load, passes on the answer on every page, doesn’t block Google’s tags a second time, makes Meta and other tags obey it, and Google Ads and GA4 show the signals arriving. Then every visitor who accepts is measured, and Google models some of the sales from those who decline.
The banner vendor owns the first link, whoever runs Google Tag Manager (GTM) owns the next four, and whoever owns Google Ads and GA4 checks the last. A new banner, a theme or checkout update, a new tag or a server-side move is what usually breaks one. A broken link is filed as F-201 (conversions lost to a consent signal that never arrives).
Where to find your decline rate. Most banner tools report an accept, opt-in or consent rate in their dashboard; the decline rate is the rest. An illustrative example, not a client: 40 per cent decline and recorded conversions down about 40 per cent is the banner working; down 70 per cent is a broken link. Once Google Ads shows modelling as active (step 1 below), part of the declined share comes back as modelled conversions, so a healthy fall gets smaller, not bigger.
Check it yourself first (no GTM access needed)
- Google Ads: Goals, Conversions, Summary, open your website purchase action, then the Diagnostics tab. “Consent mode is implemented” or “Consent mode is implemented and modeling is active” means Google is receiving the signal. The status can take up to two weeks to appear, so if the banner went live more recently, a missing status proves nothing yet: run step 3.
- GA4: Admin, Data collection and modification, Consent settings. A notice about missing ads measurement (
ad_user_data) or ads personalisation (ad_personalization) signals means Google isn’t receiving those two as granted. The banner mapping (Link 1) or the update (Link 3) is the usual cause. - Your own numbers: in GA4, Reports, User, User attributes, Demographic details, set the table to Country, and compare key events or total revenue for the week before and the week after the banner went live. Set the result against your decline rate, as above.
Then use Exhibit A to name the link and the person to send it to.
| What you see | Likely link | Who fixes it |
|---|---|---|
| Accepts in the banner dashboard, but UK and EEA purchases near zero | 1, 2 or 3 | Tracking |
| Drop far beyond the decline rate, mostly on the order confirmation page | 3 | Tracking |
| No consent status in Google Ads Diagnostics after two weeks | 1 or 2 | Tracking |
| GA4 Consent settings notice about missing signals | 1 or 3 | Banner vendor and tracking |
| Status “implemented”, modelling never active, enough ad clicks | 4 | Tracking |
| Meta or TikTok counting visitors who declined | 5 | Tracking |
“Tracking” means whoever runs GTM, GA4 and the ad tags: an agency, a freelancer or an in-house analyst. Ask them to fill in Exhibit B for your site; rows they can’t fill are the gap. If nobody on your side owns the banner and the container, that is the work on the Consent Mode consultant page, and what a Consent Mode audit hands back lists the deliverable.
Narrower questions have their own notes: how much of a drop is normal, the full Tag Assistant test, and the GTM settings in order. Each covers one or two links; this chapter covers all six.
What are the six links, who owns each, and what breaks them?
Exhibit B is a wiring register for a UK online shop running advanced Consent Mode (illustrative, not a client). It sits with the tracking documentation.
| Link | Correct state | Owner | Usually broken by |
|---|---|---|---|
| 1. Banner | Asks, stores the answer, maps it to the four types | Banner vendor sets it, tracking checks the mapping | New banner or category |
| 2. Default | All four types set before any Google tag | Tracking | Hard-coded tag, second default |
| 3. Update | On the answer and on every later page | Tracking | Theme or checkout change |
| 4. Google tags | No second consent block in GTM | Tracking | Copied tag, blanket consent trigger |
| 5. Other tags | Fire only on the matching answer | Tracking | New platform, server-side move |
| 6. Platforms | Google Ads and GA4 show the signals | Google Ads and GA4 owner | Nobody looking |
The four types Consent Mode v2 needs are ad_storage, analytics_storage, ad_user_data and ad_personalization. Three govern measurement and sending user data to Google; ad_personalization governs remarketing and personalised ads. Google lists three more storage types; Google Ads and GA4 don’t need them for this.
Link 1: what must the banner do?
In plain terms: if the banner’s answer doesn’t reach Google in the right form, every later link works on the wrong answer.
The banner asks, stores the answer, and hands each answer to the right consent type. Google’s EU user consent policy covers end users in the EEA, the UK and Switzerland: consent for cookies where legally required, and for using personal data to personalise ads. Google Ads and GA4 features for those visitors depend on the consent signals.
The handover is the part that goes wrong. A banner has its own categories (often called statistics and marketing), and its GTM template maps each one to Google’s types. Open the template settings and write down which category grants which of the four. A marketing category that grants ad_storage but not ad_user_data leaves Google Ads without one of the v2 signals.
Breaks when: the banner vendor changes, a category is renamed or added, or a new domain or language version gets a separate banner configuration. Cookiebot and GTM: why the tags still get the wrong consent state is one vendor’s version of this.
Link 2: when is the default set?
In plain terms: before the visitor answers, Google’s tags need to be told “not yet”. If they load first, they act without any consent state.
The rule: a default for all four types runs before any Google measurement command, on every page, from one source only. Out of order, the defaults don’t work. In GTM that is the banner’s template on Consent Initialization - All Pages, denied for GB, CH and the EEA. The settings row by row, including wait_for_update for a banner that loads late, are in the GTM setup note.
Two optional settings belong in the register as a business decision: url_passthrough (passes ad click information through URLs when ad_storage is denied) and ads_data_redaction (redacts ad click identifiers in requests when ad_storage is denied).
Breaks when: someone adds a hard-coded Google tag to the theme above the container, a second container or plugin sets its own default, or the template is moved onto a later trigger.
Link 3: does the answer reach the tags?
In plain terms: if this breaks, a visitor who accepted on the first page is treated as declined from the second page on, including the order confirmation page.
The rule: the update runs on the click, and again as early as possible on every later page, read from the cookie the banner set. In a GTM template that means updateConsentState, not gtag('consent', 'update', ...): gtag commands are queued and may not be processed before the next event begins.
Breaks when: a theme or checkout change removes the banner script from some page types, or the banner’s cookie name changes.
Link 4: are Google’s tags blocked a second time?
In plain terms: in advanced mode, Google’s tags still load for visitors who decline and send cookieless pings, which is what Google models from. A second block in GTM stops those pings.
The GA4 and Google Ads tags have built-in consent checks. GTM also offers Additional Consent Checks on each tag; set to “Require additional consent for tag to fire”, a tag only fires if every listed type is granted. Put that on the GA4 tag, or fire the Google Ads conversion tag on a “consent accepted” trigger, and a visitor who declines sends nothing. Google has nothing to model from, and the setup behaves like basic mode whatever the banner says. Which mode to choose is in basic vs advanced; this link makes sure the container does what you chose.
GTM’s Consent Overview (switch it on in Admin, Container Settings) lists every tag under “Consent Not Configured” or “Consent Configured”. Review the Google tags there after every publish.
Breaks when: a GA4 or Ads tag is copied from an older container, or someone “makes it compliant” by adding a consent trigger to every tag.
Link 5: do the other tags obey the answer?
In plain terms: Google’s Consent Mode steers Google’s tags. Other platforms need their own rule.
Meta and TikTok tags in GTM need Additional Consent Checks requiring the type your banner’s marketing category grants (typically ad_storage, and ad_user_data where the tag sends user data to the platform), or the banner vendor’s own blocking. Microsoft’s UET tag has its own consent mode, read from an ad_storage setting with a default and an update, so it needs that wiring rather than a plain block.
With a server-side container, consent mode is set up only in the web container: the Google tag passes the choice to the server, and Google’s tags there adjust what they send. That covers Google’s tags only. A Meta Conversions API tag in the server container needs its own check, set out in Consent Mode v2 with server-side GTM.
Breaks when: a new ad platform is added to the container, or a server-side container goes live and the other tags move there without their consent rules.
Link 6: what do Google Ads and GA4 show when it works?
In plain terms: this is where you see whether links 1 to 5 hold, and the only link a non-technical owner can check alone.
Google Ads: the Diagnostics tab (path in step 1 above) shows one of two statuses:
- “Consent mode is implemented”: set up, but below the modelling threshold of 700 ad clicks over 7 days per domain and country grouping.
- “Consent mode is implemented and modeling is active”: modelled conversions are being added to the Conversions column, not a separate one. Why none are showing has the usual reasons.
Google says the status can take 48 hours to appear, and up to two weeks in some cases.
GA4: the Consent settings page (path in step 2) shows advertising related and behaviour analytics consent signals per data stream. Google says its notices can take 48 to 72 hours to update. Modelled data in GA4 needs:
- the Blended reporting identity (Admin, Data display, Reporting identity);
- at least 1,000 events a day with
analytics_storagedenied, for 7 days; - 1,000 consented daily users on at least 7 of the previous 28 days.
Google says meeting those doesn’t guarantee eligibility.
Breaks when: nobody looks. Neither screen alerts the person who changed the site.
Which changes should trigger a re-check?
Any change to the banner, the container or the page templates. Exhibit C is the re-check schedule.
| Change | Link at risk | Check |
|---|---|---|
| New or updated banner, new category | 1, 3 | Category mapping to the four types |
| Theme, checkout or plugin update | 2, 3 | Default before tags, update on later pages |
| New tag or platform in GTM | 4, 5 | Consent Overview after publish |
| Server-side container goes live | 5 | Declined test session on the server |
| New domain or market | 1, 2 | Region rows, banner on the new site |
The test is one declined and one accepted session in Tag Assistant, reading the On-page Default and On-page Update columns on the Consent tab; the check note walks through it. Run it after every change in the table, and once a month on the order confirmation page, where a missed update costs the most.
What doesn’t correct wiring recover?
Visitors who decline are still not measured as individuals. Correct wiring gives Google the cookieless pings to model some of them, if the account clears the thresholds in Link 6. Below those, the fall stays about the size of your decline rate. That part is the banner, not a fault.
It doesn’t settle whether the banner meets privacy law either. That is a question about what the banner asks and how, for whoever advises the business on privacy. This chapter is about measurement: every answer a visitor gives is the answer Google’s tags act on.
Also filed as
- consent mode v2 end to end checklist from banner to google ads
- who owns consent mode v2 after launch
- consent mode v2 implementation checklist end to end
- conversions dropped after consent mode v2: which link is broken
- consent mode v2 broke after a theme, banner or GTM change
- consent mode v2 require additional consent GA4 tag
- consent mode v2 update not firing on next page
- consent mode status google ads diagnostics
- GA4 consent settings ad_user_data missing
Faults explained here
Sources
- Google tag platform: Consent mode overview (consent types including ad_storage, ad_user_data, ad_personalization for personalised advertising, analytics_storage; basic blocks Google tags until the banner is answered, no data sent without consent; advanced sends measurements without cookies while denied; checked 16 Nov 2026)
- Google tag platform: Set up consent mode on websites (default before any measurement command on every page; order is vital; region per ISO 3166-2; wait_for_update; optional url_passthrough and ads_data_redaction; persist the choice and call update on subsequent pages; checked 16 Nov 2026)
- Google tag platform: Consent mode APIs for GTM templates (setDefaultConsentState and updateConsentState instead of gtag consent; defaults on Consent Initialization - All Pages; update as early as possible on later pages by reading the banner's cookie; gtag commands are queued; checked 16 Nov 2026)
- Tag Manager: Consent configuration (built-in and additional consent checks; Require additional consent for tag to fire: fires only if all listed types are granted; Consent Initialization fires before all other triggers; Consent Overview in Container Settings; checked 16 Nov 2026)
- Google tag platform: Consent mode in server-side tagging (set up consent mode only in the web container; Google's tags in the server container are consent-aware; covers Google tags only; checked 16 Nov 2026)
- Google tag platform: Verify consent mode (Consent tab, On-page Default and On-page Update; default not set, default set too late, consent state doesn't update; checked 16 Nov 2026)
- Google Ads: Verify consent mode implementation (Goals, Conversions, Summary, conversion action, Diagnostics; 'Consent mode is implemented' below 700 ad clicks over 7 days per domain and country grouping; 'implemented and modeling is active'; 48 hours, up to 2 weeks; checked 16 Nov 2026)
- Google Ads: About consent mode modeling (modelled conversions appear in the Conversions column, and values in Conversion value; 700 ad clicks over 7 days per country and domain grouping; checked 16 Nov 2026)
- Google Ads: About consent mode (basic: conversion modelling based on a general model; advanced: advertiser-specific model; checked 16 Nov 2026)
- Analytics: Behavioural modelling for consent mode (consent mode on all pages; 1,000 events a day with analytics_storage denied for 7 days; 1,000 consented daily users on 7 of the previous 28 days; tags must load in all cases; Blended reporting identity; eligibility not guaranteed; checked 16 Nov 2026)
- Analytics: Verify and update consent settings (Admin, Data collection and modification, Consent settings; ad_user_data and ad_personalization; notices update in 48-72 hours; checked 16 Nov 2026)
- Microsoft Advertising: Setting up UET for consent mode (consent set through the ad_storage property, with a default and an update; checked 16 Nov 2026)
- Google: EU user consent policy (applies to end users in the European Economic Area, the UK and Switzerland; consent for cookies and local storage where legally required, and for personal data used for ads personalisation; checked 16 Nov 2026)
Baris Asa, a London tracking specialist working as Synctag, checks all six links, fixes what is broken and leaves a written wiring register your team keeps. For ecommerce brands and the agencies behind them.
Consent Mode consultant →