Lesson 2 of 7 · 4 min read
Why everybody is talking about server-side tracking
For years, tracking meant one thing: a few lines of JavaScript in the browser that sent each visit to Google, Meta and the rest. That model is breaking, and server-side tracking is what replaces it.
- Collect
- Store
- Use
- Activate
The browser stopped being a reliable messenger
Safari limits how long cookies set by scripts survive. Firefox and Brave block known trackers by default. Ad blockers remove tags altogether. Each of these takes a slice of your clients’ data, and the slices add up.
The result is familiar to every agency: conversions in the ad platform that do not match the shop, campaigns that look worse than they are, and clients asking why the numbers disagree.
Consent changed what may be collected
In the UK and the EU, a visitor decides what is stored. Google Consent Mode v2 made this concrete: tags behave differently depending on the answer, and platforms model what they cannot see.
Server-side tracking does not get around consent. It makes the data you are allowed to collect arrive complete and on time.
The ad platforms are asking for it
Meta has its Conversions API, Google has enhanced and offline conversions, LinkedIn, TikTok, Microsoft and Reddit all accept conversions sent from a server. They ask for it because their bidding works better with it.
When the platforms that spend your clients’ budgets all recommend the same thing, it stops being a technical detail and becomes part of running good campaigns.
Key takeaways
- Browser-only tracking loses more data every year, for reasons outside your control.
- Consent decides what may be collected; server-side decides whether it actually arrives.
- Every major ad platform now accepts, and recommends, conversions sent from a server.
For your marketing agency
Your clients will hear about server-side tracking from their platforms, their developers or a competitor agency. Being the agency that explains it first, calmly and without jargon, is a position worth having.