Server-side tracking: what it does and when it is worth it
Where it sits among the other tools is on the ecommerce marketing technology stack page.
What does server-side tracking do?
In a normal setup, every tag loads in the browser. Each one sends data straight to its own vendor.
In a server-side setup, the browser sends events to a server first. That server decides what goes on to Google Analytics, to ad platforms and to anything else you connect.
Google's version is server-side tagging, run in a Google Tag Manager server container (often shortened to sGTM). You host the container yourself. Google lists Cloud Run, App Engine and manual setup as hosting options, and recommends your own domain for the tagging server1. Someone has to own the maintenance. That someone is usually not Google.
Two things it is not:
- It is not the same as the Conversions API (CAPI). CAPI is Meta's interface for receiving server events. Server-side tracking is the wider method you might use to send them.
- It is not a way around consent. Consent Mode works in the server container, but consent is set up in the web container2. A visitor who says no still says no. See Consent Mode.
Why do e-commerce brands use it?
Example (illustrative): the ad panels, analytics and the shop show three different order counts, and someone asks where the conversions went.
The reasons Google gives are practical. Fewer scripts in the browser can make pages faster. One server in the middle gives you control over what each vendor receives. Cleaner collection can improve data quality1.
Safari is the other reason. WebKit's Intelligent Tracking Prevention (ITP) limits cross-site tracking. Its 2020 post on CNAME cloaking says cookies set through CNAME-cloaked responses are capped at seven days3. So on Safari the result depends on how the setup is built. A server container alone does not settle it.
How do we implement it?
Audit the basics
Check the consent management platform, the data layer and duplicate events first. If one is broken, fix it before building anything.
Set up in your accounts
Hosting, tag manager access and the domain sit in your name, so you can change supplier without starting again.
Build and deduplicate
Server container, consent set-up and tags, with the same event name and ID on both paths. One purchase should count once.
Name an owner, then compare
Someone owns the upkeep. Then platform order counts are checked against your shop's, because that is the number the decision rests on.
When should you not use it?
Skip it, for now, when:
In the first three cases, audit before you build. Our tracking audit is free, and it should say whether server-side is the next step or the tenth.
What does it cost in effort?
We give no figures. Google publishes none1, and the numbers that exist come from vendors.
The cost has four parts:
- Hosting. Pick a Google-supported option or a vendor's hosting, then pay for it.
- Build. Server container, domain, clients, tags, consent set-up and testing.
- Upkeep. Tag changes, platform changes, someone watching it break.
- Ownership. The hosting account and the tag manager access should belong to you, not to whoever built it.
Ask any supplier for all four, in writing, before you start. Hosting vendors publish their own cost comparisons4, so read those as sales material.
Pitfalls
Double counting
If the browser and the server both send the same purchase, the platform may count two. You need event deduplication: the same event name and ID on both paths.
Missing pieces
Consent Mode in the server container needs a GA4 client there, plus the Conversion Linker tag for Google Ads and Floodlight2. Leave one out and consent signals do not do what you expect.
Treating it as a fix for everything
It moves data collection. It does not repair a broken data layer or a missing consent banner.
No owner
A server container with nobody looking after it quietly stops being right.
Promises about blocked data
Be wary of anyone who promises to get round ad blockers or consent. Google's documentation does not say that1.
Our take: Selective
We rate server-side tracking Selective. This is our view, not a market fact.
Why not Core? Google describes the benefits and the hosting options, but gives no cost figures1. The cost figures you find online come from vendors that sell hosting, and they have an interest in the answer4. Vendor guides list criteria for when it makes sense, without numbers5. It needs upkeep. In our view it helps some brands a lot and others very little.
For ZFD: We treat it as a decision about your account, not a tick-box. Some brands need it. Many should fix something cheaper first.
FAQ
Is server-side tracking the same as server-side tagging?
Close. "Server-side tracking" is the general method. "Server-side tagging" and sGTM refer to Google's Tag Manager server container specifically.
Is server-side tracking the same as the Conversions API?
No. The Conversions API is Meta's interface for receiving events from a server. Server-side tracking is the wider approach you might use to send them.
Does server-side tracking get round consent or ad blockers?
No, and we do not promise it. Google's documentation describes consent handling in the server container2, not a way around it.
Where does the server container run?
Google lists Cloud Run, App Engine and manual hosting as options1. Vendors also offer hosting.
Do I need server-side tracking if I run Meta and Google ads?
Not automatically. It depends on how much your numbers disagree, whether the basics are clean, and who can run it.
Who should own the setup?
You should. Hosting, tag manager access and the domain should sit in your accounts, so you can change supplier without starting again.
Sources
- Server-side tagging overview (Google for Developers)Primary source
- Implement consent mode with server-side Tag Manager (Google for Developers)Primary source
- CNAME Cloaking and Bounce Tracking Defense (WebKit blog)Primary source
- How much does server GTM cost and why Stape is cheaper than Google Cloud RunVendor
- Google Tag Manager Server-Side Tagging: Do I Really Need It? (TAGLAB)Vendor
Let’s find what’s actually working.
Next step. Want a view on whether this is worth doing on your account? Talk to us about your tracking setup. Or read about our Analytics & tracking service.