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

READING ROOM › SYMPTOM FILES › SYM-026

SYMPTOM FILE SYM-026 FILED 06 NOV 2026 · REVISED 06 NOV 2026

How to implement Consent Mode v2 correctly in GTM: defaults, region, wait, update, in that order.

ALSO FILED AS
  • “how to implement Google Consent Mode v2 correctly”
  • “Consent Mode v2 best practices”
  • “Consent Mode v2 common mistakes GTM”
  • “consent mode v2 implementation checklist GTM”
  • “consent mode default before tags GTM”
  • “Consent Initialization trigger consent mode”
  • “consent mode region GB missing”
  • “what wait_for_update value should I use”
  • “a tag read consent state before a default was set”
  • “consent mode update not firing for returning visitors”

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

Google’s guide recommends one order for Consent Mode v2: the banner sets a default for all four consent types (the four permissions Google’s tags check) before any Google tag loads, then updates them when the visitor answers. Get it wrong and Google Ads and GA4 can show fewer sales than your shop since the banner went live. Some drop is expected from visitors who decline; an order fault shows as a step down the week the banner launched. Three questions below tell you whether yours is right.

Get the order right and visitors who accept are measured as consented. Google Ads can model some of the sales of those who decline, if the account has enough ad clicks (the threshold is under basic and advanced below).

Check yours without opening Tag Manager. First, your own numbers: compare last month’s Google Ads or GA4 purchases with your shop’s orders. Some gap is normal once visitors can decline. A gap that jumped the week the cookie banner went live is not, and Conversions dropped after implementing Consent Mode v2 sorts the normal part from the fault.

Then send your agency or developer, whoever runs your Google Tag Manager setup (the “container”), this message. Any answer that differs from the one in brackets means the order is wrong:

  1. Which trigger does the cookie banner’s tag fire on? (It should be Consent Initialization - All Pages.)
  2. Does the list of countries that start as denied include GB? (The UK’s code is GB, not UK.)
  3. Does Tag Assistant, Google’s tag checker, show “A tag read consent state before a default was set”? (It should not.)

Nobody can answer? Read-only access to the container is enough for me to tell you which of the three is wrong. It is the first thing I check as a Consent Mode consultant, for brands and for agencies running a client’s container.

If any answer differs, forward this page. Most fixes are a setting change in the banner’s template. A tag hard-coded in the site’s pages takes a developer.

Everything below is reference for whoever manages the container. You can stop here.

In GTM the order is: the banner’s template on Consent Initialization - All Pages sets all four types to denied for GB, CH and the EEA, with wait_for_update of at least 500 ms if the banner loads asynchronously; Google’s tags fire on Initialization or later; the template calls updateConsentState on the visitor’s answer and from the stored cookie on every later page; non-Google tags get additional consent checks.

StepWhat happensIn GTM
1Default consent state is setBanner template on Consent Initialization - All Pages
2Regional defaults applyRegion rows in the template’s default settings
3Google’s tags wait briefly for the answerwait_for_update in the same settings
4Google’s tags load and read the stateGoogle tag on Initialization - All Pages or later; GA4 and Ads tags on their usual triggers
5The visitor answers, the state is updatedThe template calls the update; on later pages it reads the stored answer
6Non-Google tags obey the answerAdditional consent checks on each one
7Prove itTag Assistant check, then one declined and one accepted session

For gtag.js, Google’s guide gives the same order: the consent default called before any config or event, then your consent solution, which calls the update after the visitor chooses. If you hard-code it, this is the shape, and it must be your only default source:

gtag('consent', 'default', {
  ad_storage: 'denied', analytics_storage: 'denied',
  ad_user_data: 'denied', ad_personalization: 'denied',
  region: ['GB', 'CH' /* plus the EEA codes */],
  wait_for_update: 500
});

Source: Google’s consent guide (Google: set up consent mode).

