Term · Marketing & analytics
Server-side tracking
Server-side tracking is an approach in which events — leads, purchases, sign-ups — are sent to analytics and advertising platforms from a server you control, rather than only by scripts running in the visitor's browser.
[ 01 ]
Explained
Why it exists
Browser-based tracking loses data: ad blockers, privacy features, cookie restrictions, slow connections and payment redirects all prevent some events from being recorded. Platforms then optimise with incomplete information.
How it works
- Direct server events: your application sends confirmed events — for example, a paid order from your database — to platforms' APIs, such as Meta's Conversions API or Google Ads offline conversion imports.
- Server-side tagging: a tagging server receives events from the website and forwards them to analytics and ad platforms, controlling which data is shared.
Events sent from both browser and server are deduplicated with a shared event ID.
Benefits
- More complete and accurate conversion data.
- Values taken from your system of record.
- Control over which data each platform receives.
- Potentially fewer third-party scripts on pages.
Obligations
Server-side tracking must still respect consent and privacy law: send only necessary data, hash personal identifiers where platforms require it, and describe the processing in your privacy policy. It is not a way to bypass users' choices.
[ 02 ]
FAQ
Frequently asked questions
Is server-side tracking required?
No, but it is increasingly valuable for businesses spending significantly on advertising.
Does it replace the browser pixel?
Usually they work together, with deduplication.