> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/optimize-your-setup/google-tag-gateway-gtg/setup-gtg-without-cloudflare.md).

# Setup GTG without Cloudflare

Configure GTG using Google Cloud Platform, Akamai, or a manual reverse proxy — for setups that don't run on Cloudflare.

{% content-ref url="/pages/I26hhzVcMZdudkKjSP44" %}
[Google tag gateway (GTG)](/optimize-your-setup/google-tag-gateway-gtg.md)
{% endcontent-ref %}

*Extended guide for alternative configurations.* This article covers setting up Google Tag Gateway (GTG) when you're not using Cloudflare: Google Cloud Platform, Akamai CDN, and manual configuration with other CDNs or web servers.

## 1. What is Google Tag Gateway?

Google Tag Gateway for advertisers lets you serve Google tags (GA4, Google Ads, or GTM) through your own first-party infrastructure. The tag loads from your domain instead of directly from Google's servers.

{% hint style="info" %}
**Important nuance**

Google Tag Gateway is not a replacement for server-side tagging — it's a lightweight addition. Your AdPage container gives you full data enrichment, server-set cookies for a longer lifetime, better privacy compliance, and integration with non-Google destinations. GTG is a solid first step for first-party delivery, but it doesn't offer the same functionality.
{% endhint %}

### 1.1 Benefits of Google Tag Gateway

* **Improved conversion data** — Google reports an average 11% improvement in conversion signal collection
* **First-party tag delivery** — tags load from your own domain, which can bypass some ad blockers
* **Simple implementation** — considerably less complex than a full server-side GTM setup
* **Lower cost** — no separate tagging servers required
* **Trusted Execution Environment** — improved privacy through TEE processing

### 1.2 Limitations of Tag Gateway (vs. server-side tagging)

* **No data enrichment** — you can't add server-side data to events
* **Limited cookie control** — cookies are still set client-side (ITP limitations remain)
* **Google tags only** — no support for Meta, TikTok, or other platforms
* **No custom transformations** — data passes through to Google unchanged
* **Limited debugging** — less visibility into what's actually happening

### 1.3 Do I need to change my nameservers?

Depends on the method:

| Method                | Change nameservers? | Notes                                                                                  |
| --------------------- | ------------------- | -------------------------------------------------------------------------------------- |
| Cloudflare            | ✅ Yes               | You need to move your nameservers to Cloudflare (unless you use a CNAME/partial setup) |
| Google Cloud Platform | ❌ No                | You only adjust your load balancer configuration. DNS stays where it is.               |
| Akamai                | ❌ No                | If you're already an Akamai customer, you just configure Property Manager rules.       |
| Manual (NGINX, etc.)  | ❌ No                | You only configure your own web server/proxy.                                          |

### 1.4 Available implementation options

| Option                | Complexity | Suited for         | Status               |
| --------------------- | ---------- | ------------------ | -------------------- |
| Google Cloud Platform | Low        | GCP users          | Available (Jan 2026) |
| Akamai CDN            | Low        | Akamai customers   | Available (Jan 2026) |
| Manual setup          | High       | Other CDNs/servers | Always available     |
| Fastly CDN            | Medium     | Fastly customers   | Planned              |

## 2. Google Cloud Platform (GCP) setup

Since January 2026, Google offers a one-click deployment option via Google Cloud Platform — the recommended method if you're already on GCP.

### 2.1 Requirements

* A Google Cloud project with billing configured
* Google Cloud administrator rights for resource management
* Access to Google tag settings via GTM, Google Ads, GA4, or Campaign Manager 360
* A working Google tag (GA4, Google Ads, or GTM) already installed on your site

### 2.2 Step-by-step configuration

{% stepper %}
{% step %}

### Open Google tag settings

**Via Google Ads:** go to your Google Ads account → Tools icon (wrench) → **Data manager** → under "Google tag", click **Manage** → **Admin**.

**Via Google Analytics:** go to **Admin** in your GA4 property → open **Data streams** → select your stream → **Configure tag settings** → **Admin**.
{% endstep %}

{% step %}