Google’s docs and Simo Ahava agree that the default comes first. The checklist below is Google’s documentation plus what I check:

  1. Defaults for all four types on Consent Initialization, before any Google tag.
  2. Region rows that include GB and CH.
  3. A template that calls updateConsentState, not gtag.
  4. wait_for_update for a banner that answers late.
  5. A Tag Assistant check that nothing read consent before the default.

Simo Ahava’s Consent Mode v2 for Google tags agrees with Google: the default “should be set to fire on the Consent Initialization trigger”, before “any Google tags fire”, and he calls the opposite “a race condition”.

Vendor checklists cover the banner. The trigger and region rows sit in the GTM setup, so check those too:

Common adviceWhat Google’s docs addThen check
”If using a CMP, ensure it’s Google-certified and IAB TCF-compliant” (CookieYes)A certified banner can still sit on the wrong trigger or carry the wrong region rowsThe template settings (step 1, step 2)
Default to denied for the EEAGoogle’s consent policy covers the EEA, the UK and SwitzerlandAdd GB and CH
Install the banner’s GTM templateDefaults must be set on Consent Initialization - All PagesCheck the trigger, and that there is one default source

What do the default rows look like in the template?

A worked example for a UK shop, as entered in a banner template’s default settings:

RowRegionThe four v2 typeswait_for_update
1GB, CH and the EEA country codes (list below)all denied500 or more if the banner is asynchronous
2blank (everyone else)your choice, all four setsame value

Three rules from Google’s guide and template documentation make this work:

  1. A row with no region is the fallback. It applies to every visitor not covered by another row.
  2. The more specific region wins. A row for a subdivision beats a row for its country.
  3. Every row sets every type. Google’s debugging guide shows the fault where analytics_storage has a regional default and ad_storage doesn’t (Google: verify consent mode).

Google’s docs cite ISO 3166-2: use the two-letter country code (GB) or a subdivision code (US-CA). The UK is not in the EEA.

So a denied row that lists only the EEA countries leaves UK visitors on row 2. Google’s EU user consent policy covers end users in the EEA, the UK and Switzerland (Google: EU user consent policy), which is why GB and CH belong in row 1.

The EEA codes are the 27 EU member states plus IS, LI and NO; check your list against Google’s current policy page before copying it. Row 1 is therefore:

GB, CH, IS, LI, NO, AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IE, IT, LV, LT, LU, MT, NL, PL, PT, RO, SK, SI, ES, SE

What row 2 says is a legal decision for your market, not a tag setting.

For Cookiebot specifically, the missing GB row is one of the faults in Cookiebot and GTM Consent Mode v2: why the tags still get the wrong consent state; the Cookiebot template field by field is in setting up Cookiebot with Consent Mode v2 in GTM.

Why all four types, and why does ad_user_data matter for revenue?

Google’s guide says that by default no consent mode values are set, so a type you leave out has no default at all (Google: set up consent mode). Consent Mode v2 added two types to the original two: ad_user_data (sending user data to Google for advertising) and ad_personalization (remarketing and personalised ads).

ad_user_data is easy to miss. When it is denied, Google says personal data collection for advertising is disabled, including the hashed first-party data that Enhanced Conversions sends (F-402 , Google: consent mode overview). Enhanced Conversions is the hashed customer email Google Ads uses to match a sale to an ad click. A banner that never updates ad_user_data to granted switches it off for the visitors who said yes: matched conversions you had consent for and never received.

Which mistakes put a tag in front of the default?

