Google Tag Gateway Guide

Google Tag Gateway (GTG) is a server-side tag delivery mechanism that serves Google tag scripts (like Google Ads, Analytics 4) from your own domain’s CDN instead of Google’s servers.

Why this matters for consent:
When GTG is enabled via “one-click CDN injection” in Google Tag Manager, the Google tag script loads very early — often before your CMP script has a chance to set the consent default command. This means consent signals may arrive after the tag has already started executing (“late consent”).

How to verify if your tag is enrolled in GTG

Official reference: Google Tag Gateway — Google Developers

1. Open your site in Chrome DevTools → Network tab
2. Filter by “Fetch/XHR” or search for gtm.js
3. If the request origin matches your own domain (e.g. cdn.yoursite.com/gtm.js) instead of www.googletagmanager.com, your tag is using GTG
4. Alternatively, consult the Google Tag Gateway documentation for the full enrollment guide

What to do when late consent is detected with GTG

If your Consentik diagnostic tool flags a “late consent” on a page and that page uses GTG, you have the following options:

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

Advanced Consent Mode (also called “U+C” or “Unordered Consent”) allows Google tags to run before consent is given, but restricts what data is collected. This is fully compatible with manual GTG setup.

Steps:

1. In your Consentik settings, select “Advanced” mode instead of “Basic”
2. Enable Data Transmission Controls in your GTM container
3. Set Global Consent Defaults appropriate for your region

Option 2: Migrate into a GTM container and deploy GTM via GTG

Move all your tags into a GTM container, then deploy GTM itself via GTG. This gives you control over the load order since GTM will respect your CMP’s consent signals before firing tags.

Option 3: Set up GTG manually

Configure GTG manually (without one-click CDN injection) so you control the script import order. Ensure your CMP script loads and fires the consent default command before the GTG-served tag script.

Why Advanced Consent Mode is recommended for GTG

When GTG is used with one-click CDN injection, the script load order is controlled by Google’s infrastructure — not your page. The only mechanism that is guaranteed to work in this scenario is Advanced Consent Mode, because:

• The tag runs but restricts data collection until consent is received
• No dependency on script load order
• Compatible with manual GTG configurations
• Supported by all Google Ads and Analytics 4 products

Further reading

• Google Tag Gateway documentation — Google Developers (authoritative reference)
• Advanced Consent Mode (U+C) — Google Developers
• Consent Mode setup guide — Consentik Documentation
• Verify your Consent Mode implementation — Consentik Diagnostic Tool