Your ad platform asked you to set something up, and didn’t say why
You opened Events Manager, or Google Ads, and there it was: a prompt about a Conversions API or server-side tagging, sitting where you’d normally just confirm a pixel is firing. The documentation behind it is written for whoever built the site, not for whoever’s running the account, and it assumes you already know what problem this solves.
If that left you unsure what you were being asked to do, or whether it’s worth the effort, you’re not alone. The confusion is reasonable and it’s widespread. Search for a plain answer and you’ll find a forum thread, on the first page, full of people asking each other the same question. That tells you it’s still going unanswered in simple terms.
This matters because ignoring the prompt means quietly losing sight of which of your ads are working. Here’s what changed, what server-side tracking is, what building it takes, and what it costs you to leave it as it is.
What changed, and why the platforms started asking
Two things have made browser-based tracking less reliable.
Browser privacy restrictions are one. Browsers now limit what a website can see and remember about a visitor across sessions and across other sites. That’s the information a tracking pixel relied on to report a conversion back to the platform. The pixel still fires, but it can’t always tell the platform who fired it, or that two visits belonged to the same person.
Ad blockers are the other, and they’re blunter. A meaningful share of visitors run software that stops a tracking pixel’s request from leaving the browser, so the conversion never gets reported at all, whatever their privacy settings say.
Cookies often get the blame, so it’s worth being precise. Chrome never dropped third-party cookies, and Google wound down the Privacy Sandbox, its planned replacement, in October 2025. But Safari and Firefox have restricted third-party cookies for years, which is part of why pixels already miss visitors. The browser has become an unreliable place to report a conversion from, whether or not it still accepts a cookie.
Your ad platform is asking for this extra work because the old method stopped reporting reliably, and its own bidding depends on seeing what happened.
What server-side tracking is
Here’s the short version. It’s simpler than the documentation makes it look.
Client-side tracking means the browser reports a conversion straight to the ad platform, the moment it happens, using the visitor’s own connection. It’s the setup almost every site already has, and it’s the setup that privacy restrictions and ad blockers interrupt.
Server-side tracking means the browser tells your own server instead, and your server tells the platform. The report still happens, but the final step comes from your server and not from the visitor’s browser. That route is much harder for a browser extension to block or a privacy restriction to degrade, especially when it runs on your own domain.
The confusion is usually about names more than the mechanism. A Conversions API is Meta’s way of receiving server-side data. Google’s approach goes by other names, such as server-side tagging and enhanced conversions. They’re related ideas under different labels, and knowing that makes the documentation much easier to read.
What building it involves
There are three components, and each is worth knowing before you start.
A server container is somewhere of your own for the browser to report to, instead of reporting straight to the platform. It replaces the unreliable route, and it’s infrastructure you own and maintain, so it needs looking after.
Deduplication makes sure a single purchase, reported by both the browser and the server, doesn’t get counted twice. Without it your numbers look better than reality, which is its own kind of broken.
Match quality is how well the data you send lets the platform recognise the same person it would once have recognised from a cookie. Better match quality lets the platform credit the right campaign for the right conversion, which is what improves how it bids.
It’s a project with a real setup cost and ongoing ownership. Someone has to watch that events still fire correctly as the platforms change their own APIs, as with any other infrastructure you’d stand behind on your own site. We’d rather you know that now than find out halfway through a build.
What it costs you to leave it as it is
The cost is under-reporting, and it compounds. Your bids are optimised against whatever the platform can see. A conversion it never hears about goes unrecorded, and it can also teach the platform that the campaign behind it is working worse than it is. Budget can then drift away from what’s converting and toward whatever the platform can still measure cleanly, which is rarely the same thing.
How much your own account is missing depends on your visitors and your setup, which is why it’s worth looking before you build anything.
Where we’d start, together
A tracking health check looks across your ad accounts and your site’s own setup to see what’s getting through and where the gaps are. It tells you plainly whether server-side is something you need yet or something that can wait.
We’re willing to say “you may not need this yet”, and that’s what makes it worth listening to us when we say someone does.
Contact us to get a tracking health check today.
