Google Tag Gateway and CookieHub
Google tag gateway (GTG) serves Google tags through your own domain instead of Google’s. It can be set up through a supported content delivery network (CDN) such as Cloudflare, a load balancer or your own infrastructure, and it may improve how durable your tags are and how reliable your measurement is.
CookieHub is compatible with Google tag gateway. Because GTG can change the order in which scripts load, it can also change when Google tags receive consent information, so how you deploy it matters. This page explains the setups CookieHub recommends and how CookieHub flags the late consent signals a wrong setup can cause.
How Google tag gateway affects Consent Mode
Google Consent Mode depends on consent defaults being set before Google tags begin processing measurement that depends on consent. With GTG, a Google tag can load and initialize earlier than before, sometimes before CookieHub or Google Tag Manager has set those defaults.
When that happens, Google may report a late consent signal: the tag started measuring, and the consent information arrived afterwards. Google reports these in Tag Assistant and in Google Ads and Google Analytics diagnostics.
The cause is almost always load order. It is most likely with one-click CDN setups, where the CDN injects and starts the Google tag itself, which often leaves you no control over when it loads relative to your consent script.
Setups CookieHub recommends
Which setup to use depends on how CookieHub and your Google tag are loaded:
CookieHub and the Google tag both in Google Tag Manager (recommended):
The right choice for most sites. GTM controls the initialization order, so consent defaults are in place before measurement starts, and problems are easier to trace.
CookieHub loaded directly on the page (recommended):
CookieHub runs early in the page while GTG serves the Google tag, so consent defaults are usually available in time and you depend less on GTM’s load order.
Automatic Google tag setup through a CDN (use with caution):
Some CDN integrations configure and start the Google tag on their own. If CookieHub is loaded through GTM, the tag can begin measuring before CookieHub has set consent defaults. In that case, let GTM manage the Google tag instead.
A GTM container ID as the GTG tag (not recommended):
Configure GTG with a Google tag ID. Other identifiers can behave unexpectedly, depending on the implementation.
Use advanced Consent Mode for tags enrolled in GTG
Where a Google tag stays enrolled in GTG instead of being managed through GTM, CookieHub recommends advanced Consent Mode. It lets Google tags load and receive consent updates after they initialize while still respecting the consent defaults, so it works with a manual GTG setup where you control the order in which scripts load.
How CookieHub catches late consent signals
CookieHub checks your Consent Mode setup during website scans, looking at the order in which tags initialize, when consent state becomes available and how Consent Mode is configured. When it finds a likely late consent signal, it:
Warns you in the Action Center:
The issue appears as a warning, with guidance specific to your deployment where it is available.
Records it in your scan reports:
The finding is included in your website scan reports, alongside the rest of the scan results.
Points to the likely cause:
Common causes are a Google tag that starts before consent defaults are set, automatic Google tag setup through GTG while CookieHub loads through GTM, and Consent Mode deployed in the wrong order.
If Google reports a late consent signal
First confirm that the tag really is served through GTG (see below). Then use one or more of these, depending on your setup:
Advanced Consent Mode, so tags can receive consent updates after they initialize.
Global Consent Defaults, which set default consent states before the visitor interacts with the banner.
Data Transmission Controls, for more control over how data is sent to Google services.
Google tags managed through GTM, so consent defaults are applied before measurement begins.
A manual GTG setup, which gives you more control over the order in which scripts initialize.
How to check that GTG is active
Use Google Tag Assistant, which shows what actually happens in the browser:
- Open Tag Assistant and connect to your website.
- Select the Google tag or container you want to check.
- On the Summary view, look at the Source field in the Tag Details panel. When GTG is active, your GTG provider’s icon appears beside the source, and hovering over it shows the platform and measurement path.
To review the configuration itself, open your Google tag settings from Google Tag Manager, Google Ads, Google Analytics or Campaign Manager 360, go to Admin and open Google tag gateway for advertisers. Google recommends checking through these tools, and says it cannot vouch for results from the browser’s Network tab or third-party tools.
Frequently asked questions
Yes. CookieHub is compatible with Google tag gateway and supports Google Consent Mode and Google Tag Manager. How you deploy GTG still affects consent, so check the recommended setups above before you enable it.
GTG serves Google tags through your own domain instead of Google’s, which may improve how durable your tags are and how reliable your measurement is. It can be set up through a supported CDN, a load balancer or your own infrastructure.
Yes. That is the setup CookieHub recommends for most sites, with the Google tag also managed in GTM. Avoid letting a CDN set up the Google tag automatically while CookieHub loads through GTM, because the tag can then start measuring before consent defaults are set.
A Google tag started processing measurement before consent information was available, usually because of the order in which scripts load. Google reports it in Tag Assistant and in Google Ads and Google Analytics diagnostics, and CookieHub flags likely cases in the Action Center and in scan reports.
For Google tags that stay enrolled in GTG, CookieHub recommends advanced Consent Mode, because it lets tags receive consent updates after they initialize while respecting the consent defaults.
A Google tag ID. Using a GTM container ID as the GTG tag is not recommended, because other identifiers can behave unexpectedly, depending on the implementation.
