To the glossary
AnalyticsTerm

Server-side Tracking

server analytics · server-based event transmission · S2S tracking · Conversions API

Server-side Tracking - transfer of conversion events directly from the server to the advertising platform, bypassing browser blockers.

Server-side Tracking (S2S) is a data transfer scheme in which conversion events are sent not from the user’s browser (like a classic pixel), but from your server directly to the advertising platform API (Meta Conversions API, VK API, TikTok Events API). Bottom line: ad blockers and ITP/iOS restrictions are no longer a hindrance.

In my practice, switching to S2S in e-com projects gave an increase in “visible” conversions by 25–40%. The algorithm began to learn from a larger number of signals and the CPL decreased - not because the advertising became better, but because the data became more complete. This is the most underrated technical upgrade in performance 2024–2026.

How it works: the user performs an action on the site → your backend records the event → the server sends it via HTTPS to the Meta Conversions API or equivalent. To deduplicate browser and server events, event_id is used - without it you will get duplicate data. GTM Server-side (Google Tag Manager Server Container) is the most popular solution for no-code configuration.

The complexity of S2S is not technical, but organizational: the backend developer needs to understand the task and provide the necessary fields (email, phone, user agent in hashed form). Implementation takes 1–3 sprints. For small sites without a developer, this is still unrealistic; there remains pixel with improved compliance.

Frequently asked questions about Server-side Tracking

What is server-side tracking?+
This is the transfer of conversion events from your server directly to the advertising platform API, bypassing the user’s browser. This way, ad blockers and iOS and ITP restrictions stop interfering. Implemented via Meta Conversions API, VK API, TikTok Events API.
Why do you need server-side tracking?+
To return the conversions that the browser pixel loses due to blockers and iOS restrictions. In practice, the transition increases the number of visible conversions by 25–40%, the algorithm learns more fully and the CPL decreases. This is not an ad improvement, but data recovery.
What is event_id and deduplication?+
event_id is a unique event identifier that allows the platform to understand that the browser and server event are the same action. Without it, one conversion will be counted twice and the statistics will be inflated. Deduplication is required when sending in parallel.
Is it difficult to implement server-side tracking?+
The difficulty is not technical, but organizational: the backend developer needs to provide hashed email, phone and user agent. Implementation takes 1–3 sprints. A popular no-code solution is GTM Server-side. For a small site without a developer, there is still a pixel with improved compliance.

Related terms

Need to set this up on your project?

I analyze metrics, calculate unit economics and collect funnels on real budgets. 30 minutes on call - free.