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

READING ROOM › SYMPTOM FILES › SYM-079

SYMPTOM FILE SYM-079 FILED 14 NOV 2026 · REVISED 15 NOV 2026

Setting up Cookiebot with Google Consent Mode v2 in GTM: who to hire, the template and the checks before you publish.

ALSO FILED AS
  • “how to set up Cookiebot with Google Consent Mode v2 in GTM”
  • “Cookiebot CMP template Google Tag Manager settings”
  • “Cookiebot GTM template Domain Group ID”
  • “Cookiebot Consent Mode v2 default state denied”
  • “top rated experts Cookiebot GTM Consent Mode”
  • “Cookiebot and GTM Consent Mode setup expert UK”

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

Nobody publishes an independent ranking of Cookiebot and GTM Consent Mode experts. Start with the Usercentrics Partner Directory or a Google Tag Manager (GTM) specialist who shows their consent work. Judge whoever you pick by five Tag Assistant checks before anything is published, a screenshot each. A wrong setup usually shows up as Google Ads or GA4 missing sales from people who accepted, or tags firing for people who declined.

I’m one option, not a ranking: Baris Asa (Synctag, London), eight years in tracking, five conference talks, Consent Mode v2 setup and repair for UK ecommerce brands and the agencies behind them. I have no partnership, affiliate or commission arrangement with Cookiebot or with Usercentrics, which owns it.

This page is for a new install or a rebuild. If Cookiebot is already live and the tags get the wrong state, the repair is in Cookiebot and GTM Consent Mode v2: why the tags still get the wrong consent state.

There is no neutral list, so build a short one from these:

  • The Usercentrics Partner Directory. It lists agencies that work with Usercentrics and shows partner tiers, such as Certified and Premium. It doesn’t say what a tier requires. Treat it as a starting list, not proof of the work.
  • Freelance marketplaces. If a profile says “Cookiebot partner”, look for the name in the Usercentrics directory before you rely on it.
  • GTM specialists who show consent work. Someone who writes about Consent Mode in GTM in detail, and will show a past Tag Assistant result with client details removed.
  • Your current agency or developer, if they already run your GTM container.

Whoever it is, send them the five checks further down this page and ask for the screenshots before they publish. Three questions that sort candidates fast (trigger, GB or UK, the Meta Pixel) are in how to judge a Cookiebot and GTM Consent Mode expert. Add a fourth for a new setup: “Basic or advanced mode, and why?” A good answer names one. Advanced, so Google can build a model from your own site for visitors who decline. Or basic, because you’d rather no Google request leaves the page before consent. Either is fine if they can say why. No view at all is the red flag.

What they need from you: edit access to the GTM container and a login to Cookiebot. You can keep the right to publish.

If you want me to do it, send the site and the banner tool through the Consent Mode page. You get the five screenshots and a named container version before anything goes live. Scope first, then a quote.

Why it’s worth doing properly

A correct setup keeps you measuring. Visitors who accept are tracked in full. In advanced mode, Google uses cookieless pings to model the conversions of visitors who decline, built from your own site, once your tags meet a data threshold (F-201 ). In basic mode, nothing is sent before consent, and Google Ads conversion modelling falls back to a general model. Consent Mode v2: basic vs advanced covers the choice.

The setup, for whoever does the work

From here to the five checks is technical. If you’re hiring, send this section to the person doing it.

What has to be ready before GTM?

  1. Cookiebot set up for your domain, with the banner configured and the scanner run. Google’s Tag Manager guide for Cookiebot says the scanner categorises your cookies. The category decides which Consent Mode types a visitor’s click changes.
  2. The Cookiebot ID, from the Your Scripts tab in Cookiebot. The template calls it the Domain Group ID.
  3. One copy of Cookiebot on the page. Search the page source for cbid. If the theme also loads Cookiebot, it loads twice.
  4. The basic or advanced decision, written down. It isn’t a template field. It decides whether Google’s own tags wait for consent.

How do I fill in the Cookiebot CMP template?

Add Cookiebot CMP from the Tag Manager Community Template Gallery (Google’s Cookiebot guide points to it) and create a tag from it.

FieldSet toWhy
Cookiebot IDYour Domain Group IDLoads your banner. Required.
Enable Google Consent ModeTicked (the default)Sets Google’s defaults and sends updates.
Default Consent StateOne row, region blank, all deniedThe table starts empty; see below.
Wait for update2000 (the default)How long Google’s tags wait for an answer, in milliseconds.
Redact ads dataDynamic (the default)Redacts ad click IDs in Google Ads and Floodlight requests while marketing is denied.
Enable URL passthroughUnticked (the default)Tick only as a deliberate choice.
Advertiser Consent ModeTicked (the default)Only matters if you run an IAB TCF banner; most UK shops can leave it.

Language, CDN Region and Add Geo Region(s) sit above Enable Google Consent Mode, and the Consent Mode fields only appear while it is ticked. Leave Enable IAB Transparency and Consent Framework unticked unless you show ads from IAB TCF vendors. Leave Language and CDN Region on auto-detect and com unless you run several banner languages.

Geo Regions is not the consent default. It only picks which banner a region sees. What Google’s tags assume before a click lives in the Default Consent State table.

The default state

