Skip to main content
Version: development

Google Tag Gateway (GTG)

In this introductory guide to Google Tag Gateway (GTG), you will learn what GTG is, what technical consequences it may have, and how to verify whether it is active on your website.

Google Tag Gateway (GTG) allows Google tags (gtm.js, gtag.js) to be served from your own domain, instead of being loaded directly from Google domains. This page focuses on:

  • What GTG is and why it matters
  • What technical consequences it may have
  • How to verify whether GTG is active on your site
  • Where to review its impact on consent and late default

What is Google Tag Gateway (GTG)?​

As mentioned above, Google Tag Gateway (GTG) allows Google tags to be served from your own domain, instead of being loaded directly from Google domains.

Difference between GTG and non-GTG
  • Without GTG: https://www.googletagmanager.com/gtm.js?id=GTM-XXXXXX
  • With GTG: https://<your-domain>/gtm.js?id=GTM-XXXXXX

GTG provides a lightweight alternative to server-side tracking for sites that want to:

  • Avoid ad blockers that block requests to googletagmanager.com.
  • Improve performance by reducing third-party DNS requests.
  • Increase tracking resilience against browser restrictions such as ITP and ETP.

Unlike server-side tagging, which requires a dedicated GTM server, GTG can be enabled with a single click from the GTM interface.

What GTG does not do:

  • It does not ignore or override the user's consent choices.
  • It does not collect additional data by itself.
  • It changes where tags are served from, not the consent logic.
Additional information

You can find more information about GTG in Google's official documentation:

Technical consequences of GTG​

Google Tag Gateway changes how Google tags are served, so it is recommended to review some technical aspects after enabling it:

  • The source domain for tags becomes your own domain instead of googletagmanager.com.
  • It can reduce reliance on third-party resources during tag loading.
  • It can change when certain scripts are loaded or executed.
  • It can reveal existing load-order issues, especially in implementations that depend on Google Consent Mode.

What is a late default?​

In Google Consent Mode, the consent state must be defined before any Google tag, such as GA4 or Google Ads, runs or checks that state. We refer to a late default when that signal arrives too late: the tag has already fired, or has already read the consent state, before Lawwwing set it.

In GTG environments, this usually happens for two reasons:

  • The Google script loads before the Lawwwing script.
  • Asynchronous loading changes the expected order and the Google tag starts first.

Why does it matter? Because Google requires default consent values to be available from the start. If they are not, events may be considered non-compliant and affect features such as conversion measurement, audiences, and remarketing.

Why can Google Tag Gateway deployments create load-order issues?

When Google Tag Gateway is enabled through one-click CDN integrations, script injection may happen before your page-level script order is applied. This can reduce your control over whether Lawwwing initializes before Google tags.

note

Google Tag Gateway does not create this issue by itself. What usually happens is that it reveals a pre-existing load-order issue by changing when some scripts are injected. It makes an existing problem visible.

For the specific impact on consent and how to resolve a late default, see the dedicated guide:

How to verify whether you are using Google Tag Gateway​

Lawwwing cannot automatically detect whether your website is using Google Tag Gateway. Verification must be done manually.

tip

For the official verification steps, review the Google Tag Manager help center

Here are some quick ways to verify it:

1. Review the page source code​

Inspect the <script> that loads gtm.js or gtag/js.

Tag served via GTG:

<script async src="https://<your-domain>/gtm.js?id=GTM-XXXXXX"></script>

Tag not served via GTG:

<script async src="https://www.googletagmanager.com/gtm.js?id=GTM-XXXXXX"></script>

2. Review the browser Network tab​

Filter by gtm.js or gtag, reload the page, and review the domain of each request:

  • <your-domain>/gtm.js?id=... indicates that GTG is probably active
  • www.googletagmanager.com/gtm.js?id=... indicates that GTG is not active
warning

The script name may have been customized. GTG allows the container file name, which is gtm.js by default, to be changed. If that name has been modified, searching the source code may not return any results.

3. Review Google Tag Assistant and Google Tag Manager Admin​

Use Google Tag Assistant to review which domain is serving the tags and validate GTG indicators in GTM Admin.

tip

Containers implemented through GTG show a dedicated badge or mention in the container Admin section. Check the Google Tag Manager help documentation for the exact labels.

Frequently asked questions about Google Tag Gateway​

Does Google Tag Gateway replace server-side tagging?

No. Google Tag Gateway (GTG) does not replace a server-side Google Tag Manager implementation. GTG only changes the domain from which Google tags are served, whereas server-side tagging requires a dedicated server that processes and forwards data.

Does Google Tag Gateway improve data collection?

It can improve tag-loading reliability by reducing blocks associated with third-party domains, but it does not collect additional data or change the measurement behavior configured in Google Analytics or Google Ads.

Does Google Tag Gateway affect user consent?

Not directly. GTG does not change consent choices or bypass Google Consent Mode. However, it can make load-order issues more visible, which may lead to late default situations if Google tags run before the CMP platform sets the consent state.

Can Google Tag Gateway cause a late default error?

Not by itself. What usually happens is that GTG changes when certain scripts load and reveals load-order issues that were already present. If Google tags initialize before your CMP, a late default can occur.

How can I tell if Google Tag Gateway is active?

You can review the page source, inspect network requests in the browser's Network tab, or use Google Tag Assistant. If tags load from your own domain instead of googletagmanager.com, GTG is probably active.

Do ad blockers still affect GTG?

It depends on the blocker being used. Some blockers rely on domain lists, and GTG can help avoid certain blocks by serving scripts from your own domain. However, it does not guarantee that all blocking tools will stop detecting the tags.

Do I need to change my Google Consent Mode implementation when enabling GTG?

Not necessarily. The important thing is to verify that consent states are set before any Google tag runs. After enabling GTG, it is recommended to review load order and validate that no late default issues appear.

Does Google Tag Gateway improve my website's performance?

It can reduce some third-party dependencies and avoid certain external DNS queries, although the real impact will depend on your site's architecture and how the tags are configured.

Is it possible to customize the gtm.js file name?

Yes. Google Tag Gateway allows you to customize the name of the file that serves the container. For this reason, searching only for gtm.js in the source code may not be enough to confirm whether GTG is active.

More information

If you need more information about Google Tag Gateway, or if you have further questions, feel free to contact us through any of our support channels.