What is server-side tracking?
How does server-side tracking work?
In the usual set-up, each tag runs in the visitor's browser and sends data straight to its platform. With server-side tracking, the browser sends data to your server first. The server then forwards it to the tools you choose.
Google's overview of server-side tagging describes the idea and lists benefits: page performance, more detailed privacy controls and data quality. It also lists set-up options: Cloud Run, App Engine or a manual set-up1. "Server-side tagging" is Google's name for its version. We use "server-side tracking" as the general term.
Meta's Conversions API is a related, separate thing. Meta describes it as a connection that sends data from an advertiser's server, website platform, app or CRM to Meta2. It is one example of a server-side connection, not a synonym for the whole idea.
Why do ecommerce brands use it?
Browser-only tags depend on the browser. Where a browser limits scripts or cookies, some events can go missing. Moving collection to a server can recover some of them. Safari's Intelligent Tracking Prevention is one of the rules behind those limits.
A server also gives you one place to decide what leaves your site and where it goes. That control is as useful as any recovered data.
What does it not do?
- It does not remove consent rules. Google's guide to consent mode with server-side Tag Manager says server containers support both basic and advanced modes, with consent set in the web container3. Choices still start at the banner. What applies to you is for your counsel to decide.
- It does not fix a bad measurement plan. A tidy pipe carries wrong numbers as easily as right ones.
- It is not free of upkeep. Someone runs and maintains the server.
For Consent Mode, which passes banner choices to Google tags, read the separate entry.
Easily confused with
Server-side tracking vs Server-side tagging
Google's product name for its server container approach. Close, not identical.
Server-side tracking vs Tracking pixel
Browser code that sends events to a platform. Server-side tracking can sit alongside it. See event deduplication for how double counting is avoided.
Server-side tracking vs First-party data
A broader idea: data you collect from your own customers. Server-side tracking is a method, not the data itself.
For the full picture, read the server-side tracking technology page. Whether it is worth the effort for a brand your size is covered in is server-side tracking worth it. It is one check inside an ecommerce tracking audit.
FAQ
Is server-side tracking the same as the Conversions API?
No. The Conversions API is Meta's server-side route. Server-side tracking is the wider approach, and it can feed many tools.
Does it get around consent?
No. Consent still decides what you may collect and send. Your counsel decides what applies.
Do I need it?
Not always. It depends on how much data you are losing and what it costs to run. The worth-it question is covered in the guide linked above.
Sources
Let’s find what’s actually working.
Next step. Want it set up and checked against your real orders? See our analytics and tracking service.