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

READING ROOM › SYMPTOM FILES › SYM-016

SYMPTOM FILE SYM-016 FILED 04 NOV 2026 · REVISED 21 NOV 2026

Cookiebot Consent Mode not working in GTM: five wiring faults, in order.

ALSO FILED AS
  • “Cookiebot GTM Consent Mode v2 not working”
  • “Cookiebot consent mode wrong state”
  • “Cookiebot consent mode not working in GTM”
  • “Cookiebot default denied not updating after accept”
  • “Cookiebot CMP template Consent Initialization trigger”
  • “Cookiebot UK visitors consent granted by default”
  • “Cookiebot region GB or UK”
  • “Meta Pixel fires before consent Cookiebot”
  • “Cookiebot auto blocking with Google Tag Manager”

Baris Asa, tracking consultant, London · Revised: 21 November 2026

When Cookiebot Consent Mode is not working in GTM, the banner is usually fine and the wiring isn’t. You see it as Google Ads missing sales from people who accepted, or GA4 counting people who never answered. Check five things, in order: the Cookiebot tag is on the Consent Initialization - All Pages trigger; no Google tag is hard-coded outside GTM; UK visitors fall in a denied region row (GB, not UK); the Meta Pixel and other non-Google tags have a consent check and a cookie_consent_update trigger; Cookiebot loads once.

The opposite case, consent stuck on denied after Accept, has its own section. Two checks you can do yourself in two minutes, no GTM access needed, are just below.

Baris Asa, Synctag, London. I set up and repair Cookiebot with GTM Consent Mode v2 for UK ecommerce brands and the agencies behind them. No partnership, affiliate or commission arrangement with Cookiebot or Usercentrics, which owns it.

Check it yourself before anyone opens GTM

On a laptop, from a UK connection.

  1. Cookies. Open the site in a Chrome incognito window and don’t touch the banner. Press F12, open Application, then Cookies, then your domain. Look for two names only: _ga (GA4) and _gcl_au (Google Ads). If either is already there, Google’s tags acted as if the visitor had said yes before they answered: fault 1, 2 or 3. Screenshot it.
  2. Meta Pixel. Install Meta’s Pixel Helper extension, clear the site’s cookies, reload and don’t touch the banner. If it already shows a PageView, it’s fault 4, or a Pixel added outside GTM by the theme or an app. Screenshot it.

Found one? Send the screenshot and the fault number to whoever runs GTM, or to me through Consent Mode setup and repair. That is enough to scope the job.

  • Google Ads conversions fell the week the banner went live. Often that is the banner working: people who decline drop out. If the cookie check above passes (no _ga before a click), the drop is expected, and advanced mode lets Google Ads model part of it back once the account has at least 700 ad clicks over 7 days per country and domain grouping. Consent Mode v2 didn’t lose your conversions walks through it. If _ga is set before a click, the problem is the opposite one: you’re counting people who never said yes.
  • GA4 sessions barely moved when the banner went live. When a banner starts working, people who decline should leave GA4’s cookie-based numbers. If nothing moved, their “no” may not be applied. Advanced mode with GA4’s behavioural modelling can fill part of that gap, so the cookie check is the real test.
  • Meta’s purchase count didn’t move at all. Same logic: decliners should fall out of the browser Pixel. If purchases also reach Meta through the Conversions API or a platform integration, the count may not move anyway. A PageView in Pixel Helper before any click is fault 4.
  • The Meta Pixel never fires on the first page for people who accept there. Fault 4, the trigger half.

Two terms. The default is the consent state Google’s tags assume before the visitor clicks. The update is what the click changes it to. A click never changes the default; it sends an update. The order Google expects them in, for any banner, is in How to implement Consent Mode v2 correctly in GTM.

1. Is the Cookiebot tag on the wrong trigger?

You see: a Google tag fires on an earlier message than the first Consent event in Tag Assistant.

Cause: the Cookiebot CMP tag sits on All Pages or Initialization. Google says the Consent Initialization trigger “will always fire before all other tags, including any Initialization triggers”. Anything later can lose the race.

