Short answer: Normally, your visitor’s browser sends information straight to Google, Facebook, and other tools. With server-side tracking, the browser sends it to your own server first, and your server passes it on. With a server on your own subdomain, ad blockers and privacy settings can stop less of it, and you control what each company receives. It’s worth it if you spend a fair amount on ads and are losing a lot of tracking. If your spend is small, it may not be worth the cost yet.
A simple way to picture server-side tracking
Without it: your website is a shop where every delivery company walks in and takes notes themselves. Some get stopped at the door.
With it: one person from your shop collects the notes and hands them to each delivery company. Fewer get stopped, and you decide what each one gets.
One common way to build it is Google’s server-side Tag Manager.
What it helps with
- Fewer lost sales in your reports. With a server on your own subdomain, some blockers and browsers block less of it. It can’t recover data a visitor said no to.
- More control. You choose what information goes to Google, Meta, and others.
- Sending sales to Meta from your server (the Conversions API) from one place. See Meta Pixel vs Conversions API.
- Possibly a faster website, if fewer outside scripts load in the browser.
What it doesn’t fix
- Cookie rules. You still need visitors’ permission where the law says so.
- Bad setup. If your tracking is already wrong, it will pass on the wrong information too.
- Tools disagreeing. Google Ads and Google Analytics can still count differently.
Do you need server-side tracking?
Probably yes if:
– You spend a meaningful amount on ads and lost sales hurt your results.
– Many of your visitors use iPhones or privacy-focused browsers.
– You need to send sales to Meta from your server and your website platform can’t do it well.
Probably not yet if:
– Your ad spend and traffic are small, so the server cost outweighs the benefit.
– Your website platform already does server tracking well.
– Your basic tracking is still broken. Fix that first.
FAQ
Is it free?
The Google tool is free. Google says the default test server is free in most cases, and a live setup costs about $30–$50 per server a month, more with heavy traffic. Google recommends at least 3 servers for live traffic.
Does it let me skip asking for cookie permission?
No. You still need permission where the law requires it.
Do I still need normal Google Tag Manager?
For a website, usually yes. The website container sends data to the server container.
Is it the same as Meta’s Conversions API?
No. The Conversions API is one place your data can go. Server-side tracking is a way of sending data to it and to other tools.
Not sure if you need it, or if your current tracking just needs fixing? A conversion tracking audit answers that using your own numbers.
Is your website losing the leads your ads pay for?
Free scan of one page, or the $49 Lead Leak Report for up to three.
