Table of contents
Quick answer: Server-side tracking moves your tags from the visitor’s browser to a server you control. The browser sends one stream of data to a GTM server container on your own subdomain, and that server forwards clean events to GA4, Google Ads and the Meta Conversions API. You get more durable measurement and more control over what each vendor receives.
How browser tracking breaks
Traditional tracking loads many third-party scripts in the browser. Ad blockers, browser privacy features and short cookie lifetimes stop some of those scripts or shorten how long they can recognise a returning visitor. The result is missing conversions and weaker signals for your ad campaigns.
How server-side tracking works
- Your web GTM container sends events to
data.yoursite.com, a subdomain you own. - A GTM server container running on that subdomain receives the events through a client, usually the GA4 client.
- Server tags forward the data to GA4, Google Ads, Meta CAPI or any other platform.
Because the request goes to your own domain, cookies are set in a first-party context and the setup is far less affected by browser restrictions.
What you need
- A web GTM container already working on the site.
- A server GTM container and hosting for it, either Google Cloud Run or a managed host.
- A subdomain pointed at the server with a DNS record.
- A plan for consent, so the server respects your visitors’ choices.
Setup in practice
Create the server container, deploy it to your host and map the subdomain. In the web container, set the server_container_url on your Google tag so GA4 hits go to your subdomain. In the server container, add the GA4 tag, then the Google Ads conversion tag and the Meta Conversions API tag. Finally, test in the server container’s Preview mode, where you can see each incoming request and every outgoing payload.
Deduplication matters
If you keep the Meta Pixel in the browser and also send events from the server, both must share the same event_id and event name. Meta then counts the event once. Without this, your purchases are reported twice.
Is it worth it?
Server-side tracking makes most sense for ecommerce brands, high ad spend accounts and businesses that need tighter control over data. Smaller sites with low spend can often get most of the benefit from a clean browser setup first.
FAQ
Does server-side tracking replace Google Tag Manager?
No. You use two GTM containers: the normal web container in the browser and a server container that receives and forwards the data.
Is server-side tracking a way around consent?
No. You still need consent where the law requires it, and the server container should respect the user’s consent state.
How much does hosting cost?
It depends on traffic. Small sites can run on a low-cost managed host, while large stores need more server capacity.
Want a server-side setup done properly? See my server-side tracking service.
