A server-side tracking set-up

How events travel from a website to the ad platforms through a first-party server, and where consent and deduplication happen.

By Imran Kapadia · 3 Oct 2026

Figure 1. A server-side tracking set-up.

1
Browser
The page sends one first-party request per event, after checking consent.
2
First-party endpoint
A subdomain you control receives the event, so fewer requests are blocked.
3
Server container
Cleans, enriches and filters the event. Personal data is hashed or removed here.
4
Platform APIs
Conversion APIs receive only the fields you choose. Event IDs prevent double counting.
5
Warehouse
A copy of every event goes to your own storage, so reports can be reconciled with finance.

Plain-English summary

The browser still starts the journey, but it talks to one address you own instead of many third parties. A server you control decides what is sent onward, to whom, and in what form.

Implementation notes

Send the same event ID from the browser and the server so each platform can deduplicate.
Apply consent before the first request leaves the browser, not on the server.
Log what the server sends for one week before you switch off the browser tags.
Budget for hosting and maintenance. A server container is infrastructure, not a one-off task.