Skip to main content
 

Google Tag Gateway (GTG): Consent Impact, Configuration, and Recommended Approaches

  • Updated

What is GTG?

Google Tag Gateway (GTG) is a first-party tag delivery solution that routes Google tag requests through your own domain, rather than loading them directly from Google's servers.

GTG can be deployed in three ways:

  • One-click CDN injection: Google tags are automatically served through the gateway via CDN, with no manual script configuration required.

  • Via Google Tag Manager: GTM is deployed through GTG, consolidating all tag delivery under the gateway.

  • Manual setup: The customer configures GTG directly and controls how and when scripts load on the page.

 

Depending on how GTG is deployed, it can affect the order in which scripts load on a page. With CDN-injected setups, tag load order is controlled by the CDN rather than the page's own script sequence, which means Google tags may initialize before your CMP has collected and signaled user consent.

In manually configured GTG setups, the customer controls script import order and can ensure the CMP loads before any tags execute.

If your setup results in Google tags loading before consent is available, the options in the remediation section below address this directly. 

 

How to verify GTG enrollment

To check whether GTG is active on your property, use one of the following approaches:

Google Tag Manager (Recommended)

Open your Google Tag Manager account and navigate to your tag configuration settings: 

Open tag manager > Select Google tags > Choose a Tag > Admin > Verify GTG Adoption and domain.

Or read more from Google Documentation for your specific use case.

Inspect network requests

Alternatively, inspect your site's network requests. If Google tag requests (e.g. for gtag.js or Google Analytics' request path /g/collect) are being served from your own domain's path rather than from googletagmanager.com or www.google-analytics.com, GTG is active.

Via the Usercentrics or Cookiebot CMP

In your CMP dashboard, check whether a GTG label or first-party tag delivery indicator is shown in your tag or vendor configuration. [Exact UI path to be confirmed before publication.]

 

If GTG is active, verify whether Google tags are firing before consent is collected.

In Cookiebot, you can check this in two places:

  • Cookie Scan Report — looks for Google cookies (e.g. _ga) firing before consent.
    Go to: Admin > Cookies & Reports > open the latest report > look for any entries where Blocked until accepted by user is set to No.

     

  • Consent Mode Checker — shows non-essential Google trackers set prior to consent, broken down by implementation type.
    Go to: Admin > Domain & Aliases > scroll to the Consent Mode Checker.

 

Remediation options

If tags are confirmed to be loading before consent and GTG enrollment is verified, the following approaches are available. Each addresses the root issue in a different way.

Implement advanced consent mode and configure Data Transmission Controls and Global Consent Defaults according to your requirements (see Cookiebot GCM Documentation or follow this video guide).

This approach allows tags to load in a consent-pending state while restricting data transmission until consent is granted. Google recommends this approach for GTG-enabled setups because it resolves the load order issue regardless of how GTG is deployed, whether via CDN injection or manual configuration. Customers retain fine-grained control over what data is sent and when, and it allows tags to initialize in a data-restricted state and only transmit data once consent is granted.

Option 2: Migrate to GTM and deploy GTM via GTG

Move all tags into a Google Tag Manager container and deploy GTM itself through GTG. This consolidates tag management under the gateway and ensures that consent controls can be applied uniformly across all tags. It also means non-Google tags managed via GTM benefit from first-party tag delivery in the same setup.

Option 3: Configure GTG manually with controlled script import order

Set up GTG manually so that you control how and when scripts are loaded on the page. This allows you to ensure the CMP loads and collects consent before any Google tags initialize, restoring the load order control available in standard non-CDN tag deployments.

 

For questions about GTG compatibility or consent signal configuration, refer to the Google GTG documentation, the Google developer setup guide, or contact your Cookiebot support team.

Comments

0 comments

Please sign in to leave a comment.