Tag Manager Help says the Consent Initialization trigger fires before all other tags, including Initialization triggers, and that it is meant for tags that set or update consent, such as your banner’s tag (Tag Manager: consent settings). The order still breaks in four ways. Each shows up the same way: in Tag Assistant, a Google tag appears before the first Consent event. Google’s guide: “If your consent code is called out of order, consent defaults won’t work.” It fails in two ways: a late default (a Google tag reads consent, and may write cookies, before the visitor answered) or a late update (people who said yes are treated as denied).

  1. The banner template on All Pages or DOM Ready. It passes a quick test because it does load. When the Google tag is on Initialization (Google’s example page-load trigger), it loads after that tag has already read an empty consent state.
  2. A Google tag hard-coded in the page above the GTM snippet. It runs before GTM’s first trigger, so nothing in GTM can come before it. Move the tag into GTM. If it must stay hard-coded, the default has to come from a gtag snippet above it, and that snippet becomes your only default source: turn the defaults off in the GTM template.
  3. Two sources of defaults. A banner template plus a separate default tag, or the banner’s script in the page plus its template in GTM. The second can overwrite the first with different values. Pick one.
  4. An update that arrives as a dataLayer event. A banner that only pushes something like consent_accepted into the dataLayer (the page’s message queue to GTM) hasn’t updated anything. A Custom HTML tag that turns that event into a gtag update can arrive after the next tag has already read consent, because gtag commands are queued (see below). Use a template that calls updateConsentState.

Filed as SYM-026 under F-201 , Consent Mode mis-wired: all four mistakes are forms of it. How the first two look with Cookiebot in particular is in the Cookiebot note.

What does wait_for_update do, and what value should I use?

Google describes it as control over “how long to wait before data is sent”, in milliseconds. Its template guide says that for an asynchronous banner you “should specify a wait time of at least 500 milliseconds” (Google: consent mode templates).

Google asks for the wait when the update can arrive later, for example when the template makes a network request before calling updateConsentState. Google’s text ties the wait to asynchronous work before the update. In practice, if your template reads the stored answer from its cookie and calls the update before any Google tag fires, there is less to wait for. My reading of Google’s text, not documented behaviour: if the update waits on a network request and no wait is set, Google’s tags may fire on the denied default first.

wait_for_update is read by Google’s tags. Non-Google tags follow their own consent checks (step 6).

How does the banner send the update?

Through the template. Google expects the consent solution to update the state as soon as the visitor interacts with the banner, to store the choice, and to call the update again on later pages (Google: set up consent mode). Two points matter:

  • Tag Manager APIs, not gtag('consent', ...). Google’s template guide says: “Don’t create templates that use the gtag consent command”, and use setDefaultConsentState and updateConsentState instead, because gtag commands “are queued after all other pending messages and may not be processed before the next event begins”. Tag Manager Help adds that gtag commands are not guaranteed to be available before the next trigger fires.
  • Returning visitors get the update early. updateConsentState should run as early as possible on pages after the one where the visitor answered, ideally by reading the stored answer from the banner’s cookie inside the template.

Most banners in the Community Template Gallery do both; how four of them ship is in Cookiebot, CookieYes, Usercentrics and Complianz compared. Check yours in Preview (GTM’s test mode) on a second page view before trusting it: the first Consent event should already show the stored answer.

Two optional settings sit in the same template:

  • url_passthrough carries the ad click information across pages in the URL for visitors who declined ad_storage. Of the two, it is the one that affects attribution.
  • ads_data_redaction removes ad click identifiers from Google Ads requests, only while ad_storage is denied.

Neither changes the order. Both are choices to make with your legal adviser once the order is right.

Where do Google’s tags and the other tags fit?

Google’s tags have built-in consent checks and read the state themselves, so they stay on their normal triggers. Google’s debugging guide gives Initialization - All Pages as the example trigger for a page-load Google tag, which still fires after Consent Initialization. For step 6, turn on consent overview (Admin, Container Settings, Additional Settings, then the Consent Overview icon in the Tags list): it lists every tag that has no consent setting yet.

Non-Google tags (Meta Pixel, TikTok, LinkedIn, Hotjar) need Require additional consent for tag to fire. Tag Manager Help says such a tag “will only fire if the status of all specified consent types are ‘granted’ when the tag is triggered”. List only the types your banner ties to that tag. Listing too many drops visitors who accepted what the tag needs.

Basic or advanced: where does that choice sit?

