Server-side tracking
Server-side tracking is a way of measuring in which data about visitors and conversions goes via your own server to tools such as GA4, Google Ads and Meta, instead of directly from the browser.
- 3 min read
What is server-side tracking?
With ordinary tracking, known as client-side, all the measurement code runs in the visitor's browser. The browser itself sends data to Google Analytics, Google Ads, Meta and other tools. Each tool places its own code and its own cookies.
With server-side tracking, it works differently. The browser first sends the data to one server that you manage, usually on a subdomain of your own website, such as meten.yourcompany.nl. That server processes the data and passes it on to the tools that need it. This is often done with a server container from Google Tag Manager.
For Meta, the server-side integration is called the Conversions API. Google Ads can also receive conversions via the server, with extra data such as an encrypted email address for better matching, known as enhanced conversions.
Why it matters for your business
Browser-based measurement is becoming less and less reliable. Ad blockers stop measurement code. Browsers such as Safari limit how long cookies from measurement code are kept. As a result, you see fewer conversions than there really are, and you can't always link clicks from ads to the enquiry that follows later.
That has consequences for your ads. Google Ads and Meta steer on the conversions they get back. If enquiries are missing, the system learns from an incomplete picture and uses your budget less smartly.
Server-side tracking catches part of that. Measurement runs via your own domain, cookies are first-party and stay usable for longer, and you decide which data you pass on. That last point helps with privacy too: you can filter data before it goes to another party.
How it works
You set up a server container with a hosting provider and link it to a subdomain of your website. In your regular Tag Manager container, you send the events to that server instead of directly to GA4 or Meta. The server container holds tags that forward the data to each tool.
Important: server-side tracking is not a way to get around consent. The rules for cookies and privacy still apply. You therefore always combine it with a proper cookie banner and Consent Mode.
An example. Say an installation company advertises on Google and Meta for heat pumps. In the CRM far more enquiries come in over a month than Google Ads and Meta report together. Some of the visitors use an ad blocker or Safari on an iPhone, so their Conversion never make it back to the ad platforms. As a result, the campaigns are optimised on a picture that is too small and skewed.
After the switch to server-side tracking, GA4, Google Ads and the Meta Conversions API run via a server on the company's own subdomain. Form enquiries are passed on with an encrypted email address, so the platforms can match them to a click better. The reported conversions line up better with what's in the CRM, and the platforms have more to learn from.
Common mistakes
The first mistake is starting with server-side before the basics are right. If your conversions in the browser are already set up wrongly, you just move those errors to the server.
A second mistake is measuring twice. If you send Meta data via both the pixel and the Conversions API, you need to deduplicate events with a shared event ID. Otherwise every enquiry counts twice.
Also often seen: thinking server-side tracking makes consent unnecessary. It doesn't. Anyone who sends personal data without consent runs the same risk as with browser-based measurement.
Finally, companies forget about maintenance. A server container needs hosting, which costs a small amount per month and has to keep running.
How to approach it
First make sure your regular measurement is in order. Conversions for forms, phone clicks and WhatsApp need to be set up correctly in GA4 and Google Ads, and your cookie banner needs to work with Consent Mode.
Then decide whether server-side pays off. If you advertise seriously on Google or Meta and are clearly missing conversions, it often delivers a gain. If you have little traffic and no ads, it's usually not the first step yet.
Set up the server container on its own subdomain, send GA4, Google Ads and Meta via the server and deduplicate the events. Then compare the figures with what comes in in your CRM.
We set up server-side tracking as part of conversion tracking and dashboards, with the aim that your ads steer on real enquiries.
Frequently asked questions
Don't see your question here? Call, WhatsApp or email us. You'll get an answer within one working day.
Is server-side tracking allowed without cookie consent?
No, the privacy rules still apply. Server-side tracking changes how data is sent, not whether you need consent. So always combine it with a cookie banner and Consent Mode.
What does server-side tracking cost?
Besides the setup, you need hosting for the server container. The cost of that depends on the amount of traffic on your site. For most trade businesses, it's a modest amount per month.
What is the Meta Conversions API?
The Conversions API is how you send events such as enquiries to Meta via a server, instead of only via the pixel in the browser. As a result, more conversions come back to Meta. If you combine your pixel and API, you need to deduplicate the events.
What is Google Ads and how does it work?
Google Ads explained: how the auction system works, which campaign types there are and how you decide what a click is allowed to…
Local SEO: get more from your local visibility
Local SEO makes sure customers near you find you on Google and Google Maps.
What does a marketing agency do?
What exactly does a marketing agency do, and when do you need one?
Ready for more enquiries?
Choose where your growth should come from. A specialist picks it up within one working day.
Marketingkennersonline · reply within one working day