Fix: trigger the Cookiebot CMP tag on Consent Initialization - All Pages. Tags that need to fire early, such as the Google tag, go on Initialization - All Pages, which Google designs to fire before every other trigger except Consent Initialization.

2. Does a Google tag load outside GTM?

You see: a GA4 or Google Ads request in the Network panel before gtm.js loads, or a Google tag in Tag Assistant that isn’t in your container.

Cause: gtag.js hard-coded in the theme or added by a plugin. It can run before GTM, and so before Cookiebot’s default. If that snippet sets its own default to granted, the earliest Consent event reads granted too.

Fix: move that tag into GTM and remove the hard-coded copy.

If it truly can’t move, put a consent default snippet above it in the page source, matching the template’s region rows exactly. Cookiebot says its snippet “must precede gtag.js or GTM code snippets”, with data-cookieconsent="ignore" if you use automatic blocking. The page then carries two sets of defaults, so keep them identical; the earliest Consent event will be the snippet’s.

3. Do the region rows leave UK visitors on granted?

You see: as a UK visitor, the earliest Consent event reads granted.

Cause: region rows are the Default Consent State settings in the Cookiebot tag: one row per list of countries, plus an optional global row (Region left blank) for everyone else. One version is a global row set to granted plus a denied row for EU countries that leaves out GB. Another is a row typed “UK”. Cookiebot asks for ISO 3166-1 alpha-2 codes, and the United Kingdom’s is GB.

What it costs: GA4 and Google Ads treat those visitors as consented, so the numbers include people who never answered, and the consent rate in Cookiebot won’t line up with what Google received. The compliance problem comes on top.

Fix: set the global row to denied, or add GB to the denied row, as Cookiebot’s own regional example does. Then rerun the cookie check.

You see: the Meta Pixel, TikTok or Pinterest under Tags Fired before any click. Or they never fire on the first page for new visitors who accept there.

Cause: these tags don’t read Consent Mode by themselves. Without a check, they fire for everyone, and Meta counts purchases from people who declined. With a check but still on All Pages, they’re evaluated once, at page load, and skipped. Cookiebot: “The updating of Consent Mode settings does not trigger a reevaluation of tags with the ‘All Pages’ trigger.”

Fix: in each tag, Advanced Settings, Consent Settings, require additional consent for ad_storage. Replace All Pages with a Custom Event trigger, event name cookie_consent_update, which fires once the choice is known, from the banner or a previous visit. That much is Cookiebot’s guide. I also set the Meta base tag to fire once per page (Advanced Settings, Tag firing options), so a visitor who changes their choice on the same page doesn’t send a second PageView.

5. Is Cookiebot loading twice?

You see: cbid in the page source (Ctrl+U, then search) as well as a live Cookiebot CMP tag in GTM.

Cause: Cookiebot’s script pasted into the theme and the GTM template added too. For automatic blocking with GTM, Cookiebot says to make sure “the Cookiebot script is not executed by Google Tag Manager”, and to mark the consent default and GTM snippets data-cookieconsent="ignore" so auto-blocking doesn’t hold them back.

Fix: pick one. In GTM: the template only, nothing in the theme. With auto-blocking: the page-source script in this order (consent default, GTM, then Cookiebot), with the GTM tag paused.

Filed as SYM-016 under F-201 , Consent Mode mis-wired. The five faults are the forms F-201 takes when the banner is Cookiebot.

Tag Assistant shows the earliest Consent event as denied, which is correct, but nothing changes after the visitor clicks Accept. Google’s debugging guide: “If the consent state doesn’t update, check if you have an update mechanism implemented.” With Cookiebot in GTM, the template is that mechanism. Four things to rule out:

  1. Check you’re reading the latest event. The earliest Consent event is the default and stays denied whatever the visitor does. Click the most recent one.
  2. Enable Google Consent Mode is unticked in the Cookiebot tag. The template then sets no defaults and loads Cookiebot’s script with consentmode=disabled, which is meant to stop it sending Consent Mode signals. A hard-coded gtag default then sits there alone, denied for good. The box is ticked by default, so if it’s off, someone turned it off.
  3. The banner never loaded. Cookiebot’s GTM guide says to register the domain in the Cookiebot account. A new or staging domain that isn’t registered often shows no banner, so no answer is ever sent.
  4. A second Cookiebot script outside GTM answers instead of the template (fault 5).

