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

READING ROOM › FIELD NOTE › NOTE-019

NOTE-019 · FIELD NOTE FILED 10 NOV 2026 · REVISED 10 NOV 2026 F-201

Consent Mode v2: do you need a consultant or is the CMP setup enough?.

ABSTRACT — A certified CMP's Google Tag Manager template handles Google's side of Consent Mode v2. Meta and other non-Google tags, tags outside GTM, the basic-or-advanced choice and the day-14 check stay with you. When the template is enough, when it isn't, and how to tell.

Baris Asa, Synctag, tracking specialist, London · Last checked: 10 November 2026

Often the CMP setup is enough. A certified CMP (the cookie banner tool, such as Cookiebot or CookieYes) ships a Google Tag Manager template that sets the Consent Mode v2 defaults and passes the visitor’s answer to Google’s tags. For one site, one banner and only Google’s ad tags, that covers it. You need a person when Meta or other non-Google tags run alongside. Or when tags sit outside GTM, or nobody chose basic or advanced mode. Or when Google Ads conversions fell further than your refusal rate and, two weeks on, still don’t show “modeling is active”.

That last status decides whether Google Ads estimates the conversions from visitors who refused cookies, or goes without them.

Synctag (Baris Asa, London) is a UK tracking consultancy for privacy-first tracking and consent management: Consent Mode v2 on Cookiebot, CookieYes and other banners in Google Tag Manager, for online shops and the agencies behind them, tested on reject as well as accept. I sell this work, so weigh what follows with that in mind. I have no partnership, affiliate or commission arrangement with any consent platform. Where Consent Mode sits among the other privacy layers is in privacy-first tracking in the UK.

What does the CMP template do on its own?

Google recommends a CMP for sites on Google Tag Manager, and CMPs publish templates in the Community Template Gallery for it (Google’s guide). Installed as the vendor says, a template does three things:

  1. Sets the defaults. Each consent type starts at denied or granted before the visitor answers, with rows by region.
  2. Fires first. The vendor guides put the tag on the Consent Initialization trigger, which runs before every other trigger (GTM consent settings).
  3. Sends the update. When the visitor clicks, the template maps the banner’s categories onto Google’s consent types and tells Google’s tags.

CookieYes’s guide is a fair example. Its Advertisement category sets ad_storage, ad_user_data and ad_personalization; Analytics sets analytics_storage; regions are ISO 3166-2 codes or “All”; the trigger is Consent Initialization, All Pages (CookieYes documentation). Cookiebot’s template works the same way; its region field, trigger and script blocking are in Cookiebot and GTM Consent Mode v2, and the template field by field is in setting up Cookiebot with Consent Mode v2 in GTM.

Google’s tags then adjust themselves, because they have built-in consent checks (GTM consent settings). The template handles Google’s side properly. Google’s CMP Partner Program lists Cookiebot, OneTrust, CookieYes and Usercentrics at Gold tier as of 10 November 2026, a badge for products “integrated with Consent Mode and Google Tag Manager” (CMP Partner Program). The badge is about the product, not your installation.

What does the CMP setup leave to you?

Five things the GTM template doesn’t settle:

Left to youWhy the template doesn’t settle itWhat it costs if missed
Consent on Meta, TikTok and other GTM tagsNo built-in check; each tag needs its own settingThey ignore the banner’s answer
Tags hard-coded in the siteGTM’s per-tag settings don’t reach themHits before the default; duplicates if also in GTM
Basic or advanced modeSet by how the tags are wired, often by accidentA modelling level nobody chose
Which regions get which defaultYour lawyer’s call, typed into the templateUK visitors on the wrong default
The day-14 checkGoogle reports status days laterModelling never starts, unnoticed

Non-Google tags in GTM. A tag without a built-in check needs “Require additional consent for tag to fire”, and a trigger on the banner’s own consent event. GTM’s Consent Overview lists every tag still marked “Consent Not Configured”; switch it on first in Container Settings (GTM consent settings). It’s the gap I find first after a template install: the CMP did its part, nobody set consent on the Meta tags.

