Data and Tracking
Is server-side tagging worth it for you?
With server-side tagging, measurements run through a server container instead of in the browser alone; Google names three reasons: better site performance, more detailed privacy controls and better data quality g-sst. The server container uses the same model of tags, triggers and variables as the web container g-sst. The effort is not in setting it up but in running it: from then on the container is a system that has to run, cost and be monitored.
What we do: We weigh operating cost against the gain in data quality, think consent in from the start, measure in parallel before switching and monitor the container permanently; you get server-side tagging only if it pays off for you, and then one that runs.
By Robin Kardinal, Chief Operation Officer (COO)
Last updated on
What it is about and when it becomes relevant
What changes
Instead of every tool running its own scripts in the browser, one data stream goes to your server container, which distributes onward. Google names improved site performance, more detailed privacy controls and better data quality as the advantages g-sst. The model of tags, triggers and variables stays the same as in the web container g-sst.
When it becomes relevant
When so many scripts run in the browser that load time suffers, when measurements regularly get lost to browser settings, or when you want to control which fields go to which vendor at all. For a small site with two tools, running it rarely pays off.
What makes work afterwards
The container is infrastructure: it has costs, needs its own subdomain setup, must be monitored and fails when nobody watches. Whoever sets it up and then forgets it has not improved the measurement, only relocated it.
Common mistakes and how you spot them
Set up server-side, left running client-side
How you spot itThe browser's network log still shows all the old scripts. Load time has not improved; the costs are there anyway.
Consent stays in the old setup
How you spot itThe server container keeps sending although the browser declined. Checkable by whether the consent parameters travel along g-consent.
No monitoring
How you spot itAn outage only gets noticed when conversions are missing in the monthly report. With client-side tagging you notice immediately, here you do not.
More fields transferred than needed
How you spot itPersonal fields flow through the container to vendors that do not need them. The privacy advantage then turns into its opposite.
How we go about it
Calculate first, build second
We put running costs against the expected gain in data quality. For small setups the honest answer is often that it does not pay off.
Think consent in from the start
The consent parameters belong in the setup, not next to it afterwards g-consent. Otherwise the container measures cleanly and legally wrong.
Measure in parallel, then switch
Old and new run side by side for a while, so deviations can be explained before the old route is switched off.
Monitor permanently
Outages and deviations get flagged automatically, so they surface the same day and not in the quarterly report.
Further reading
This topic belongs to Tag Management.
Frequently asked questions
What is server-side tagging?
A measurement that runs through a server container instead of in the browser alone. Google names better site performance, more detailed privacy controls and better data quality as the reasons g-sst.
Do I need a new container for it?
Yes, a server container. It uses the same model of tags, triggers and variables as the web container g-sst, but runs on its own infrastructure.
Does server-side tagging solve my consent problems?
No. Consent applies regardless of where a tag is executed. The consent parameters have to travel with the setup g-consent, otherwise you measure cleanly and still without a legal basis.
Does my website get faster from it?
Only if you also switch off the client-side scripts afterwards. Google explicitly names improved site performance as an advantage g-sst, but it only appears once less actually runs in the browser.
What does running it cost?
That hangs on traffic and hosting; any general number would be a guess. The calculation itself is simple and belongs before the decision, not after.
Is this exactly where you are stuck?
Write to us about where it is stuck. Robin Kardinal and the team will look at what is concretely behind it in your case, and tell you where the biggest lever sits.
Sources
Every statement about ad products comes from the official documentation of the respective platform, with the date we retrieved it. Products change; if something looks outdated to you, write to us and we will check it.
- g-sstGoogle Tag Platform, Serverseitiges Taggingretrieved on 21.9.2026
- g-consentGoogle Tag Platform, Einwilligungsmodusretrieved on 21.9.2026
Content and images on this page may have been created with AI support.