Google Tag Gateway
Google Tag Gateway (GTG) allows Google tags to be served through your website’s first-party domain instead of directly from Google domains.
GTG can be implemented using supported content delivery networks (CDNs), load balancers, or custom infrastructure. When enabled, visitors download Google tag resources through your own domain, which may improve tag durability and measurement reliability.
How GTG affects Consent Mode
GTG can change the order in which scripts are loaded and initialized on your website. Because of this, GTG may affect when consent information becomes available to Google tags.
For Google Consent Mode to work correctly, consent defaults should be established before Google tags begin processing measurement activity that depends on consent state.
If a Google tag initializes before consent defaults have been applied, Google may report a late consent signal.
Verifying GTG enrollment
There are two different things worth confirming, and they are checked in different places.
Confirm a tag is actually being served through GTG
Use Google Tag Assistant. This is the check that reflects what happens in the browser rather than what is configured.
-
Open Tag Assistant and connect to your website.
-
Select the Google tag or container you want to check.
-
Open Summary in the top left. It is selected by default when Tag Assistant opens.
-
In the Tag Details panel, look at the Source field. When GTG is active, the GTG provider’s icon appears beside the source.
-
Hover the icon. The popover confirms the details:
Tag was loaded by Google tag gateway. Platform: [your GTG provider, for example Cloudflare]. Measurement path: [your configured measurement path].
If no provider icon appears in the Source field, the tag is not being served through GTG on that page load.
Confirm GTG is configured for your Google tag
Your GTG configuration lives in your Google tag settings, which you can reach from any of the following Google properties:
- Google Tag Manager — open the Google tags tab, then click the tag name to edit its settings.
- Google Ads — Tools → Data manager → under “Google tag” click Manage, then Admin.
- Google Analytics — Admin → Data streams → select a stream → Configure tag settings → Admin.
- Campaign Manager 360 — Data manager under “Floodlight” → Manage under “Google tag” → Admin.
From Admin, open Google tag gateway for advertisers to review the active domains and measurement path.
Recommended verification methods
We recommend verifying your GTG integration through Google Tag Manager or another Google property, as described above. Google is unable to provide assurance regarding the accuracy of results from other methods, including but not limited to inspecting the browser Network tab or using third-party tools.
For more information, see Google’s Google tag gateway for advertisers documentation and setup guide .
GTG and CookieHub
CookieHub is compatible with Google Tag Gateway. However, deployment architecture can affect how consent signals are applied.
We recommend reviewing the deployment recommendations and troubleshooting guidance before enabling GTG.
Detecting late consent signals with CookieHub
CookieHub continuously evaluates Consent Mode implementations and can detect situations where consent information may be provided after Google Tags begin processing measurement activity. These checks are based on observed tag initialization order, consent state availability, and Consent Mode configuration.
If a potential late consent signal is detected:
- A warning will be displayed in the CookieHub Action Center.
- The issue will be included in website scan reports.
- Additional information and remediation guidance will be provided where available.
Common causes include:
- Google Tags initializing before consent defaults are established.
- Automatic Google Tag setup through GTG while CookieHub is loaded through GTM.
- Incorrect Consent Mode deployment order.
We recommend reviewing any late consent warnings promptly, as they may affect the quality of consent signals received by Google services.
For more detail, see Understanding late consent signals.