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
You can verify whether a Google tag is enrolled in GTG using Google Tag Assistant.
Google provides documentation on how to verify GTG enrollment and identify whether a tag is being served through GTG infrastructure .
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.