What server-side tracking is
Server-side tracking routes your analytics data through a server you control before it reaches Google, Meta or any other platform. The browser no longer sends hits directly to third parties. It sends them first to your server-side container, which validates, enriches and redistributes them.
In a conventional setup known as client-side, each tag runs in the user's browser. The Meta pixel, the GA4 tag, the LinkedIn script: all of them run on the client side and send their requests directly to their respective servers. You control neither what leaves nor what gets blocked along the way.
Server-side introduces an intermediary. In practice, you deploy a Google Tag Manager container hosted on a server. The browser sends a single stream of data to this container. The container then sorts everything out and relays it to each destination.
The first-party vs third-party principle
The decisive distinction is the domain. In client-side, requests go out to third-party domains (google-analytics.com, facebook.com). In server-side, the browser communicates with a subdomain of your own site, for example metrics.yoursite.com. From the browser's point of view, this is a first-party request. This technical nuance underpins most of the advantages we detail below.
Why migrate: reliability and privacy
Two reasons justify migrating: you recover lost data and you regain control over what is shared. Both have a direct impact on the quality of your marketing decisions.
Reliability: recovering lost data
Ad blockers and browser anti-tracking protections target requests to known third-party domains. A script loaded from google-analytics.com is an easy target. A request to your own subdomain is far less so. Server-side thereby escapes a significant share of the blocking.
Safari's case is emblematic. Its ITP feature caps the lifetime of first-party cookies set by JavaScript at seven days, sometimes twenty-four hours. The result: a visitor who returns after ten days is counted as new, and your conversion journeys are truncated. With server-side, cookies set by the server via an HTTP header escape this limitation and retain a standard lifetime.
Privacy: regaining control
Server-side hands you back control over the data before it leaves your perimeter. You decide precisely which fields are passed to which platform. You can mask an IP address, strip a sensitive parameter from a URL, or hash an email before sending it to Meta. In client-side, this data goes out in the clear, beyond your control.
It's a compliance asset, not an exemption. Consent remains mandatory. But server-side turns compliance from an act of faith into a verifiable technical control.
Without server-side, your analytics cookies set by JavaScript expire in less than a week under Safari. The server restores a full lifetime.
Client-side vs server-side
Client-side remains simpler and free, while server-side is more reliable and more privacy-respecting but requires infrastructure and maintenance. The table below settles the matter based on the criteria that matter.
| Criterion | Client-side | Server-side |
|---|---|---|
| Cost | Free | Hosting €40-150/month |
| Resistance to ad blockers | Low | High |
| Cookie lifetime (Safari) | 7 days max | Standard |
| Control over data sent | Limited | Total, field by field |
| Impact on page speed | Heavy client-side scripts | Lightened, server execution |
| Setup complexity | Simple | High |
The reading is clear. If you run a small site with a tight budget and low traffic, client-side is enough. As soon as conversion reliability weighs on media buying decisions, or the share of Safari and mobile traffic is high, server-side becomes worthwhile. This logic of making measurement more reliable is the same as the one underpinning a good tagging plan: you can only steer well what you measure cleanly.
Setting it up with GA4
The setup rests on a Server-Side Google Tag Manager container, hosted and then connected to GA4. Here is the sequence, with no superfluous step.
In Google Tag Manager, create a new container of the "Server" type. This is distinct from your usual web container. It will receive the data and relay it.
Deploy the container on Google Cloud (App Engine or Cloud Run) or via a third-party host such as Stape or Addingwell. This is where your collection server actually runs.
Map a subdomain of your site, for example metrics.yoursite.com, to the container. This is what makes requests first-party and gets them past the browser protections.
In your web GTM container, configure the GA4 tag to send its hits to your server-side container's URL rather than directly to Google.
Enable the GA4 client in the server-side container to receive the requests, then add the GA4 tag that forwards them to your property. Test with Preview mode and GA4 DebugView.
The data flow, step by step
Once it's in place, the journey of an event is as follows. The user acts on your page. The web GTM container captures the event and sends it to metrics.yoursite.com. The server-side container receives the request via its GA4 client, enriches or filters it according to your rules, then the server GA4 tag forwards it to your Google Analytics property. The same container can, in the same pass, relay to Meta via the Conversions API or to other platforms, without overloading the browser.
Validating that everything works
Never declare a migration complete without proof. Use GTM's server-side Preview mode to inspect each incoming request. Cross-check with GA4's DebugView in real time. Compare conversion volumes over two to four weeks against the old configuration: a positive gap confirms that you're recovering previously lost data.
Limits, costs and mistakes to avoid
Server-side is not magic. It has a cost, a complexity and some pitfalls. Knowing them prevents a failed migration.
The first barrier is the recurring cost. The GTM container is free, but hosting is not. Expect 40 to 150 euros per month on Google Cloud depending on traffic, less with a specialized shared host. The second barrier is maintenance: a collection server has to be monitored, updated and debugged. It's not an infrastructure you deploy and then forget.
On the mistakes side, three come up systematically. Believing that server-side exempts you from consent: false, GDPR applies identically. Forgetting to configure the first-party domain, which cancels most of the anti-blocking benefit. And failing to keep the client-side capture tracking, wrongly thinking that everything migrates to the server side.
This demand for clean measurement goes beyond conventional web analytics. In the age of generative engines, tracking your visibility in ChatGPT or Perplexity requires dedicated tools, as we detail in our analysis of AI share of voice. The same discipline applies: you only make progress on what you measure. To navigate a server-side migration with confidence, the support of an SEO agency that masters measurement infrastructure saves months. You can also start by framing your foundations with our GEO Audit Templates Pack.
Let us audit your visibility and measurement foundations for free. Walk away with a clear diagnosis and concrete priorities.
Questions fréquentes
Is server-side tracking legal under GDPR?+
Yes, provided you follow the same rules as conventional tracking: prior user consent, a valid legal basis and transparency in your privacy policy. Server-side actually makes compliance easier because you control precisely which data is sent to each third-party platform. It does not, however, exempt you from collecting consent.
Does server-side tracking improve SEO rankings?+
Not directly. Server-side does not influence Google rankings. Its indirect benefit is real: by lightening the scripts loaded in the browser, you reduce load time and improve Core Web Vitals, a ranking signal. More reliable data also helps you steer your SEO decisions more effectively.
How much does a Server-Side GTM container cost?+
The Server-Side GTM container is free, but hosting is not. On Google Cloud, expect roughly between 40 and 150 euros per month depending on traffic, via App Engine or Cloud Run. Alternative hosts such as Stape or Addingwell offer dedicated plans starting at around twenty euros per month.
Should you remove client-side tracking after migrating?+
No, the two coexist. The browser remains the initial point of collection: it captures the event and then sends it to your server-side container instead of sending it directly to Google. This is what's called a hybrid architecture. You're moving the dispatch to the platforms, not the detection of user actions.
