Lesson 4 of 7 · 5 min read
Learn to use server-side tracking
You do not need to become a developer to use server-side tracking well. You need to know what a good setup contains, what to ask for, and how to check it.
- Collect
- Store
- Use
- Activate
What a working setup consists of
An endpoint on the client’s own domain that receives events. Consent applied before anything is stored or forwarded. Connections to the platforms that matter, such as GA4, Google Ads and Meta. And a place where the data is kept, ideally the client’s own warehouse.
Questions to ask any provider
Does collection run on the client’s own domain and server, or on a separate one? Is browser and server data deduplicated, so conversions are not counted twice? Where is the data stored, in which region, and who owns it? What happens when tracking breaks, and who notices?
How to know it works
Compare conversions in the platforms with the source: orders in the shop, leads in the CRM. The gap should shrink after the switch. Watch event match quality in Meta and enhanced conversion coverage in Google Ads. And keep an eye on event volumes: a sudden drop is the clearest sign that something broke.
Where to start
Pick one client with clear conversions, such as a shop or a lead-generation site. Measure the gap between the platforms and the source for a month before and after. That before-and-after is also the best story you can tell your next client.
Key takeaways
- A setup is an own-domain endpoint, consent, platform connections and a place to keep the data.
- Ask where collection runs, how deduplication works and who owns the data.
- Judge success against the source, not against the old numbers.
For your marketing agency
Start with one client and document the before-and-after. It is the proof you need to roll it out across your book, and the case study that wins the next pitch.