Tags outside GTM. Two different cases. A non-Google tag pasted into the theme, or added by a platform’s own Meta app, ignores the banner entirely unless the CMP’s script blocking catches it. A Google tag hard-coded in the theme shares the page’s consent state, but it can fire before the template has set the default, and Google says the default has to come “before any commands that send measurement data” (Google’s guide). Move it into GTM, or put a consent default snippet above it. Some CMPs also offer automatic script blocking: CookieYes says it blocks third-party cookies before consent (CookieYes GTM guide). That is a separate install with its own load-order rules.

Basic or advanced. In basic mode, Google’s tags don’t load until the visitor answers, and Google Ads models conversions from a general model. In advanced mode, they load and send cookieless measurements while consent is denied, and Google Ads gets an advertiser-specific model (Google’s consent mode overview). A template install often lands on one without anyone choosing. If Google’s tags load behind denied defaults, that is advanced; if the CMP’s script blocking holds them back, that is basic. The trade-off is in basic vs advanced.

Regions. Which visitors start at denied is a decision for your data protection lead or lawyer, not for the CMP or for me. The template applies it. Google’s EU user consent policy covers the EEA, the UK and Switzerland (Google’s policy).

When is the CMP setup enough?

When all of these are true:

  • Every tag on the site lives in one Google Tag Manager container.
  • The only ad and analytics tags are Google’s (Google Ads, GA4, Floodlight).
  • One banner covers one site, with no checkout or booking step on another domain.
  • Someone chose basic or advanced on purpose and wrote it down.
  • The day-14 check below passes checks 1 to 3, and 4 and 5 where your volumes clear Google’s thresholds.

Not sure where your tags live? Ask whoever runs GTM for the tag list, and check your shop platform’s installed apps for a Google or Meta channel app. Anything outside GTM puts you in the next list.

When is the CMP template not enough?

When one of these is true:

  • Meta, TikTok or another ad platform runs alongside Google’s tags, in the browser or through a server container.
  • Conversions fell from the day the banner went live, by more than the refusal share the banner dashboard shows. The cause may be wiring, not refusals (why conversions drop after Consent Mode v2).
  • A server-side GTM container sits in the path, and consent has to reach it too (Consent Mode v2 with server-side GTM).
  • More than one site, banner or region, or an agency managing consent across client containers.
  • Day 14 has passed and Google Ads still says “Consent mode is implemented” with no “modeling is active”, on an account that clears the click threshold.

Some of these are a day’s work for a developer who knows GTM. The person you hire doesn’t have to be me. Three questions to ask them:

  1. Will you test reject and a partial choice, not only accept, from a UK location?
  2. Will you show me Consent Overview with no non-Google tag left at “Consent Not Configured”?
  3. After two weeks, which side of Google’s thresholds am I on?

Five more checks for the finished job are in how to judge a Cookiebot and GTM Consent Mode expert. If you commission an audit rather than a fix, what it should hand back is in what a Consent Mode v2 audit covers.

How do you check the setup at day 14?

Five checks. The first three are for whoever owns the container and work on day one. You can do check 4 yourself. Check 5 needs volume.

  1. Defaults first. Tag Assistant’s Consent tab, fresh visit, nothing clicked: ad_storage, ad_user_data, ad_personalization and analytics_storage each have a default before any tag fires.
  2. Reject reaches Google. After reject, all four read denied. After a partial choice (analytics yes, marketing no), the three ad types stay denied. Screen by screen: how to check Consent Mode v2 is working.
  3. Non-Google tags wait. In GTM’s Consent Overview, no non-Google tag that sets cookies is left at “Consent Not Configured”. Google’s tags with built-in checks can be marked “No additional consent required”.
  4. Google Ads status (you can do this one). Goals, then Conversions, then Summary; pick a website conversion action and open Diagnostics. You want “Consent mode is implemented and modeling is active”. The status can take 48 hours to appear, in some cases up to two weeks, and modelling needs at least 700 ad clicks over 7 days per domain and country, which doesn’t guarantee it (Google Ads Help).
  5. GA4 modelling. Advanced mode only, and only at volume: 1,000 events a day with analytics_storage denied for 7 days, and 1,000 daily users with it granted on 7 of the last 28 days. Modelled data shows only under the Blended reporting identity, and meeting the numbers doesn’t guarantee it (GA4 Help).

