Google Tag Gateway Guide

Google Tag Gateway (GTG) changes how Google tag scripts are delivered to your visitors. If your site uses GTG, you need to take specific steps to ensure your Consent Mode implementation continues to work correctly. This guide explains what GTG is, how to detect it, and what to do when it causes consent issues.

What is Google Tag Gateway?

Google Tag Gateway is a server-side tag delivery mechanism that serves Google tag scripts – such as Google Ads and Google Analytics 4 – from your own domain’s CDN instead of Google’s servers (www.googletagmanager.com).

GTG is typically enabled through a “one-click CDN injection” option in Google Tag Manager. Once enabled, Google’s infrastructure automatically routes tag script delivery through a subdomain of your site (for example, cdn.yoursite.com/gtm.js).

Why GTG affects consent load order

When GTG is enabled via one-click CDN injection, the tag script loads very early – often before your CMP script has had a chance to fire the consent default command. This creates a situation where consent signals arrive after the Google tag has already started executing, known as late consent.

Late consent means:

• Google tags execute before knowing the user’s consent status
• Data may be collected before consent is given
• Your Consent Mode implementation does not meet Google’s technical requirements

How to verify if your tag is enrolled in GTG

Method 1 – Chrome DevTools Network tab

1. Open your site in Chrome and press F12 to open DevTools
2. Go to the Network tab
3. Reload the page
4. In the filter box, search for gtm.js
5. Check the domain in the Name column:
   • If it shows www.googletagmanager.com/gtm.js → GTG is not active
   • If it shows your own domain (e.g. cdn.yoursite.com/gtm.js) → GTG is active

Method 2 – Consentik diagnostic tool

1. Log in to your Consentik dashboard
2. Go to Google Consent Mode V2
3. Scroll to the Consent Mode Diagnostic section
4. Click Run diagnostic scan
5. Check the Tag Gateway column in the results table — it shows the GTG domain if active

Method 3 – Google’s official enrollment checker

Use the Tag Manager verification guide from Google to check whether your container is enrolled in GTG.

What to do when late consent is detected with GTG

If your Consentik diagnostic tool flags a Late consent error on a page that also has an active Tag Gateway, you have three options.

Option 1 (Recommended): Enable Advanced Consent Mode (U+C)

Advanced Consent Mode – also called U+C (Unordered Consent) – allows Google tags to run before consent is given, but restricts what data is collected until the user makes a choice. This is the only mechanism that is guaranteed to work when GTG controls the script load order, because it removes the dependency on load timing entirely.

Steps to enable Advanced Consent Mode in Consentik:

1. In your Consentik dashboard, go to Settings → Consent Mode
2. Switch from Basic to Advanced mode
3. In your GTM container, enable Data Transmission Controls
4. Set Global Consent Defaults appropriate for your region
5. Re-run the diagnostic scan to confirm the issue is resolved

Why this works:

• The tag runs but restricts data collection until consent is received from your CMP
• No dependency on script load order – works regardless of when GTG delivers the tag
• Compatible with both one-click CDN injection and manual GTG configurations
• Supported by all Google Ads and Google Analytics 4 products

Option 2: Migrate tags into GTM and deploy GTM via GTG

If you have tags firing outside of GTM, move them into a GTM container and deploy GTM itself via GTG. GTM will respect your CMP’s consent signals before firing tags, giving you control over the data collection flow.

Option 3: Configure GTG manually

Instead of using one-click CDN injection, configure GTG manually. This allows you to control the script import order and ensure your CMP script loads and fires the consent default command before the GTG-served tag script executes.

This option requires technical knowledge of your CDN configuration and is recommended only for teams with dedicated infrastructure engineers.

Summary: which option to choose

Further reading

• Google Tag Gateway overview — Tag Manager Help
• Advanced Consent Mode (U+C) — Google Developers
• Consent Mode setup guide — Consentik Documentation
• Verify your Consent Mode implementation — Consentik Diagnostic Tool