Verify Google Tag Gateway

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

You can verify whether a website is enrolled in Google Tag Gateway in Google Tag Manager, Google Ads, Google Analytics or by checking the network requests in your browser.

Check the configuration in Google Tag Manager

Navigate to the Google Tag Manager tool.

1. In the Accounts list, navigate to your container
2. Open the Admin tab.
3. Select Google Tag Gateway.
4. Look for a green label saying "Active" or "First-party", this verifies that GTG is active.

Check the configuration in Google Ads

In Google Ads:

1. Go to Tools > Data Manager.
2. Open the Connected Products tab.
3. Find the Google tag section, select Manage for the relevant tag.
4. In the opened section, go to the Admin tab.
5. Select Google Tag Gateway.
6. Look for a green label saying "Active" or "First-party", this verifies that GTG is active.

Check the configuration in Google Analytics

In Google Analytics, open the relevant Property.

1. Go to Admin > Data Streams.
2. Choose the relevant data stream.
3. Select Configure tag settings.
4. Open the Admin tab.
5. Select Google Tag Gateway.
6. Look for a green label saying "Active" or "First-party", this verifies that GTG is active.

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