Server-Side Tagging
Server-side tagging routes tracking data through a server you control before it reaches Google or Meta, rather than sending it directly from the visitor's browser.
Why it matters
Browser-based tracking is increasingly blocked - by ad blockers, by Safari's tracking prevention, by consent tooling. Server-side collection recovers a meaningful share of conversions that would otherwise never be recorded, which makes the platform's optimisation better rather than just the reporting prettier.
What people get wrong
Assuming a site with no visible tags is untracked. A server-side container is invisible to anyone inspecting the page source, so a scan showing "no tracking" can be looking at a perfectly measured business.
How to tell whether yours is actually working
Open Events Manager or your analytics platform, pick your most important conversion event, and look at how many events arrived from the browser versus from the server.
If both are firing and they are being matched correctly, the two streams describe the same events and get deduplicated into one. If they are not matched, both get counted, and every sale becomes two. The tell is a funnel that runs backwards: more purchases than checkouts, more bookings than enquiries. Nobody completes a step they never started.
The mechanism is a shared event ID sent by both the browser and the server for the same event. When that ID is missing or different, nothing errors. Events arrive, the dashboard fills in, and the numbers simply read better than the business does.
What server-side tagging does not fix
It does not create data that was never collected. If a form never fired an event in the first place, moving the tag to a server changes nothing about that.
It is not a way around consent. A visitor who has not consented has not consented regardless of where the tag runs, and treating server-side as a consent workaround is both a compliance problem and, increasingly, a data quality one.
And it does not make a bad measurement plan good. Sending the wrong event more reliably is still the wrong event.