Since Google launched Google tag gateway for advertisers, I keep getting the same question from clients: "Is this the free version of server-side tracking? Can I cancel my Stape plan?" The short version is no. The two tools share one idea, sending tracking traffic through your own domain, but they solve different problems. This guide explains what tag gateway actually does, where server-side Google Tag Manager (sGTM) goes further, and how I decide which one a business needs.
What is Google tag gateway for advertisers?
Google tag gateway for advertisers is a Google feature that loads your Google tag and sends its measurement requests through your own domain, using a CDN (content delivery network) or load balancer you already run, instead of loading everything straight from Google's domains. The browser asks yourstore.com for the tag script, and your CDN quietly forwards that request to Google and returns the response.
In a standard setup, the visitor's browser downloads gtag.js or gtm.js from a Google domain and sends hits for GA4, Google Ads and Floodlight back to Google domains. Some ad blockers, privacy browsers and network filters block those well-known hostnames. With tag gateway, the same scripts and hits travel on a path under your own website, so they look first-party to the browser.
How do you set it up?
You set it up in the Google tag settings or in Google Tag Manager under Admin > Google tag gateway, then connect it to the service that sits in front of your website. Google offers guided integrations for several providers:
- Cloudflare, which was the first integration and can be switched on with a few clicks for domains proxied through Cloudflare.
- Akamai and Fastly, for sites already running on those CDNs.
- Google Cloud, through an external Application Load Balancer.
- Manual setup for other CDNs or servers that can forward a path to Google.
For a site already proxied through Cloudflare, the setup is quick because Cloudflare does the routing at its edge. If your domain is not behind a supported CDN or load balancer, tag gateway is harder to justify, since you would be adding infrastructure just to proxy one vendor's tags. Check Google's and your CDN provider's current documentation for plan requirements, because these integrations are still evolving.
What is server-side GTM?
Server-side Google Tag Manager is a second GTM container, of the "Server" type, that runs on a cloud server you control and receives events before forwarding them to vendors. Your web container sends one stream of events to a tracking subdomain such as sgtm.yourstore.com. Inside the server container, a client (for example, the GA4 client) turns each request into an event, and server tags send it to GA4, Google Ads, the Meta Conversions API (CAPI), TikTok and others.
The container is usually hosted on Stape or Google Cloud Run. I cover the full architecture in what server-side tracking is and whether you need it, so here I will focus on the comparison.
What is the difference between tag gateway and server-side GTM?
The core difference is that tag gateway only changes where Google's tags are delivered from, while server-side GTM changes where your tracking data is processed. Tag gateway is a first-party delivery route for Google tags. sGTM is a server you own that can read, change, enrich and route events to any platform.
| Google tag gateway | Server-side GTM | |
|---|---|---|
| What it does | Serves Google tags and routes their hits through your domain | Receives events on your server and forwards them to vendors |
| Vendors supported | Google tags only (GA4, Google Ads, Floodlight) | Google, Meta, TikTok, Pinterest, webhooks, CRMs and more |
| Can modify data before it leaves | No | Yes: remove, add, hash or transform fields |
| Enrich with server data (margin, CRM status) | No | Yes, with lookups and APIs |
| Meta CAPI or TikTok Events API | No | Yes |
| Infrastructure | Your existing CDN or load balancer | A hosted server container |
| Running cost | Depends on your CDN; Cloudflare describes its integration as free | Monthly Stape plan or Google Cloud billing |
| Maintenance | Low | Medium |
| Setup effort | Low on a supported CDN | Medium to high |
What tag gateway does not do
Tag gateway does not process your data. The payload GA4 or Google Ads receives is the same as before; it simply arrives by a first-party route. That means:
- No Meta, TikTok or other platforms. If you need the Meta Conversions API, tag gateway does nothing for you. I explain why Meta wants a server connection alongside the Pixel in Meta Pixel vs Conversion API.
- No data control. You cannot strip IP addresses, remove URL parameters that contain personal data, or hash customer details on the way through.
- No enrichment. You cannot add profit margin, customer lifetime value or CRM lead quality to a conversion.
- No fix for broken events. A
purchaseevent that fires twice or carries the wrong value is still broken, just delivered more reliably. - No consent bypass. Consent Mode still decides how Google tags behave. If a visitor declines, a first-party route does not change what you are allowed to collect. My Consent Mode v2 guide explains the settings that apply either way.
What tag gateway does well
Tag gateway does one thing well: it makes Google measurement requests harder to block and less dependent on third-party hostnames, with very little effort. Google positions it as a way to recover measurement signal for its own tags, and for a business that only advertises on Google, that is often the part that matters most. There is no server to monitor, no container to update, and no extra hosting bill if your CDN integration is free.
When should you use Google tag gateway?
Use Google tag gateway when your ad spend and analytics are mostly Google, your site already sits behind Cloudflare or another supported CDN, and you want a quick improvement without running a server. Typical examples I see:
- A local service business running only Google Ads, with GA4 for reporting and calls and forms as conversions.
- A small ecommerce store on Cloudflare that wants Google Ads and GA4 to lose fewer hits, but is not ready for server-side hosting.
- A business that has just fixed its basic GTM setup and wants a low-risk next step.
When do you need server-side GTM instead?
You need server-side GTM when you advertise on more than Google, when you need to control or enrich data before vendors receive it, or when you want conversions to come from a trusted source such as your store backend. Common signs:
- You run Meta Ads or TikTok Ads and need their server APIs with proper deduplication.
- You want to send purchases from your backend or order webhooks rather than relying on the thank-you page in the browser. My guide to Shopify server-side tracking shows what that looks like.
- You need to remove personal data from URLs, or hash emails and phone numbers for enhanced conversions centrally.
- You want to report profit rather than revenue to Google Ads for value-based bidding.
For Tea of Sylhet, the problem was not only blocked requests. Purchase events lacked reliable revenue values in Google Ads, so I built a hybrid setup with web and server GTM on a Stape custom tracking domain, where purchases are validated server-side and forwarded as authoritative events. Tag gateway alone could not have done that, because it does not touch the data.
Can you use Google tag gateway and server-side GTM together?
Yes. Google documents a combined setup where your CDN serves the Google tag scripts from your domain through tag gateway, while a separate server-side GTM container handles data collection, enrichment and forwarding. In that model, the CDN takes care of script delivery and the server container takes care of the data.
In practice, I only add tag gateway on top of sGTM when the site is already on a supported CDN and the extra layer is cheap to run. Many sGTM hosts already offer their own first-party script loading, so check what your setup does before stacking another route on top. Two first-party layers that both try to serve the same script can cause confusing debugging sessions.
A quick decision checklist
- Only Google tags matter to you right now → start with tag gateway.
- Your domain is not behind a supported CDN or load balancer → tag gateway is harder to justify; consider sGTM if you need first-party tracking.
- You need Meta CAPI, TikTok Events API or webhooks → sGTM.
- You need to filter, hash or enrich data → sGTM.
- You already run sGTM on a supported CDN and want first-party script delivery for Google tags → consider both, then test carefully.
- Your events are not firing correctly yet → fix that first. Neither tool repairs a broken setup.
How do you test either setup?
You test both setups the same way: confirm that requests go to your own domain, and that GA4, Google Ads and any other platforms receive the events you expect. My routine:
- Open your site with the browser's developer tools on the Network tab and check that tag scripts and hits load from your domain, not a Google hostname.
- Use Tag Assistant or GTM Preview mode to confirm the Google tag still fires with the right consent state.
- Check GA4 DebugView and Google Ads conversion diagnostics for the events you care about.
- For sGTM, also open the server container's Preview mode and confirm each server tag returns a success response.
- Compare conversions with real orders or leads over the following weeks.
If you want a quick first pass, my free tracking health check flags common setup problems before you start.
Final thoughts
Google tag gateway is a useful, low-effort way to make Google tags more resilient, but it is a delivery route, not a tracking server. If you only need Google measurement on a site already behind a supported CDN, it may be enough. If you need Meta CAPI, data control or backend-verified conversions, you still need server-side GTM, which is the core of my advanced conversion tracking service. Not sure which you need? Book a free tracking audit.