If you accepted Statistics only, analytics_storage turns granted and the three ad types staying denied is correct, not a fault.

The Tag Assistant screenshots, for whoever runs GTM

To tell faults 1, 2 and 3 apart, from Google’s consent debugging guide:

  1. Open Tag Assistant, enter the site’s URL, and don’t touch the banner.
  2. In the Summary, click the earliest Consent event. Screenshot its API Call (the panel that lists the consent values) and the Tags tab.
  3. Accept all, click the most recent Consent event, and screenshot its API Call.
  4. Do it from a UK connection (a VPN will do).

An engineer can also click a GA4 or Google Ads tag, open Output, then Consent: On-page Default and On-page Update should match the two API Calls.

Look atPassFail points to
Earliest Consent event, UK visitorAll four types denied, no Google tag before itGranted: fault 3, or a hard-coded gtag default (fault 2). Tag first: fault 1 or 2
Latest Consent event after Accept allAll four grantedThe update section above
Declined session, Tags Not FiredMeta Pixel and other non-Google tags listedFault 4
No Consent event at allConsent tab empty, below
Check order · stop at the first fail · from Google's consent debugging guide and Cookiebot's GTM guide; no client data
Consent typeOn-page DefaultOn-page Update
ad_storageGrantednone
analytics_storageGrantednone
ad_user_dataGrantednone
ad_personalizationGrantednone
Tag Assistant · GA4 tag, Output, Consent · simulated UK visitor before any click · worked example, illustrative, not a client account

A UK visitor, no click yet, everything granted, so Google’s tags set cookies before an answer. That is fault 3, unless a hard-coded gtag default got there first (fault 2); the Network panel tells you which.

Google says that happens when Consent Mode isn’t implemented on the page. Check the Cookiebot tag fired at all, then that Enable Google Consent Mode is ticked in it (item 2 in the update section).

Fixed when

The repair is finished when Tag Assistant shows these five things, and there’s a written note of whether basic or advanced mode was chosen, and by whom:

  1. As a UK visitor, the earliest Consent event on each page type reads denied for all four types, before any Google tag fires.
  2. After Accept all, the latest Consent event reads granted for all four.
  3. In a declined session, every non-Google tag is under Tags Not Fired.
  4. On a returning visit, the update straight after the default carries the earlier answer, before any Google tag fires.
  5. One Cookiebot script per page, from one place.

Three questions that show whether someone knows these faults: “Which trigger does the Cookiebot tag go on?” (Consent Initialization - All Pages). “UK or GB in the region rows?” (GB). “How will the Meta Pixel wait for consent?” (a consent check on ad_storage and the cookie_consent_update trigger). For a new install, the template field by field is in Setting up Cookiebot with Consent Mode v2 in GTM.

Basic or advanced, and what it’s worth

If the GA4 and Google Ads tags also require additional consent in GTM, you’re in basic mode: they send nothing unless and until the visitor grants consent, and Google uses a general model. In advanced mode they stay on their built-in checks and send cookieless pings (hits with no cookie and no ID) while consent is denied, and Google Ads builds a conversion model from your own account’s data. Google Ads Help lists the conditions for conversion modelling, among them at least 700 ad clicks over 7 days per country and domain grouping.

Cookiebot’s guide notes that with built-in checks “data will be transmitted to Google without explicit permission”, and suggests the additional check if that concerns you. My view: choose on purpose and write it down. On an audit, “nobody knows who chose” is the finding. Which banner to pick in the first place is in Cookiebot vs CookieYes vs Usercentrics vs Complianz.

What the Cookiebot template sets, for reference

Read from the Cookiebot CMP template’s own code, which Usercentrics publishes on GitHub.

