Server-side tagging explained without the jargon

Dear founder,

Every year server-side tagging gets talked about like it's the answer to all your data problems. Sometimes it is a genuine help. Often it's a big lift for a small gain. Let me tell you plainly what it does so you can decide honestly.

What it actually changes

Normally, tracking runs in the visitor's browser, sending data straight to Google, Meta and the rest. Server-side tagging moves that step to a server you control, which sits in the middle.

• More reliable data because ad blockers and browser limits interfere less
• More control over what leaves your site and where it goes
• Better page speed, since fewer scripts run in the browser itself
• More responsibility, because now you're running a bit of infrastructure

The honest trade-offs

It isn't free and it isn't magic. There's a running cost and a real setup effort.

1. You'll pay for hosting the server, month after month
2. Someone has to maintain it when things change
3. The benefit is bigger for high-traffic stores than small ones

If you're doing a few hundred orders a month, your time is better spent on the product page than on tag infrastructure.

I'd think about server-side tagging once your data losses are genuinely costing you decisions, or your marketing spend is large enough that a few percent of recovered signal matters. Below that, it's a solution looking for a problem. If you're not sure which camp you're in, book advisory time and we'll weigh it up against everything else on your list.