Short answer: with server-side tagging the browser doesn’t send data straight to each platform, but first to a Google Tag Manager server container you manage. That server forwards the data to GA4, Google Ads, Meta and other platforms. You get more control over what gets through and less code in the browser. Consent is still required, and it costs hosting and maintenance.
By the TrackLead team. Technically reviewed by Pieter. Updated: November 2026.
What server-side tagging is
With regular tracking the visitor’s browser loads one tag per platform: the Google tag, the Meta Pixel, the LinkedIn Insight Tag. With server-side tagging the browser first sends the data to a tagging server: a Google Tag Manager server container that you or your client manage. Only that server forwards the data to GA4, Google Ads, Meta and other platforms.
Google’s term is server-side tagging. In the market you also hear server-side tracking or sGTM. It is the same idea.
How it works
The browser sends a request to the server, on a subdomain or path of the website itself.
A client in the server container receives the request and turns it into event data. A new container includes a GA4 client by default.
Tags in the server container forward that event data to the platforms, each in its own format.
Triggers and variables decide which tag fires when and which fields go along, just like in the web container.
Because the server sits between the browser and the platforms, you decide what gets through. For example, you can remove an IP address before it reaches a platform.
What you gain
Control over data: you choose per platform which fields you forward.
Less code in the browser: one request to your own server instead of a script per platform. Google mentions better performance as a benefit.
Cookies from your own domain: the server can set first-party cookies. In Safari these last longer than cookies set by a script, as long as the subdomain doesn’t point to another party through a CNAME or run on a very different IP network.
A base for Conversions APIs: Meta recommends using the Pixel and the Conversions API together. A server container lets you send those server events too.
What it doesn’t fix
Consent. You still need consent. See Consent Mode v2 in GTM.
Ad blockers. Filter lists such as EasyPrivacy also block known server container paths and subdomains.
A poor data layer. If the website passes the wrong value, the server forwards it too.
Maintenance. It is an extra layer that can break when a platform changes something, and it costs money to host.
What you need
A server container in Google Tag Manager, next to the web container.
Hosting: Google Cloud Run in your own or your client’s Google Cloud account, or a managed host such as Stape, TAGGRS or Addingwell. Google recommends at least two servers for production, at roughly 45 dollars per server per month on Cloud Run.
Your own subdomain or path on the website’s domain.
Working consent and a clean data layer.
What to sort out for each point is in what to sort out before you start with server-side tracking. The build steps are in the complete guide to server-side GTM.
When it is worth it
Server-side tagging pays off when the client steers budget on conversion data, when platform numbers clearly differ from the store or CRM, or when the client advertises on Meta or LinkedIn and wants to use the Conversions API. If the client mainly uses GA4 and spends little on ads, a good web container is often enough.
A middle step for Google tags only is Google tag gateway: it loads the Google tag from your own domain, without a server container. The difference with regular tracking is in client-side vs server-side tracking.
With TrackLead you set up the implementation in your client’s own GTM, on the host you already use, with monitoring included. Take a look at tracklead.eu.
Frequently asked questions
Is server-side tagging the same as server-side tracking?
In practice, yes. Google calls it server-side tagging: tags run in a server container instead of in the browser. Server-side tracking is the broader term used in the market.
What does server-side tagging cost?
Google estimates roughly 45 dollars per server per month on Cloud Run and recommends at least two servers for production. Managed hosts charge a subscription. More in what a setup really costs.
Does server-side tagging bypass ad blockers?
Not reliably. Filter lists such as EasyPrivacy also block known server container paths and subdomains.
Do I still need a cookie banner?
Yes. Server-side tagging changes the route the data takes, not whether you need consent.