Server-side tracking: why your data no longer adds up

Your ad platform reports twenty sales, your webshop counts thirty. Sound familiar? Chances are your measurement isn't complete. That's not down to you, but to how the web has changed in recent years. Server-side tracking is a way to recover a large part of that missing data.

Where your data leaks

Most websites still measure through scripts in the visitor's browser. Those scripts send data straight to Google, Meta and other platforms. That goes wrong in three places:

• Ad blockers block requests to known tracking domains. A visitor with an ad blocker is often invisible to your analytics.
• Browser restrictions such as Intelligent Tracking Prevention in Safari limit cookies set with JavaScript to seven days. If a visitor comes back after eight days and buys something, they look like a new visitor and you lose the link to your campaign.
• Consent: anyone who doesn't consent to cookies isn't fully measured. That's how it should be, but it does make your data less complete.

What server-side tracking is

With server-side tracking, the browser no longer sends data directly to each platform, but first to a server of your own on your own domain, for example meten.jouwbedrijf.nl. That server processes the data and forwards what's needed to Google Analytics, Google Ads and Meta, through integrations such as the Meta Conversions API.

Because the data runs through your own domain, it gets blocked less often. Cookies set by your own server don't fall under Safari's seven-day limit, provided the server is set up properly on your own domain. And you decide which data does and doesn't go to a platform.

What it gives you

• More complete data. You see more conversions in your platforms and your analytics.
• Better optimisation. Bidding algorithms in Google Ads and Meta learn from conversions. The more they see, the better they steer.
• A faster site. Fewer scripts in the browser means shorter load times.
• More control. You can filter or anonymise data before it leaves your server.

What it doesn't do

Server-side tracking is not a way to get around privacy rules. If a visitor hasn't given consent, you won't fully measure them server-side either. If you set it up properly, you link the server to the same consent choice as the rest of the site. The goal is not to measure more than is allowed, but to measure everything that is allowed.

When does it pay off?

Server-side tracking requires a server of your own and the right setup, and that takes time and a few tens of euros a month in hosting. It pays off mainly if you advertise seriously and steer on conversions, as webshops and lead generation businesses do, and if a large share of your visitors come via iPhone or Safari.

Conclusion

If your data doesn't add up, you're making decisions based on half the picture. Server-side tracking recovers a large part of the missing measurement, within the rules that ought to be there. For anyone who advertises, it's no longer an extra, but the foundation.

Sources: WebKit, Intelligent Tracking Prevention 2.1, Google, server-side tagging and Meta, Conversions API.