Google tag gatewayIn this guide
- The gateway serves the Google tag from your domain through a CDN rule. It is quick and covers Google tags only.
- Server-side tagging runs a container on your server. It covers every vendor, sets long-lived cookies and lets you edit data.
- They are not rivals. Many sites use the gateway for the loader and a server container for the data.
Two Google-related features are often presented as the same thing: Google tag gateway for advertisers (earlier called first-party mode) and server-side tagging with a Google Tag Manager server container. They share a goal, which is to make tracking requests look first-party and survive blockers, but they work in different places and do different amounts of work. This page puts them side by side. The gateway is explained on its own in what is Google tag gateway, and the server side in what is server-side tracking.
Where each one acts
| Google tag gateway | Server-side tagging | |
|---|---|---|
| What it moves | The address the Google tag loads from and reports to | The place your tag logic runs |
| Where tags run | Still in the visitor's browser | On a server you control |
| Which vendors | Google tags | Google, Meta, TikTok, Pinterest, CRM, anything with a server tag |
| Cookies | Same cookies as before, served from your domain path | Can set and refresh cookies from your tagging subdomain |
| Control over data | None beyond what the tag sends | You can remove, add and hash fields per vendor |
| Page speed | About the same | Better, because fewer scripts load |
| Typical set-up time | Under an hour with a supported CDN | A few hours with a ready container and a host that gives you a wizard |
| Typical running cost | Whatever your CDN already charges | A hosting plan or your own cloud instances |
Orders from your store, back to the ad that earned them
Your store sends the order once. Open Tracked passes it on to each ad platform, cleaned and deduplicated.
What each one recovers
Both aim to reduce the number of requests that blockers cut because they come from known Google or vendor domains. The gateway does it for Google traffic by moving it onto your domain. A server container does it for everything the browser sends to your tagging subdomain, and then the server contacts the vendors itself, out of the blocker's reach.
The gateway does not give you longer cookie life. Safari's limits on cookies written by JavaScript apply whichever domain the script is served from. A server container can set cookies in an HTTP response, which browsers treat more kindly, and Open Tracked's Cookie Keeper can restore platform cookies from the server for visitors who come back without them. See Safari ITP and extending cookie lifetime.
Where the gateway is enough
- Your ads are on Google only: Google Ads, GA4 and Merchant Center.
- You already use Cloudflare or another CDN that supports the gateway.
- You do not hash or enrich data and do not need long-lived cookies.
- You want a result this week with no new infrastructure.
Ask Ari instead of digging through reports
Ari reads your tracking and ad data and answers in plain words.
Where you need a server container
- You advertise on Meta or TikTok. The gateway does nothing for them.
- You want the Conversions API with high match quality.
- You want to remove or add fields before data leaves, for privacy or for matching.
- You have leads and sales that happen outside the browser.
- You want longer cookies and returning-visitor recognition on Safari.
The combination
Nothing stops you from running both. A typical set-up: the gateway or a custom loader serves the Google tag from your domain, the web container sends every event to your tagging subdomain, and the server container forwards to GA4, Google Ads, Meta and the rest. With Open Tracked, the Custom Loader power-up serves the Tag Manager script from your own domain on every plan, including Free, and the hosted container takes care of the server side.
Decision in four questions
- Do you advertise anywhere besides Google? If yes, you need a server container.
- Do you need to control the data each vendor sees? If yes, you need a server container.
- Is Safari traffic a large part of your visits? If yes, you need server-set cookies.
- If all answers are no, try the gateway first and measure.
Three real-world scenarios
| Business | Situation | What fits |
|---|---|---|
| Local services firm | Google Ads and GA4 only, WordPress behind Cloudflare, one marketer | Start with the gateway. Measure for two weeks. |
| Online store | Meta, Google and TikTok ads, many iPhone visitors, a Shopify or WooCommerce shop | Server container with Cookie Keeper. The gateway adds little on top. |
| Agency with ten clients | Different platforms per client, need to prove results | Server containers on a managed host, one per client, with a shared checklist. |
Checklist before you switch anything on
3 things to remember
Scroll and the points stack up.
The gateway serves the Google tag from your domain through a CDN rule. It is quick and covers Google tags only.
Server-side tagging runs a container on your server. It covers every vendor, sets long-lived cookies and lets you edit data.
They are not rivals. Many sites use the gateway for the loader and a server container for the data.
Frequently asked questions
Is Google tag gateway the same as server-side tagging?
No. The gateway forwards Google tag traffic through your domain. Server-side tagging runs a container on a server and works for all vendors.
Can I use Google tag gateway and a server container together?
Yes. They can run side by side and do not conflict.
Which one is cheaper?
The gateway costs whatever your CDN or load balancer charges for the traffic. A server container costs a hosting plan or cloud instances. Open Tracked starts free at 15,000 requests a month.
Which one helps Safari more?
A server container, because it can set and restore cookies from your own server. The gateway mainly changes the tag's address.
Do I need consent either way?
Yes. Neither one removes the need for consent where the law requires it. See Consent Mode v2.
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 · 6 min read