Learn · How-To
How to Set Up Server-Side Tracking for Accurate Ad Attribution
Browser-based, client-side tracking alone increasingly under-reports real conversions due to ad blockers, cookie restrictions and browser privacy changes. Server-side tracking moves the data collection point onto your own server infrastructure, restoring accuracy across ad platforms — not just one specific network's API.
- 1
Audit your current tracking setup
Identify every conversion event you currently track client-side and how much you estimate is being lost to blocking or privacy restrictions, using platform discrepancy reports as a rough guide.
- 2
Choose your server-side container approach
A server-side Google Tag Manager container is the most common path, running on a dedicated subdomain you control rather than relying solely on the browser.
- 3
Set up your server-side container infrastructure
This typically requires a small always-on server or managed hosting (e.g. via Google Cloud Run) to run the container.
- 4
Configure a first-party tracking subdomain
Routing tracking requests through your own domain, rather than a third-party one, reduces the chance of the requests being blocked by browser privacy features.
- 5
Map your client-side tags to equivalent server-side tags
Recreate your key conversion events — leads, purchases, sign-ups — as server-side tags, sending the same underlying data through the new pipeline.
- 6
Implement deduplication between client and server events
Use a shared event ID between client and server-side events so platforms don't double-count the same conversion.
- 7
Test thoroughly before fully cutting over
Run client-side and server-side tracking in parallel, comparing event counts, before relying solely on the server-side pipeline for reporting and optimisation.
- 8
Monitor server costs and uptime as an ongoing operational concern
Unlike client-side tags, a server-side container is infrastructure you're now responsible for keeping running.
Pro tips
- This is a genuine infrastructure project, not a quick tag-manager tweak — budget real developer time and ongoing hosting cost, not just a one-off setup session.
- Start with your highest-value conversion event, the same principle as platform-specific CAPI setups, rather than migrating everything simultaneously.
Related reading
Want help putting this into practice?
Take our 2-minute quiz to see where your business stands, or talk to a specialist about getting this done for you.