### Navigate to Tag Gateway settings

In Admin, click **Google tag gateway for advertisers** → **Continue** on the setup screen.
{% endstep %}

{% step %}

### Check compatibility

Enter a valid website URL → click **Scan** to check whether your site already uses a GCP load balancer → select **Google Cloud Load Balancer** from the list → **Continue**.
{% endstep %}

{% step %}

### Configure the gateway

The system automatically creates and configures:

* **External Application Load Balancer** — routes tag traffic through your first-party domain
* **Backend service** — handles gateway requests to Google's services
* **SSL certificates** — configured automatically for your domain
* **Routing rules** — direct traffic to the right backend
  {% endstep %}

{% step %}

### Adjust settings (optional)

You can override active domains via the edit icon. Adjust the measurement path (make sure it doesn't conflict with existing website routes).

{% hint style="success" %}
**Tip — measurement path:** use a neutral or random path instead of obvious names like `/metrics` or `/tracking` — for example `/v2ur` or `/5n8r`. This lowers the chance that ad blockers interfere with your tracking.
{% endhint %}
{% endstep %}
{% endstepper %}

## 3. Akamai CDN setup

Since January 2026, Google Tag Gateway also supports Akamai CDN — a good fit if you already use Akamai for content delivery.

### 3.1 Requirements

* An active Akamai account with Property Manager access
* One of the following Akamai products: Ion, Dynamic Site Accelerator, or API Acceleration
* A Google Tag ID (obtained via Google)

### 3.2 Configuration steps

{% stepper %}
{% step %}

### Create a new rule

Go to Akamai Property Manager → create a new rule named "Google Tag" → add at least a **Hostname match**.
{% endstep %}

{% step %}

### Configure the Google Tag Gateway behavior

Add the **Google Tag Gateway** behavior → specify your Google Tag ID (obtained via Google) → configure the **Serving Path** (e.g. `/gtag` or a unique path) → under Advanced options, choose whether Akamai or another platform injects the tag automatically.

{% hint style="warning" %}
**Incompatibilities:** The Google Tag Gateway behavior is incompatible with these Akamai behaviors: Brotli Support, Construct Response, and EdgeWorkers. Make sure they're not active in the same rule.
{% endhint %}
{% endstep %}
{% endstepper %}

## 4. Manual setup (NGINX, Fastly, other CDNs)

If you don't use Cloudflare, GCP, or Akamai, you can configure Google Tag Gateway manually with any CDN, load balancer, or web server that supports request forwarding.

### 4.1 Requirements for manual setup

* A working Google tag (GA4, Google Ads, or GTM) already installed on your site
* A CDN or server that supports request forwarding (e.g. Fastly, NGINX, Apache)
* Admin-level access to your domain's DNS
* SSL certificate configuration
* A dedicated path or subdomain (e.g. `/metrics` or `tags.yourdomain.com`)

### 4.2 NGINX proxy configuration

NGINX can act as a reverse proxy to load GTM as a first-party script. A minimal configuration:

```nginx
location /gtm-proxy/ {
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_pass http://app-address;
}
```

* `Host` — sets the Host header on the request to the backend
* `X-Real-IP` — stores the client's original IP address
* `X-Forwarded-For` — carries the client IP plus any proxy server addresses

### 4.3 Docker + NGINX server-side setup

For a more robust implementation, you can run GTM server-side with Docker and NGINX as a proxy:

* Configure two separate subdomains: one for the preview server, one for the tagging server
* Make sure both services are reachable over HTTPS
* Configure the location block with the right proxy headers for client IP preservation

### 4.4 General manual configuration steps

1. Choose a URL path to act as the proxy to Google (e.g. `/v2ur` or `/5n8r`)
2. Configure your CDN/server to forward requests on this path to Google's endpoints
3. Preserve query parameters — make sure all URL parameters stay intact when forwarding
4. Configure SSL — a valid SSL certificate on your domain
5. Update your Google tag to point to the new first-party endpoint

## 5. Verifying your setup

### 5.1 Browser DevTools method

Open your website → right-click → **Inspect** (or F12) → **Network** tab → reload (F5/Ctrl+R) → filter on your URL path (e.g. `/v2ur`) → confirm the requests exist and include your website's domain.

### 5.2 What you should see

| Check              | Expected result                     |
| ------------------ | ----------------------------------- |
| HTTP status        | 200 OK                              |
| Request URL domain | Your own domain (not google.com)    |
| Request path       | Your configured path (e.g. `/v2ur`) |
| Response content   | JavaScript code from the Google tag |

## 6. Tag Gateway alongside your AdPage server-side tagging

Google Tag Gateway isn't a replacement for server-side tagging — it can be a valuable addition. Here's what each layer offers:

| Capability                          | Tag Gateway | AdPage server-side tagging |
| ----------------------------------- | ----------- | -------------------------- |
| First-party tag delivery            | ✅           | ✅                          |
| Server-set cookies                  | ❌           | ✅                          |
| Data enrichment                     | ❌           | ✅                          |
| Non-Google platforms (Meta, TikTok) | ❌           | ✅                          |
| Custom transformations              | ❌           | ✅                          |
| Privacy/data control                | Limited     | Full                       |
| Setup complexity                    | Low         | Higher                     |
| Ongoing cost                        | Low         | Higher                     |

### 6.1 When is GTG alone enough?

Tag Gateway can be sufficient if:

* You only use Google platforms (GA4, Google Ads)
* You don't need server-side data enrichment
* You have limited technical resources
* You want to get started quickly with first-party tracking

### 6.2 When do you need server-side tagging?

Server-side tagging (your AdPage container) is necessary if:

* You want to track Facebook, TikTok, or other non-Google platforms
* You want to set server-side cookies (longer lifetime, ITP-proof)
* You want to enrich data with CRM data or other server-side sources
* You want to remove or hash PII before data reaches vendors
* You want full control over what data goes where
* You need CAPI integrations (Conversions API)

### 6.3 Combining: Tag Gateway + your AdPage container

The most powerful setup is often a combination: use Tag Gateway for simple first-party delivery of Google tags, and your AdPage container for advanced use cases like CAPI integrations, data enrichment, and privacy compliance. That gives you the best of both.

## 7. FAQ

**Can I use Tag Gateway with TransIP nameservers?** Yes — you don't need to move to Cloudflare. Choose the GCP solution (recommended), Akamai (if you already use it), or a manual setup with your own web server/CDN. DNS stays with TransIP; you only configure the proxy/load balancer at the infrastructure level.

**Does Tag Gateway replace server-side tagging?** No, not at all. Tag Gateway is a lightweight solution for first-party tag delivery. Server-side tagging (your AdPage container) offers much more: data enrichment, server-set cookies, CAPI integrations, privacy control, and support for non-Google platforms. They work well together.

**Does Tag Gateway extend cookie lifetime?** No. Cookies are still set client-side, so Safari's ITP limitations still apply. For longer cookie lifetime, you need server-side tagging that can set cookies server-side — that's what your AdPage container does.

**What does Google Tag Gateway cost?** Depends on your chosen solution:

* GCP: charges for load balancer usage (relatively low)
* Akamai: included if you're already a customer
* Cloudflare: free on all plans (including the free tier)
* Manual: only your existing server/CDN costs

**Can I track Facebook/Meta with Tag Gateway?** No. Tag Gateway only supports Google tags (GA4, Google Ads, GTM). For Facebook, TikTok, Pinterest, and other platforms, you need server-side tagging with the matching CAPI integrations — already built into your AdPage container.

**Do I need to change my nameservers?** Only with Cloudflare do you typically need to move your nameservers. With GCP, Akamai, or a manual setup, your nameservers stay where they are — you only configure the proxy/load balancer.

## 8. Useful resources

* Google's official documentation
* Akamai TechDocs
* Google Ads Help
* Analytics Mania

{% hint style="info" %}
This article is meant as a guide and may change as Google rolls out new features.
{% endhint %}


---

# 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.adpage.io/optimize-your-setup/google-tag-gateway-gtg/setup-gtg-without-cloudflare.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.