Server-side tracking fixes some things, not everything

Server-side tracking is one of the most recommended changes in analytics right now, and one of the most oversold. It's worth doing in many cases. It's also worth being clear about what it does.

What it is

In traditional tagging, the visitor's browser loads tags from each platform and sends data to each one directly. In server-side tagging, the browser sends events to a server you control, often on your own subdomain. That server decides what to forward, to which platform, in what form.

What it genuinely improves

• Control. You decide exactly which data each platform receives, and can remove or hash personal data before it leaves your systems.
• Data quality. Fewer third-party scripts in the browser means fewer conflicts, and you can enrich and validate events on the server.
• Site performance. Moving tag work off the page can make pages lighter and faster.
• Durability. Data collected in a first-party context tends to be more consistent than data sent from many third-party scripts.

What it doesn't do

• It doesn't bypass consent. If someone declines tracking, server-side tagging must respect that, exactly as client-side tags must. Any set-up sold as a way around consent is a legal and reputational risk.
• It doesn't fix poor event design. If events are badly defined, sending them through a server sends bad data more efficiently.
• It doesn't make attribution causal. Better tracking data gives better attribution data, but attribution still measures credit, not what the marketing caused.
• It isn't free. There's hosting to pay for, configuration to maintain and expertise to keep in-house.

When it's worth it

It usually makes sense when you have significant paid media, several platforms receiving conversion data, real concerns about data control, or page performance problems from tags. For a small site with a couple of tags, the benefit may not justify the upkeep.

Do it in the right order

1. Agree an event specification first: what you track, and why.
2. Get consent working properly.
3. Then move collection server-side, testing that numbers reconcile before switching off the old tags.

Server-side tracking gives you better plumbing. It doesn't change what the water is.