Verify Google Tag Gateway

Before troubleshooting late consent or adjusting script order, first verify whether Google Tag Gateway is actually enabled in your setup.

Google describes GTG as a setup where a Google tag or Google Tag Manager container is served through your own domain. In a standard setup, the tag is loaded from a Google domain. With GTG, the tag is loaded from your first-party domain, and some measurement requests are sent through that domain as well. 

What to verify

Start by checking two things:

• whether the Google tag or GTM container is loaded through your own domain
• whether measurement hits are routed to your measurement path.  

Both parts matter. A container can be loaded through GTG while measurement traffic is still not routed as expected.

Check where the tag is loaded from

Open your site in the browser and inspect the network requests.

Look for the request to gtm.js or gtag.js.

If GTG is enabled, the request should be loaded through your own domain rather than directly from a standard Google-owned host. Google describes this as serving the tag through first-party infrastructure on your website’s domain.  

Check where measurement hits are sent

Google recommends validating the setup in Tag Assistant.

Open Tag Assistant, connect to your site, navigate through the page, and trigger at least one tag. Then go to:

Summary > Output > Hits Sent

Review the requests shown there and confirm that the hits are routed to your measurement path. Google explicitly tells you to verify this in Tag Assistant when validating GTG.

Use CookieTractor debug mode

If you need to inspect how CookieTractor behaves on the page when GTG and Google Consent Mode are in use, add ?ct-debug=true to the URL to open CookieTractor Debug Mode. 

Reopen the banner, click Read more about our cookies, and review the Debug section at the bottom of the expanded panel. Use it to check whether Consent Mode is active and whether anything suggests a timing issue. 

What you should see

A GTG-enabled setup should give you evidence that:

• the Google tag or GTM container is served through your own domain
• the setup is active for the domain you are testing
• measurement hits are routed to the configured measurement path.  

If one of those parts is missing, treat the setup as incomplete and review your GTG configuration before moving on.

If GTG is not clearly verified

If you cannot confirm that GTG is enabled, or if hits are still going directly to Google-owned endpoints, review your GTG configuration and measurement path before treating the issue as a normal late-consent or script-order problem.

Related information