> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/data-activation/connectors/google-ads/google-tag-gateway-integration-guide.md).

# Google Tag Gateway Integration Guide

## Google Tag Gateway with JENTIS

Google Tag Gateway (GTG) routes Google’s browser tags through a first-party domain.

It acts as a proxy for client-side Google tags, including Google Analytics 4, Google Ads, and Floodlight. Rather than sending requests directly to Google domains, the browser sends them through your domain first.

This can make client-side measurement more resilient to browser restrictions and ad blockers.

### JENTIS Server-Side tracking versus GTG

JENTIS Server-Side tracking remains the primary measurement solution. It provides a substantially larger uplift, typically **20–40%**, by moving tracking logic and data delivery server-side.

GTG can provide an additional, smaller uplift for client-side Google tags. It does not replace server-side tracking.

Use GTG as a complementary proxy layer for Google tags that must remain client-side. This commonly includes signals such as Google Ads remarketing.

{% hint style="info" %}
Use JENTIS Server-Side tracking for primary conversion tracking. Add GTG only for remaining client-side Google signals.
{% endhint %}

### Configure Google Tag Gateway

Google Tag Gateway is available for the following JENTIS connectors:

* Google Ads
* Google Analytics 4
* Floodlight

Open the relevant connectors **tags** in the **JENTIS Tag Manager**. Select the **Google Tag Gateway** tab to choose a gateway option.

{% hint style="info" %}
The Google Tag Gateway placeholder configuration is found in the tags of the mentioned Google connectors. 
{% endhint %}

<figure><img src="https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2Faik1dvXvQChiKDNjg7s9%2Fimage.png?alt=media&amp;token=3ae085e4-8026-4aaf-8129-2b79f8167be1" alt=""><figcaption></figcaption></figure>

#### Configure a Custom Gateway URL

Use a custom gateway URL when your organization needs its own first-party proxy domain. For example, you can create and manage the gateway through Cloudflare.

1. Create the gateway endpoint in your chosen infrastructure.
2. Configure DNS and routing for the custom first-party URL.
3. Open the connector’s tag and expand the **Google Tag Gateway** tab.
4. Enter the complete gateway URL (including "https\://" and save the changes.
5. Preview and validate the container changes then publish your changes through your normal release process.

Ensure the URL is publicly reachable and serves requests over HTTPS. Validate the proxy configuration before deploying it to production.

{% hint style="warning" %}
Custom gateways require DNS and proxy configuration outside JENTIS.&#x20;
{% endhint %}

### Best practices

#### Prevent duplicate conversions

You can use both a client-side Google tag through GTG and a JENTIS Server-Side connector. In this case, send the same `transaction_id` with both conversion events.

Google uses this shared identifier to deduplicate the conversion. Generate one stable ID per transaction and reuse it across all tracking paths.

#### Choose the right use case

Use GTG when client-side Google connectors still deliver required signals. A typical setup uses JENTIS Server-Side tracking for conversions and GTG for client-side remarketing.

Avoid treating GTG as a substitute for a server-side measurement strategy. Its role is to improve the reliability of the client-side tags that remain.

### FAQ

#### Does Google Tag Gateway replace JENTIS Server-Side tracking?

No. GTG complements JENTIS Server-Side tracking. JENTIS should handle primary conversion tracking, while GTG proxies supported client-side Google tags.

#### Do I need a new DNS record?

You need DNS configuration when using a Custom Gateway URL, this is configured outside of JENTIS with your Content Delivery Network (ie. Cloudflare) or Webserver.

#### Will JENTIS Support Google Tag Gateway DNS and Routing natively?

Yes, we are working on an option to host the GTG within your JENTIS services, making the configuration more convenient and easy to activate. This will come in the future.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.jentis.com/data-activation/connectors/google-ads/google-tag-gateway-integration-guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.