Google Tag Gateway, or GTG, is a Google feature that lets advertisers load Google tags using their own first-party infrastructure instead of loading those tags directly from a Google domain.

In a standard Google tag setup, the browser requests the Google tag from a Google domain. With Google Tag Gateway, your website loads the Google tag from your own first-party domain, and some measurement requests are sent to Google using that first-party domain. Google says GTG can be set up using a content delivery network, load balancer, or web server.

GTG can improve signal durability and give advertisers more control over their tagging infrastructure. However, it can also affect when Google tags load on your website. This is important for Google Consent Mode because consent defaults must be available before Google tags send measurement data.

Read this article if:

For general Consent Mode setup, start with Google Consent Mode Quickstart.

A late consent signal means that a Google tag fired before the required consent controls were available on the page.

This usually means one or both of the following happened:

Google’s Consent Mode documentation says the default consent command should be called before commands that send measurement data, such as config or event. Google’s troubleshooting documentation also states that the website should set the default consent state before tags or other code use or update consent.

When Enzuzo detects late consent, you should first identify the affected Google tag, then check whether that tag is enrolled in Google Tag Gateway.

Google Tag Gateway can change how Google scripts are loaded on your website.

This matters because Consent Mode depends on load order. Enzuzo, or your Consent Mode default command, needs to initialize before Google tags rely on consent state.

Some GTG setups use a CDN or automated integration to insert or rewrite Google tag scripts. Google notes that if you use Consent Mode, you must turn off automated script setup. Google also says automated setup can insert new scripts into your HTML, and that you should disable automated setup if you want to maintain control over your code and its placement.

Because of this, one-click CDN injection or automated GTG setup may prevent your team from fully controlling whether the CMP script, Consent Mode default command, or TCF stub loads before Google tags.

You can check GTG status in the Google product where your Google tag is managed.

Google lists this as the path for accessing Google tag settings from Google Ads.

Google lists this as the path for accessing Google tag settings from Google Analytics.

Google lists the following GTG statuses in Google Tag Manager:

You can also use Google Tag Assistant to confirm whether your GTG setup is working.

Google recommends this method for validating whether GTG hits are routed through the expected measurement path.

If Enzuzo compliance scan reports late consent:

If a late consent signal is detected and the affected tag is enrolled in GTG, Enzuzo recommends using U+C / advanced Consent Mode for most GTG-enabled Google tag setups.

In this article, U+C means allowing Google tags to load while using Consent Mode defaults and consent updates to control tag behavior. Google refers to this more broadly as advanced Consent Mode.

With advanced Consent Mode, Google tags load when the page opens, default consent states are applied, and tags adjust behavior after the visitor makes a consent choice. Google says that when consent is denied, Google tags may send cookieless pings, and when consent is granted, tags send full measurement data.

This approach is recommended for GTG-enabled tags because it is compatible with manual GTG setups where Google tags may load early, while still allowing consent defaults and updates to control Google tag behavior.

Google also recommends unblocking Google tags when using Consent Mode to get the full benefits of Consent Mode. Google explains that if Google tags are delayed or blocked until a consent interaction occurs, modeled conversions may be less accurate and behavioral modeling in Google Analytics may be unavailable.

Important: Your Consent Mode setup should reflect your legal requirements, regional requirements, and internal privacy policies. This article is not legal advice.

If you adopt U+C / advanced Consent Mode with GTG, review Google’s Data Transmission Controls.

Google’s Data Transmission Controls are available in Google tag settings for Google Ads, Google Analytics, and Campaign Manager 360. Google notes that Consent Mode must be activated before Data Transmission Controls can be used.

Use these controls according to your business, measurement, and legal requirements.

If GTG is active and Enzuzo reports late consent, you should also review your Google tag default consent settings.

In Google tag settings, Google provides a Set consent mode override setting. This can override default consent settings in website code and set the default to denied for selected regions. Google says this can help when existing default consent commands do not take effect before Google tags load, such as when a website builder or CMS does not allow control over plugin load order.

Google also notes that this setting applies only to the tag being configured, so you must configure it for each relevant Google tag on your website.

Use Global Consent Defaults / consent mode override according to your regional consent requirements.

If you need better control over script and tag order, move your Google and third-party tags into Google Tag Manager.

In this setup:

Google says the GTM Consent Initialization trigger is designed to make sure consent settings are honored before other triggers fire, and that it fires before all other tags, including Initialization triggers.

For step-by-step setup, see Google Tag Manager (GTM) Configuration.

If you cannot migrate all tags into GTM, use a manual GTG setup where your development team controls the script import order.

In this setup, your developer should make sure the page loads in the correct order:

Google’s developer documentation explains that GTG can be set up using first-party infrastructure such as a CDN, load balancer, or web server. Google also says that self-service GTG setup requires manually updating website tag script sources to point to the new measurement path.

Use this approach only if your team can control script order across all relevant pages.

After updating your setup, verify that Consent Mode is working correctly.

Use Enzuzo compliance scan, Google Tag Assistant, or GTM Preview mode to check that:

Google’s Tag Assistant documentation for Consent Mode verification recommends checking the earliest Consent event, confirming the expected Consent Mode parameters, and reviewing which tags fired or were blocked.

If Enzuzo reports late consent and the affected Google tag is enrolled in GTG, Enzuzo recommends the following order of fixes:

If you do not use GTG, review your regular Google Tag Manager (GTM) Configuration or gtag Consent Mode Integration setup instead.