At step 4. Basic keeps Google’s tags from loading until the visitor answers. Advanced loads them straight away with the denied defaults and sends cookieless pings (measurements with no cookie stored on the device). Both modes get conversion modelling; basic gets Google’s general model, advanced lets Google build one on your own account (Google: consent mode overview). The trade-off and how to switch are in Consent Mode v2 basic vs advanced.

Google Ads lists 700 ad clicks over 7 days per country and domain grouping as the eligibility threshold for consent mode conversion modelling. Google recommends cookieless pings; without them modelling may still run but without advertiser-specific calibration, so accuracy can drop (Google Ads Help). GA4’s behavioural modelling has separate eligibility rules, set out in GA4 Help.

How do I know the order is right?

Open Tag Assistant, select the earliest Consent event in the Summary and confirm all four types were set before any tag activity (Google: verify consent mode). The Consent tab shows “A tag read consent state before a default was set” when something read consent too early (Tag Assistant Help). If that appears and nobody can say which tag caused it, it is one of the four mistakes above. Then run one session declining everything and one accepting, and check the Google tags change behaviour between them. Google’s debugging guide covers the rest, including testing other regions by changing the browser’s location.

If you run a server container, it has its own checks: Consent Mode v2 with server-side GTM. If conversions fell the week the banner went live, start with Conversions dropped after implementing Consent Mode v2.

Common questions

Which trigger does the Google tag go on, relative to the banner tag?

Banner on Consent Initialization - All Pages; Google tag on Initialization - All Pages or later. The first fires before every other tag, so the default is in place.

What region code do I use for UK visitors?

GB, not UK (ISO 3166-2). The UK is not in the EEA, so add GB and CH to the EEA list; the full row is under the default rows above.

Do I still need to set defaults if my banner tool has a GTM template?

Usually the template sets them, so do not add a second default tag. Open its settings and check the rows, regions and wait_for_update.

Google steers you to setDefaultConsentState and updateConsentState instead, because gtag commands are queued and may not be processed before the next event begins.

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

Sources

Read on 6 November 2026:

  • Google for Developers, set up consent mode on websites (default called before measurement commands such as config or event; “If your consent code is called out of order, consent defaults won’t work”; no values set by default; region according to ISO 3166-2, more specific region wins; wait_for_update controls how long to wait before data is sent; update on interaction and on later pages; url_passthrough, ads_data_redaction)
  • Google for Developers, consent mode templates and APIs (don’t use the gtag consent command in templates; setDefaultConsentState and updateConsentState; gtag commands queued; Consent Initialization - All Pages; at least 500 ms wait_for_update for asynchronous banners; blank region applies to all others; update as early as possible on later pages, read from the banner’s cookie)
  • Google for Developers, consent mode overview (consent types; basic mode uses a general model, advanced an advertiser-specific one; ad_user_data denied disables hashed first-party data for Enhanced Conversions) and verify consent mode (earliest Consent event; a tag that read or wrote cookies before the default; Initialization - All Pages as the page-load example; regional defaults must cover every parameter; changing location)
  • Tag Manager Help, consent settings (Consent Initialization fires before all other tags; for tags that set or update consent; gtag commands not guaranteed to be available; consent overview; additional consent checks require every listed type granted)
  • Tag Assistant Help, consent mode troubleshooting for Google Ads (Consent tab; “A tag read consent state before a default was set”)
  • Google, EU user consent policy (end users in the EEA, the UK and Switzerland)
  • Google Ads Help, consent mode conversion modelling (700 ad clicks over 7 days per country and domain grouping; cookieless pings recommended for advertiser-specific calibration)
  • CookieYes, Google Consent Mode v2 (vendor source, updated 10 July 2025: certified CMP advice). I have no partnership or commission arrangement with CookieYes.
  • Simo Ahava, Consent Mode v2 for Google tags (not re-verified in November 2026, consistent with Google’s current docs; 16 January 2024, updated 7 March 2024: default on Consent Initialization, before any Google tag; update once choices are registered; race condition)

← back to the reading room