Server-side tracking is the practice of collecting and sending analytics or event data from a website's backend server, rather than from a script running in the visitor's browser, often relaying it directly to an analytics provider or through a server-side tag manager.
Because the request never has to survive the visitor's browser environment, server-side tracking isn't affected by ad blockers, browser tracking-prevention features, or a visitor closing the tab before a client-side script finishes firing — all common causes of undercounted data in purely client-side setups. It typically requires more setup than dropping in a script tag, since the server needs to be configured to capture and forward the relevant events.
An ecommerce site might log a completed order directly from its checkout server the moment payment is confirmed, rather than relying on a browser script to fire an event after redirecting the customer to a confirmation page — a step where tracking is often lost.
Not always — many implementations still use a lightweight client-side script to capture page context, like the URL or referrer, and then relay that data through the server, combining both approaches.
Ad blockers primarily block known third-party tracking scripts and domains in the browser; a server-side request originating from the website's own domain and infrastructure doesn't match those blocklists the same way.
It's generally less prone to data loss from browser-side interference, but accuracy still depends on correct implementation — a misconfigured server-side setup can undercount or duplicate events just as easily.