Server-side Tracking
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?+
Why do you need server-side tracking?+
What is event_id and deduplication?+
Is it difficult to implement server-side tracking?+
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.