Server-side tracking: what it is, and when you actually need it.

It is worth doing. It is also the fix people reach for too early. On most of the sites we look at, the browser tracking is broken first, and moving broken tracking to a server just moves the problem somewhere harder to see.

How it works

With ordinary, client-side tracking, every tag on the page talks straight to its platform. The Meta pixel calls Meta. The Google tag calls Google. Each one sets its own cookies and sends whatever it collects.

With server-side tracking, the page sends one stream of events to a tagging server, usually a Google Tag Manager server container on a subdomain such as data.yoursite.co.uk. That server then forwards each event to the platforms that need it, in the format each one expects.

	Client-side	Server-side
Who sends the data	The visitor’s browser, tag by tag	Your tagging server
Ad blockers and browser limits	Block or shorten a lot of it	Affect less of it, because the request goes to your own domain
Control over what is shared	Each tag takes what it can	You choose every field before it leaves
Page speed	Every tag adds script	Fewer scripts in the browser
Cost	Free	Hosting for the server, usually a modest monthly fee

Meta Conversions API and Google enhanced conversions

These are the 2 jobs most businesses actually want server-side tracking for.

Meta Conversions API (CAPI) sends conversions from your server straight to Meta. Meta recommends running it alongside the pixel rather than instead of it, with a shared event ID on each event so the same purchase isn’t counted twice. Set up properly, it gives Meta’s algorithm more of the conversions it is optimising for.

Google enhanced conversions sends hashed first-party data, such as the email address a customer typed into your form, with the conversion, so Google can match it to a signed-in user. It can run from the browser or from a server container.

Neither one fixes a wrong pixel, a missing event or a form that fires its conversion twice.

A worked example: fix the pixel first

Driftways Glamping is a campsite in South Norfolk. Its ad platforms were reporting results the owners couldn’t match to the bookings in front of them.

The audit found 2 problems before any talk of servers. The site was firing a Meta pixel that belonged to a different account, so Meta was learning from the wrong data. And there were duplicate tags hard-coded into the site, so some events could be counted twice.

We moved the tracking onto the correct pixel, took the duplicates out, and built a ROAS reporting pipeline the owners can read without opening an ad platform. Conversions API on the right pixel is the next step, and it is a much smaller job now that the browser side reports the truth.

If CAPI had gone in first, it would have sent cleaner copies of the wrong data to the wrong account.

Setting it up, in order

1. Audit what fires today. Every tag, on every key page, and where it sends data. Check the pixel and property IDs belong to you.
2. Fix the client side. Remove duplicates, correct the IDs, and make sure each conversion fires once, at the right moment.
3. Get consent right. Under UK GDPR and PECR you still need consent for marketing tracking, wherever it runs. Your consent banner has to control the server stream too.
4. Stand up the tagging server on a subdomain of your site, and route your Google tag through it.
5. Add the platform connections: GA4, Google Ads with enhanced conversions, Meta Conversions API with event deduplication.
6. Reconcile. Compare platform conversions with the bookings, sales or enquiries in your own system for a few weeks. The numbers will never match exactly. They should be close, and they should move together.

Do you need it?

You probably do if you spend meaningfully on Meta or Google, your platform numbers and your own sales numbers disagree by a wide margin, and you have already checked the browser tracking. You probably don’t yet if the spend is small or the client-side tracking hasn’t been audited. Fix that first. It is cheaper, and it is usually where the gap is.

If the numbers in your ad platform don’t match the numbers in your business, that is where our performance marketing work starts. The same problem from the Google side is in GA4 and Google Ads conversions don’t match.

Common questions