Google Tag Gateway

How gtag traffic for Google Ads, GA4, and Floodlight gets served through a first‑party domain instead of Google's own servers.

What it is

By default, gtag.js loads from googletagmanager.com, and every hit it sends travels straight to Google's servers from the visitor's browser. Google Tag Gateway reroutes both of those through a domain the site itself controls: the script is served from your domain, and the transport_url passed into gtag('config', …) points at it too. Google's endpoint sits behind that domain rather than in front of the browser.

The request looks and behaves like any other first‑party call, so it isn't singled out by tracking‑prevention or ad‑blocking rules aimed at third‑party ad domains.

Two ways to turn it on

Every connector that supports Tag Gateway (Google Ads, Floodlight, GA4) exposes both options as constants. They resolve in order: the JENTIS‑managed toggle wins if it's on; otherwise a manually entered gateway URL is used; otherwise the connector falls back to Google's own CDN as before.

Option 1: Bring your own gateway

For teams who've already setup up Tag Gateway themselves (a CDN or reverse proxy CNAME'd to Google's fps.goog endpoint ) independent of JENTIS.

1. Set up and verify your own first‑party routing, per Google's Tag Gateway setup docs.

2. Paste the resulting URL into the connector's Google Tag Gateway URL constant.

3. JENTIS loads gtag.js from it and sends it as transport_url, unchanged.

Google Tag Gateway URL → yourdomain.com/<path_created>

Option 2: JENTIS one‑click gateway

For teams who want Tag Gateway without setting it up on their own.

1. Switch on Enable JENTIS Google Tag Gateway on the connector.

   1. JENTIS builds the URL for you, using your own JENTIS tracking domain. There is no additional CNAME or proxy to maintain.

   2. The URL encodes the session, the ID, and the container, so Google can resolve the right config per hit.

https://<hash>.yourdomain.com/g/<configURL>

Please consider that using this 2nd option can results in errors in the console or in the network requests tab, if gtag tries to load files from the wrong domain. You can ignore this as tracking should be working as per usual.