A smaller account may never cross the thresholds in 4 and 5. That isn’t a fault and it isn’t a reason to hire anyone. It means you shouldn’t count on modelled conversions.

What does a day-14 check look like on a template install?

On a template install, the Google side usually passes and the gap is a non-Google tag the template never touched. In this exhibit, every Google check passed and the Meta pixel ignored the banner.

Exhibit: one site, GB region, CMP template from the gallery, day 14. The failing row in bold.

CheckResultSet by
Defaults before tagsPassCMP template
Reject and partial choicePassCMP template
Google Ads DiagnosticsModeling is activeGoogle’s tags, at volume
Meta pixel consentConsent Not Configured, All PagesContainer owner

Reconstructed · client data anonymised

The Meta tag fired on page load whatever the visitor chose, so the banner’s answer never reached it. A consent check alone, with no update trigger, would have swung the other way: anyone who accepted mid-page would have been missed. Filed under F-201 , the nearest code: the Google side passed, the container wiring around it didn’t.

Fix: swap the All Pages trigger for the CMP’s consent-update event (the name is in the vendor’s GTM guide), and keep an additional consent check on ad_storage as a second guard. In Preview, confirm the event also fires on page load for a returning visitor who already accepted, not only on the click. Re-test: the Meta tag absent from the network log after reject, present once after accept.

Common questions

It sets up the Google side: the default for each consent type, by region, and the update when the visitor answers. Consent checks on Meta and other non-Google tags, tags hard-coded outside GTM, and the choice of basic or advanced mode stay with whoever owns the container.

Often, yes. If every tag lives in Google Tag Manager, the only ad tags are Google’s, and one banner covers one site, the vendor’s template and its guide will get you most of the way. Run the day-14 check on this page. Pass checks 1 to 3, and 4 and 5 where your volumes clear Google’s thresholds, and you don’t need anyone.

The browser test works on day one. Google Ads can take 48 hours, and in some cases up to two weeks, to show its consent mode status on a conversion action, and modelling needs at least 700 ad clicks over 7 days per domain and country. Check Google Ads Diagnostics at day 14.

Is a CMP partner badge from Google a guarantee the setup is correct?

No. Google’s CMP Partner Program badges vendors whose product is integrated with Consent Mode and Google Tag Manager, ranked Gold, Silver and Bronze. It says nothing about your installation. Google also says advertisers don’t have to use a partner CMP to adopt Consent Mode.

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

Sources

Read on 10 November 2026:

  • Google for Developers, set up consent mode on websites (CMP recommended for Tag Manager; CMP templates in the Community Template Gallery; default before any commands that send measurement data; ISO 3166-2 regions)
  • Tag Manager Help, consent settings (built-in and additional consent checks; Consent Overview, enabled in Container Settings; Consent Initialization trigger; featured CMP templates)
  • Google, CMP Partner Program (badge for CMPs integrated with Consent Mode and GTM; Gold, Silver and Bronze tiers; Cookiebot, OneTrust, CookieYes and Usercentrics listed Gold; advertisers may use a non-partner CMP)
  • CookieYes, implementing Google Consent Mode using CookieYes, updated 10 July 2026 (category mapping; region codes; Consent Initialization, All Pages trigger) and getting started with Google Tag Manager and CookieYes (automatic blocking of third-party cookies before consent; custom event trigger for GTM-loaded tags)
  • Google for Developers, consent mode overview (basic and advanced; general and advertiser-specific models; many CMPs send the consent state to Google)
  • Google Ads Help, set up and manage consent (Diagnostics statuses; 48 hours, in some cases up to two weeks; 700 ad clicks over 7 days per domain and country)
  • Google Analytics Help, behavioural modelling for consent mode (thresholds; tags load in all cases; Blended reporting identity; no guarantee)
  • Google, EU user consent policy (EEA, UK and Switzerland)

— B.A., filed from London

CONNECTED RECORDS F-201

REVISION HISTORY — revised 10 NOV 2026.

← back to the reading room