The Default Consent State table has no rows on a new tag. Click Add row, leave Region blank (the template’s label: “leave blank to apply globally”), and keep every column on denied, which is where each one starts. That sets ad_storage, ad_user_data, ad_personalization and analytics_storage to denied, with Preferences denied too. The template sets security_storage to granted whatever you enter.

Add the row even though denied is also the fallback. The template applies Wait for update only to the rows you create. With no rows, it sets an all-denied default for everyone, without the wait.

If you add regional rows, the template’s help text asks for ISO 3166-1 alpha-2 country codes. For the UK that is GB, not UK. My default for UK ecommerce is one global denied row: the visitor’s click moves it to granted for what they accepted.

What the click changes

Cookiebot category acceptedConsent Mode types set to granted
Statisticsanalytics_storage
Marketingad_storage, ad_user_data, ad_personalization
Preferencesfunctionality_storage, personalization_storage

For a returning visitor, the template sets the default first, then reads the stored CookieConsent cookie and sends the saved answer as an update straight after.

Which trigger does the tag go on?

Consent Initialization - All Pages. Google’s Tag Manager help says this trigger is for tags that set or update consent, such as a CMP tag, and that it fires before all other triggers. A CMP tag on plain All Pages is a mistake I find on audits. More than once.

Your GA4 and Google Ads tags keep their normal triggers. Non-Google tags such as the Meta Pixel don’t read Consent Mode by themselves. Google’s Cookiebot guide says to set “Require additional consent for tag to fire” on these tags, and recommends replacing page-load triggers with a custom cookie_consent_update event trigger; the steps are in fault 4 of the wrong-state note.

Then switch on the consent overview: Admin, Container Settings, tick “Enable consent overview”. In Tags, open the Consent Overview icon. Any tag under Consent Not Configured still needs a decision.

What are the five checks before I publish?

Run each in Tag Assistant Preview (GTM’s test mode) on the home page, a product page and checkout. If you added region rows, Google’s verify guide says to repeat the checks with a simulated location for each region.

  1. Before any click. Open the earliest Consent event and its API Call. ad_storage, ad_user_data, ad_personalization and analytics_storage should read denied. That default should come before the first Google tag fires, and Tag Assistant should show no warning that the default was set too late.
  2. After Accept all. Open the most recent Consent event. The same four should read granted.
  3. After a decline: Google’s state. Start again in a fresh private window and click Decline. The most recent Consent event should still read denied for all four.
  4. After a decline: other tags. In the same session, open the Tags tab and click the Meta Pixel. It should show as not fired. It only will if it has its own consent check.
  5. A return visit. Accept, then reload. The update straight after the default should carry the earlier answer before the Google tags fire.

If the Consent tab is empty, Google says Consent Mode isn’t implemented on that page. First check that Enable Google Consent Mode is still ticked. For a test from outside GTM, with cookies and the Network panel, use How to check Consent Mode v2 is working.

When all five pass, name the container version after what changed (“Cookiebot CMP, global denied default, Consent Initialization”) and publish.

What goes wrong

  • UK typed into a region row. Use GB.
  • The tag on All Pages. Move it to Consent Initialization - All Pages.
  • Enable Google Consent Mode unticked “for testing” and left that way. The template then sets nothing and loads the script with consentmode=disabled.
  • A second default set in the theme. Remove the one outside GTM.
  • Testing only as a first-time visitor. The return visit is a separate path; check 5 covers it.

Should I do it myself?

With a clean container, yes, it’s realistic. It gets harder with an old default in the theme, a second banner, or server-side GTM behind the page, where the server has its own consent handling (Consent Mode v2 with server-side GTM). Client results stay off the record. The five screenshots are the exhibit, for your own site.

Common questions

Where do I find the Cookiebot ID for the GTM template?

On the Your Scripts tab in Cookiebot. The template calls it the Domain Group ID and accepts only a UUID.

Yes. Enable Google Consent Mode starts ticked. Unticked, the template sets no defaults and loads the script with consentmode=disabled.

Sources

Read in November 2026:

  • Usercentrics on GitHub, Cookiebot CMP GTM template source (field names, help text and defaults; Domain Group ID from Your Scripts; Enable Google Consent Mode ticked by default; Default Consent State table with no rows, columns defaulting to denied, blank region for global, ISO-3166-1 alpha-2 codes; Wait for update 2000, added to region rows only; all-denied fallback; Redact ads data Dynamic; URL passthrough; Advertiser Consent Mode; Geo Regions as alternate banners; security_storage always granted; category mapping; stored CookieConsent answer sent as an update; consentmode=disabled when off; changelog to v2.12.7)
  • Usercentrics, Partner Directory (agency listings, Certified and Premium partner tiers)
  • Tag Manager Help, Set up Cookiebot to obtain user consent (points to the Cookiebot CMP template, configure the banner, scanner categorises cookies, “Require additional consent for tag to fire”, additional consent checks and the cookie_consent_update trigger for non-Google tags)
  • Tag Manager Help, consent settings (Consent Initialization trigger for tags that set or update consent, fires before all other triggers; additional checks; consent overview; featured CMP templates)
  • Google for Developers, verify consent mode (earliest and most recent Consent event, API Call, default set too late, empty Consent tab, simulated location per region)
  • Google for Developers, consent mode overview (basic and advanced, cookieless pings, general and advertiser-specific modelling, data threshold)

← back to the reading room