Cookiebot categoryConsent Mode types it sets
Statisticsanalytics_storage
Marketingad_storage, ad_user_data, ad_personalization
Preferencesfunctionality_storage, personalization_storage
Necessarysecurity_storage, always granted
  • Default. One default per region row. With no global row, it adds an all-denied default for every visitor outside your region rows.
  • Wait. “Wait for update” defaults to 2,000 milliseconds and is added to each of your region rows: how long Google’s tags wait for an update before sending. The all-denied fallback is set without it.
  • Returning visitors. It sets the default first, then reads the CookieConsent cookie and sends the stored answer as an update straight after.

If you run server-side GTM, the server has its own checks in Consent Mode v2 with server-side GTM.

Common questions

Why does Tag Assistant still show denied after I click Accept in Cookiebot?

Check you’re reading the most recent Consent event: the earliest one is the default and stays denied. If no update follows your click, rule out Enable Google Consent Mode being unticked in the Cookiebot tag, a banner that never loaded on that domain, and a second Cookiebot script outside GTM. If you accepted Statistics only, the three ad types staying denied is correct.

The template, and the Cookiebot script it loads, do the Google side: defaults per region row and the update when the visitor answers. The trigger and every non-Google tag’s consent check are still yours to set.

Should I type UK or GB in the Cookiebot region field?

GB. Cookiebot asks for ISO 3166-1 alpha-2 country codes, and the United Kingdom’s is GB.

Which trigger should the Meta Pixel use with Cookiebot?

A Custom Event trigger on cookie_consent_update, with additional consent required for ad_storage. On All Pages it is checked once, at page load, and missed by anyone who accepts on that page.

Basic sends Google nothing unless and until the visitor grants consent. Advanced sends cookieless pings while consent is denied, and once the account meets Google’s threshold (at least 700 ad clicks over 7 days per country and domain grouping) Google Ads models conversions from your own data. Either is valid if someone chose it on purpose and wrote it down.

I do: Baris Asa, Synctag, London, for UK ecommerce brands and the agencies they work with (Consent Mode setup and repair). No affiliate tie to Cookiebot. Whoever does it, the job is finished when the five checks under Fixed when pass.

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

Sources

Cookiebot pages read on 4 November 2026; template source, consent setup guide, consent mode overview and Tag Manager trigger types read on 5 November 2026; Google’s consent debugging guide, Tag Manager consent settings and Google Ads conversion modelling page re-read on 21 November 2026:

  • Cookiebot Support, Google Tag Manager deployment (Cookiebot CMP template; register the domain; Consent Initialization - All Pages; global region recommended; ISO 3166-1 alpha-2 codes; category to consent type mapping; built-in and additional checks; data sent to Google before consent and the additional check if that concerns you; cookie_consent_update trigger; All Pages tags not re-evaluated; Consent Mode enabled by default), implementing Google Consent Mode (default snippet must precede gtag.js or GTM; data-cookieconsent="ignore"; regional example including GB), Google Tag Manager and automatic cookie blocking (script not executed by GTM; data-cookieconsent="ignore"; load order) and automatic cookie blocking (find cbid in the page source)
  • Usercentrics on GitHub, Cookiebot CMP GTM template source (Wait for update default 2000, added to region rows only; all-denied fallback when no global row; with Consent Mode off, no defaults and the script loaded with consentmode=disabled; default set before the stored CookieConsent answer is sent as an update; security_storage always granted)
  • Google for Developers, set up consent mode (default before any commands that send measurement data; wait_for_update in milliseconds; region-specific defaults), verify consent mode (earliest and most recent Consent event; API Call; “check if you have an update mechanism implemented” when the state doesn’t update; On-page Default and On-page Update; Consent Initialization for CMP tags; empty Consent tab; visitor location) and consent mode overview (basic and advanced; cookieless pings while consent is denied; general and advertiser-specific models)
  • Tag Manager Help, consent settings (Consent Initialization fires before all other tags; built-in and additional consent checks) and trigger types (Initialization fires before all other triggers except Consent Initialization, for tags that should fire early)
  • Google Ads Help, consent mode conversion modelling (conditions for conversion modelling, including 700 ad clicks over 7 days per country and domain grouping)

← back to the reading room