Server-side tracking
With server-side tracking, your own server passes data on to Google, Meta and other services. You control what is shared, and pages load faster.
The limits of browser-based tracking
With classic tracking, the browser sends data straight to every provider, which means many scripts, slower pages and little oversight. Ad blockers and Safari's Intelligent Tracking Prevention also lose data. Missing conversions weaken the optimisation of paid campaigns.
How it works
The browser sends a single data stream to a tagging server under your domain, which routes it onward. We usually run server-side Google Tag Manager in an EU region, plus official server APIs such as the Meta Conversions API.
Benefits
Control: truncate IP addresses, remove identifiers, filter data before it reaches third parties
Page speed: fewer scripts in the browser
Data quality: more stable first-party cookies and more reliable conversion tracking
Data such as margin or customer status can be added without exposing it in the browser.
Legal framework
Server-side tracking does not bypass consent. Section 25 of the German TDDDG still covers identifiers in the browser, so consent also governs which data goes where on the server.
We document the data flows for your record of processing activities.
Effort and operations
A tagging server brings ongoing hosting costs. We set it up, monitor availability and costs, and handle updates. For smaller websites, we first check whether it pays off.