In this guide
- Google tag gateway for advertisers (formerly first-party mode) sends Google tag traffic through your own domain, using a CDN, load balancer or web server you already have.
- The tag still runs in the browser. It changes the address the tag loads from and reports to, not where the logic runs.
- It only covers Google's tag. Meta, TikTok and your own enrichment need a server container.
Google tag gateway is Google's own answer to a simple problem: ad blockers and browsers recognise Google's domains and cut the traffic. If the tag is loaded from your own domain and sends its data to a path on your own domain, there is less to recognise. Google calls the feature Google tag gateway for advertisers, and it was previously known as first-party mode. This page explains what it does, what it does not do, and how it fits next to a server container. Sources are listed at the end.
What it does, in one picture
Without the gateway, the page loads googletagmanager.com/gtag/js and the tag sends measurement requests to Google domains. With the gateway turned on, the page loads the same tag from a path on your site, for example yourstore.com/metrics/, and your CDN or load balancer forwards the requests to Google. The visitor's browser only talks to your domain.
Runs on your domain, anywhere
Your tracking runs on your own domain, so a visit from any country is handled the same way.
How it is set up
Google's setup guide lists several routes. The common ones:
| Route | What you do | Who it fits |
|---|---|---|
| Cloudflare | Turn the gateway on from the Tag Manager or Google tag admin screen. Google configures the forwarding rule for you. | Sites already behind Cloudflare |
| Google Cloud load balancer | Add a rule on an external application load balancer that forwards the gateway path to Google. | Sites already on Google Cloud |
| Akamai or Fastly | Follow the CDN's own gateway instructions, which forward the same path. | Sites already on those CDNs |
| Manual | Add the forwarding rule to your web server or another CDN yourself. | Teams that run their own proxy |
Google announced Cloudflare as the first partner and general availability in May 2025, and others followed. Partner lists change, so check Google's setup guide for the current options.
What it recovers
Some blockers and privacy tools match on Google's hostnames. Moving the tag to your own domain avoids those matches and lets more Google tag requests through. Google and third-party write-ups report that measured conversions go up for sites that turn it on; the figures quoted are vendor-reported and vary a lot between sites, so measure your own before and after.
Check your tracking in one pass
This is an example. Run the check on your own site to see where yours stands.
What it does not do
- It does not run your logic on a server. The tag still runs in the browser, so page speed does not improve the way it does when scripts move off the page.
- It only covers Google tags. Meta, TikTok, Pinterest and your CRM are untouched.
- It does not set longer-lived cookies from your server. The cookie lifetime limits that browsers such as Safari apply to script-set cookies are not changed by forwarding alone. See Safari ITP.
- It does not add or clean data. You cannot hash fields, remove personal data or add stored data to the event.
- It does not replace consent. Consent Mode and your banner still decide what is allowed. See Consent Mode v2.
Gateway or server container?
Pick the gateway when
You only use Google products, you want the fastest change, you already have a CDN in front of your site and nobody on the team is ready to run a server container.
02Pick a server container when
You send events to Meta, TikTok or others, you need first-party cookies with a long life, you want to control what each vendor receives, or you need the Data Store, the Enricher or offline conversions.
Use both when
You want the Google tag to load from your domain and your server container to do the rest. They do not conflict. The server container address and the gateway path are different things.
How Open Tracked relates
Open Tracked hosts a server container, and its Custom Loader power-up already serves the Google Tag Manager script from your own domain, which covers the same ground as the loader part of the gateway for the container script. The server side then adds what the gateway does not: Cookie Keeper for long-lived cookies, the Data Store and Enricher, Bot Detection, and the Meta and TikTok APIs. Both Custom Loader and Cookie Keeper are on the Free plan.
Testing it
- Open your site in a private window with developer tools open, on the Network tab.
- Filter for
gtagorcollect. - Check the hostnames: they should be your own domain, not
googletagmanager.comorgoogle-analytics.com. - In GA4 DebugView, confirm the same events still arrive.
- Compare event counts for a week against the week before.
Sources: Google tag gateway setup guide, and write-ups such as PPC Land.
Gateway, Custom Loader and server container side by side
| What changes | Google tag gateway | Open Tracked Custom Loader | Server container |
|---|---|---|---|
| Where the tag script loads from | Your domain, through a CDN rule | Your tagging domain | Not applicable by itself |
| Covers measurement requests | Yes, forwarded through your CDN | The container requests go to your tagging server | Yes, collected by your server |
| Non-Google vendors | No | No | Yes |
| Long-lived server cookies | No | No | Yes |
| Where it runs | Your CDN or load balancer | Open Tracked hosting | Open Tracked hosting |
Questions to settle before turning it on
Watch events arrive, live
A sample feed. In Open Tracked you see the same stream for your own store.
Frequently asked questions
Is Google tag gateway the same as first-party mode?
It is the new name for first-party mode. Google renamed it to Google tag gateway for advertisers.
Does Google tag gateway cost money?
Google does not charge for the feature. Your CDN or cloud provider may charge for the traffic it forwards, so check their pricing.
Can I use it together with server-side tagging?
Yes. They solve different parts of the problem and can run side by side.
Does it help with Safari?
Only partly. It changes the address of the tag. It does not by itself give you long-lived cookies set from your server.
Does it help Meta tracking?
No. It only handles Google tag traffic. Meta needs the pixel plus the Conversions API from a server.
Do I need spreadsheets to read my results?
No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.
Is Open Tracked different from Open Track or Open Space Track?
No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.
Fix your tracking at the source
Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.
The Open Tracked team
We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?
Comments
Loading comments...
Guides · 5 min read
