Tracking
Server-side tracking setup: when it pays off and how it works
Why server-side tagging?
- More complete conversion data Fewer measurements are lost to ad blockers and browser restrictions. How many, you'll see when I compare the tracking with your own orders.
- Lower cost per result Meta reports an average 17.8% lower cost per result for advertisers using the Conversions API for web events.
- Control over your data You decide which data goes to which platform.
- All your channels from one source Google, Meta and other platforms get their data through the same setup, without separate tags per channel.
What is server-side tracking?
With server-side tracking, your website no longer sends measurements directly to Google, Meta and other platforms. It sends them to a server under your own domain first, for example metrics.yourcompany.com. That server decides which data goes on to which platform. You usually use a Google Tag Manager server container for this.
With the usual client-side method, each tag loads its own script in your visitor's browser. Each tag sends data on its own. With server-side, one data stream goes to your server. There, you decide what goes to which platform.
Server-side tracking moves measurement from your visitor's browser to a server you control.
What server-side tracking delivers
Set up properly, it delivers four things. The first matters most: Smart Bidding and Meta's algorithm learn from the conversions that come in. If some are missing, they learn from an incomplete picture.
- More complete conversion data in Google Ads and Meta, because fewer measurements get lost along the way to ad blockers and browser restrictions.
- One setup for the Meta Conversions API and Google's enhanced conversions, with deduplication so a purchase isn't counted twice.
- Control over what you share: for each platform you decide which data goes through and what you leave out or encrypt.
- Fewer third-party scripts in the browser, which can make your site faster.
Client-side and server-side tracking compared
Client-side, each tag loads its own script in your visitor's browser, and each tag sends data on its own. Server-side, one data stream goes to your own server, which passes the data on to each platform.
For Safari, that makes a difference. With ITP, Safari's tracking protection, cookies set with JavaScript in the browser get a lifespan of seven days at most. A server on your own domain can set cookies that last longer, provided Safari also sees that server as part of your site.
| Client-side | Server-side | |
|---|---|---|
| Ad blockers | Tracking scripts often blocked | Blocked less often |
| Safari ITP and cookie lifespan | JavaScript cookies 7 days at most | Longer, if on your own domain and IP range |
| Load time | Each tag loads its own script | Fewer scripts in the browser |
| Costs | No server costs | Hosting, depending on your traffic |
| Maintenance | Only tags in the browser | Server container and server to maintain too |
| Consent | Cookie banner and Consent Mode needed | Same rules, the choice carries over to the server |
Web container and server container in Google Tag Manager
A web container is the Google Tag Manager container that runs on your site, in your visitor's browser. With client-side tracking, it sends the data directly to Google, Meta and other platforms.
A server container runs on a server you control, at Google Cloud or another hosting provider. You usually work with both: the web container or the Google tag on your site sends the events to the server container, instead of to each platform separately.
In the server container, a client, a kind of translator, receives the incoming requests and turns them into events. The tags in the server container then forward those events to GA4, Google Ads or Meta's Conversions API. For each tag, you decide which data goes along.
How much more do you measure with server-side tracking?
There's no fixed percentage: it depends on your visitors, their browsers and how much measurement you're losing now. Google and Meta do publish their own averages for advertisers who made the switch:
11%
more signals for advertisers using Google tag gateway, which routes tags through their own domain (Google, May 2025)
17.8%
lower cost per result with the Meta Conversions API for web events, compared with advertisers without it (Meta, April 2026)
Note what was measured. Google's figure is about signals, meaning tags that do load and measure, not directly about extra sales. Meta's figure compares advertisers with and without the Conversions API. These are averages. That's why, with every setup, I compare the number of measured conversions before and after with your own orders or leads, so you see what it delivers for you.
Drawbacks and risks
Server-side tracking takes more than a regular setup, and it doesn't solve every measurement problem.
- Ongoing costs: the server costs hosting for as long as you measure, and those costs grow with your traffic.
- More maintenance: besides the web container, the server container has to be kept up to date too. After a webshop update or a new ad channel, I test both again.
- Double counting: Meta recommends using the pixel and the Conversions API together. If you send the same purchase through both, Meta needs the same event ID and name for each event to turn them into one purchase.
- Longer cookies only with the right connection: according to Google, on the hosting provider's default address the server can only set JavaScript cookies. If your tracking subdomain points to another domain via a CNAME record, or to a server in a different IP range than your website, Safari limits the server's cookies to seven days as well. Google names a path on your own website, such as /metrics, as the best connection.
- One server for all platforms: if the server goes down, measurement stops for all channels at once. That's why I monitor whether data keeps coming in.
- No extra measurements without consent: visitors who decline aren't measured server-side either. The gain is in measurements that would otherwise be lost for technical reasons.
- Source: Meta on using the pixel and Conversions API together
- Source: WebKit on cookies via a CNAME or another IP address
- Source: Google on a path or subdomain for your server
Server-side tracking and the cookie banner
Server-side tracking is not a way around the cookie banner. It doesn't change the rules: without your visitor's consent, you may not collect or share marketing data, not even through your own server. That's why I always set it up together with Consent Mode, so the choice someone makes in your cookie banner is also followed server-side.
If you use it to get around consent, you run a risk with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens). Set up properly, you measure what you're allowed to measure more completely. And you share less than with separate tags in the browser.
When I recommend it, and when I don't
I only start once the regular tracking is correct and there are enough conversions to make a difference. This is my check:
Worth it if
- You advertise seriously on Google and Meta and steer on conversions
- Your platforms show clearly fewer conversions than your own orders or leads
- You want to set up the Meta Conversions API and enhanced conversions properly
- You want to decide yourself which customer data goes to which platform
Fix something else first if
- Conversions are currently double counted or missing
- Your cookie banner and Consent Mode don't work correctly yet
- You only have a handful of conversions per month
- Nobody maintains the setup after go-live
How I set up server-side tracking
I work in five steps, from measurement plan to monitoring:
- 1
Measurement plan
I document which conversions and events count, what value belongs to them and which data may go to which platform.
- 2
Checking the current tracking
The basics first: cookie banner, Consent Mode, GA4 and the conversions in Google Ads and Meta. Whatever isn't right there, I fix first.
- 3
A server on your own domain
I set up a server container with a hosting provider and connect it to your own domain, preferably via a path on your website, so Safari sees the tracking as part of your site.
- 4
Connections per platform
GA4, Google Ads with enhanced conversions and the Meta Conversions API, with deduplication against the pixel. I connect every channel you advertise on. In setups built by others, I often see only some of the channels running through the server.
- 5
Testing and monitoring
I compare the new tracking with your orders or leads, check the quality of the matched data in Meta and Google and maintain the setup afterward.
What does server-side tracking cost?
There are two kinds of costs: the one-off setup and the ongoing hosting of the server. Hosting mainly depends on your traffic. A site with few visitors is cheap, a busy webshop pays more. The setup depends on the number of platforms, your webshop system and the state of your current tracking.
So I put together a custom quote after a quick look at what's in place now. Sometimes a lighter step is enough: with Google Tag Gateway you load Google tags through your own domain, for example via Cloudflare, without a full server-side setup. I look at that first too, so you don't buy technology you don't need.
Frequently asked questions
What's the difference between server-side tagging and server-side tracking?
In practice, people mean the same thing: measurements go to the platforms through your own server instead of directly from the browser. Server-side tagging is the Google Tag Manager term, where you work with a server container. Server-side tracking is the broader umbrella term, which also covers direct connections such as the Meta Conversions API.
Do I need server-side tracking for the Meta Conversions API?
Not necessarily. You can also connect the Conversions API through an integration in your webshop system or a partner integration. A server container does give you more control over which data you share and makes it easier to serve Google and Meta from one setup. Which route fits depends on your platform and your budget.
Does server-side tracking work with Shopify and WooCommerce?
Yes. With both systems, a server container can receive your order data and forward it to GA4, Google Ads and Meta. Which route works best depends on your theme, your apps or plugins and how your cookie banner is set up. I check that beforehand, so no duplicate measurements occur.
Is server-side tracking GDPR compliant?
Only if you set it up that way. Server-side tracking itself is neutral: you still need to ask for consent for marketing cookies, follow your visitor's choice and document which data you share. Set up properly, you actually share less than with separate tags in the browser, because you decide what goes through.
First see where your return is leaking?
Outsourcing to me means your advertising is handled from A to Z. The free Quick Scan is the first step: I go through your account with read-only access and show you your 3 biggest opportunities, in a report that is yours to keep, even if we do not work together afterwards.