Imagine paying a top marksman and then blindfolding him right before he takes the shot. That’s roughly what happens to your Google and Meta campaigns if you rely only on a classic browser Pixel to measure results. In this article, we’ll explain why browser-based tracking loses data, what server-side tracking is, and when it pays off for you.
If you’ve read our article The end of third-party cookies in practice, this is its more technical follow-up.
Why the classic Pixel loses data
For years, tracking was simple. You added a snippet of code to your website, such as the Meta Pixel or the Google tag, and it ran in the customer’s browser. When the customer made a purchase, the browser sent the ad platform a message: this person just bought something for a hundred euros. This approach is called client-side tracking.
Today, this approach runs into several obstacles:
- ad and tracking blockers stop the data from being sent right in the browser,
- browsers and operating systems, such as Apple’s Safari and iOS, restrict tracking and shorten cookie lifespans,
- declined consent, when someone doesn’t allow tracking in the cookie banner,
- interrupted page loads, when someone closes the thank-you page before the script has a chance to run.
The result? The ad platform doesn’t see some of the purchases that actually happened. The campaign looks worse than it really is, and the algorithm learns from incomplete data. You might then switch off a campaign that was actually making money.
What server-side tracking is
With server-side tracking, conversion data travels a different route. Purchase data doesn’t go to Google or Meta directly from the browser, but first to a server you control. That server processes the data and sends it to the ad platforms server to server, for example through Meta’s Conversions API (CAPI for short) or through a server-side Google Tag Manager container.
Put simply: the purchase message doesn’t go through the browser, where a blocker can stop it, but directly between two servers. Browser blockers have a much harder time stopping it, and you also get control over exactly what gets sent.
An important note: server-side tracking doesn’t bypass visitor consent. If someone declined tracking, you have to respect that on the server too. We explain how to evaluate campaigns when some people decline cookies in our article on Consent Mode v2.
You’ll find the official description of server-side tagging in Google’s documentation.
Why accurate data matters
You might be thinking: “I can see the orders in my online store, so why does Facebook need to see them too?” The answer has to do with how campaigns work today.
Modern campaigns, such as Performance Max in Google Ads or Advantage+ in Meta Ads, are driven by machine learning. Its fuel is conversion data. When the system doesn’t know who bought, it can’t look for similar people. It starts showing ads to the wrong audience, and your cost per acquired customer, known as CPA, goes up.
More complete data means the algorithm better understands who actually buys from you. That can show up as a more stable ROAS, meaning return on ad spend. Our ROAS calculator shows you how to calculate it for your campaigns.
How to find out how many conversions you’re missing
Before you invest in anything, check how big your problem actually is. A simple comparison is all you need:
- Pick a period, such as the last month.
- Write down the number of orders and revenue straight from your online store or your accounting.
- Next to it, write down the number of purchases Google Ads and Meta see for the same period.
- Compare the numbers. Ad platforms never match exactly, because they attribute purchases to different campaigns and use different time windows.
- If the gap is large and persistent, it’s a sign that your tracking is losing data.
In Meta, the event match quality score in Events Manager also helps, showing how well the system can match conversions to people.
When server-side tracking pays off
- You invest in Google or Meta ads regularly and make decisions based on data from the ad platforms.
- The number of conversions in your ad platforms differs significantly from the orders in your online store.
- You use automated campaigns and bid strategies that learn from conversions.
- You want control over what customer data goes out to third parties.
For a small website with a minimal ad budget, it usually makes more sense to start with the basics: properly set up conversion tracking and a working cookie banner. You’ll find an introduction to tracking in Google Tag Manager basics.
How to implement server-side tracking step by step
- Check your current tracking. Compare the orders in your online store with the conversions in Google Ads and Meta for the same period.
- Verify cookie consent. Your cookie banner and consent mode must work correctly, or you’ll be tracking in breach of the rules.
- Choose a solution. A server-side Google Tag Manager container on your own cloud server or with a server-side tracking provider, or a direct connection between your online store and the Conversions API, if your platform offers one.
- Set up hybrid tracking. Keep the browser Pixel and add server-side sending for your key conversions.
- Turn on deduplication. The same purchase from the browser and the server must have the same event ID, so it isn’t counted twice.
- Test and monitor. In Meta Events Manager and in Google Ads, check whether events are coming in and how their quality has improved.
Frequently asked questions
Should I remove the old Meta Pixel or Google tag from my website?
No. The recommended practice is hybrid tracking: the browser code stays, and server-side tracking adds your key conversions, such as a purchase or a submitted form. Ad platforms can merge the same event from both sources into one if it has the same ID.
Is server-side tracking GDPR-compliant?
It can be, if you set it up correctly. The advantage is that data passes through your server first, and you decide what gets sent. For example, you can remove IP addresses or hash email addresses. But you have to respect visitor consent just as you would with classic tracking.
How much does server-side tracking cost to implement?
The costs consist of a one-time technical setup and a monthly server fee, which depends on your traffic and the solution you choose. For businesses that invest in ads regularly, compare this amount with how much budget they currently spend on campaigns optimized on incomplete data.
Can I set it up myself?
If you have experience with Google Tag Manager, the basics, yes. For an online store with several ad platforms, deduplication, and cookie consent, it’s safer to bring in an expert. Faulty tracking can hurt your campaigns more than no tracking at all.
If you feel your ad platforms are showing fewer orders than you actually have, we’ll be glad to take a look at your tracking. When we manage Google Ads, we always start with accurate conversion tracking, so your campaigns learn from real data.
