Glossary
What is server-side tracking?
Server-side tracking sends conversion events to ad and analytics platforms from a server, rather than from JavaScript running in the visitor’s browser. Because delivery is server-to-server, events are unaffected by ad blockers, browser tracking prevention or a tab closed before the pixel fired.
The data still originates with the visitor (a page view, a signup, an order), but instead of relying on a pixel to report it, the event is recorded first-party (by a lightweight script or your backend), enriched with stored click IDs and customer data, and forwarded from a server to interfaces like the Meta Conversions API, Google’s APIs and the TikTok Events API.
The gains are reliability and control. Delivery does not depend on the browser environment; failed requests can be queued and retried; and you decide exactly what each platform receives. Personal identifiers are normalized and hashed before they leave the server.
Two caveats: server-side tracking complements the pixel rather than replacing it (both send the same events, deduplicated by event_id), and it is not a way around privacy law. Consent and data-protection obligations apply to server events exactly as they do to browser ones.