COKIQ docs
What Google tag gateway for advertisers changes for consent, how to check if your Google tag uses it, and how to fix a late consent signal with COKIQ.
Site owners, marketers and agencies who use COKIQ with Google tags served through Google tag gateway (Cloudflare, Akamai, Google Cloud or a manual setup).
Google tag gateway for advertisers (GTG) serves your Google tag from your own domain instead of a Google domain. Google: "Google tag gateway for advertisers lets you deploy a Google tag using your own first-party infrastructure, hosted on your website's domain."
Without GTG the page loads the Google tag from www.googletagmanager.com. With GTG it loads from a path on your own domain (for example https://www.example.com/abcd/?id=G-XXXX), and some measurement requests go to your domain, which forwards them to Google. GTG changes how data reaches Google, not whether consent is needed.
Consent Mode only works if the consent default is set before a Google tag runs. One-click CDN setups (for example Google Tag Manager > Admin > Google tag gateway with Cloudflare) often inject the Google tag into your pages at the CDN. You usually cannot control where it is injected, so the Google tag can run before COKIQ sets the default: a "late" consent signal.
In basic mode COKIQ holds Google tags until consent. COKIQ also recognises first-party gateway URLs (any script URL with ?id=G-, GT-, GTM-, AW- or DC-). A tag that a CDN injects into the HTML before the COKIQ script runs cannot be held by any script on the page.
U+C (advanced consent mode) is the recommended mechanism for GTG-enabled tags because it is compatible with manual GTG: tags load, read the consent state and only send full data once consent is granted.
Step 1
In Google Tag Manager open Admin > Google tag gateway. Status "Active" and a domain marked "First-party" means GTG is on for that domain ("Not started", "Paused" or "Pending" means it is not serving yet). In Google Ads or Google Analytics, open your Google tag settings and look for the Google tag gateway section. In the browser, open DevTools > Network and reload: if gtag/js or gtm.js loads from your own domain instead of www.googletagmanager.com, the tag is served through GTG. COKIQ debug mode (?cokiq_debug=1) also prints a warning when a Google tag is served from your own domain.
Step 2
In COKIQ open Banner > Google Consent Mode v2 and choose Advanced. Then, in your Google tag settings, turn on Data Transmission Controls and set Global Consent Defaults according to your needs, so your Google tags behave correctly even if they start before the banner. Advanced (U+C) is the recommended mechanism for GTG-enabled tags because it is compatible with manual GTG.
Step 3
Move your Google tags into a single Google Tag Manager container, deploy that container through Google tag gateway, and add the COKIQ GTM template on the Consent Initialization - All Pages trigger. The template sets the consent defaults (per region) and loads COKIQ before any other tag in the container fires.
Step 4
Use Google's self-service (manual) GTG setup instead of one-click CDN injection, and keep the COKIQ script as the first script in <head>, before the first-party Google tag.
Step 5
Reload a page with ?cokiq_debug=1. The console should say "OK: COKIQ set the consent default before any Google tag ran". Confirm in Tag Assistant (Consent tab) that the default appears before the first Google tag event.
Yes. COKIQ sets the Consent Mode default and update for Google tags served by GTG in the same way as for tags from googletagmanager.com. What matters is the load order: the COKIQ default must come first, or you use advanced mode with Data Transmission Controls and Global Consent Defaults.
First check whether the late tag uses GTG (step 1). If it does, use one of the three options on this page. If it does not, move the COKIQ script to the top of <head> or fire the COKIQ GTM template on Consent Initialization - All Pages.
COKIQ support first (support@cokiq.com), not Google. Send the debug report from the console and we help you fix the order.
