Server-side tracking moves part of the measurement work from the browser to a server you control. This guide explains how it works, what it really brings (and what it doesn’t), how to set up Google Tag Manager server side, the costs to expect and how it fits with GDPR consent. A self-check helps you decide whether server-side GTM is worth it for you.
At a glance
Server side tagging is a tracking method in which measurement tags no longer all run in the visitor’s browser. The site sends events (page views, add to cart, purchases) to an intermediate server, often on a subdomain such as metrics.yoursite.com. That server receives the data, cleans it if needed, then forwards it to each tool: Google Analytics 4, Google Ads, Meta and so on.
With Google Tag Manager, this server is a “server container”. According to Google’s documentation, server-side tagging moves measurement tag instrumentation from your website or app to a server-side processing container on Google Cloud or another platform.
In the classic model, each tool installs its own script. When a visitor opens a page, the browser loads the GA4 script, the Google Ads tag, the Meta pixel, sometimes LinkedIn or TikTok, and each sends data straight to its vendor. It is simple, free and still how most sites work.
The browser sends a single data stream to your tracking server. The server container receives requests through “clients” (for example the GA4 client), then fires server-side tags that forward the data to each tool. In between, you can enrich data (margin, customer status), remove some of it (IP address, URL parameters containing an email) and decide exactly what each partner receives.
In most setups, part of the tracking stays in the browser: the Google tag or a web container sends events to the server. Server-side does not fully replace client-side; it complements it.
![]()
| Criterion | Client-side (browser) | Server-side (server) |
|---|---|---|
| Where tags run | In the visitor’s browser | On a server you control |
| Scripts loaded on the site | One script per tool (GA4, Ads, Meta…) | A single stream to your server |
| Ad blockers | Often block tags | Less affected with your own subdomain |
| Cookie lifetime (Safari) | Limited for JavaScript-set cookies | First-party cookies set by the server |
| Control over data sent | Each tool gets what it collects | Filtering and anonymization before sending |
| Site performance | More JavaScript to run | Less code in the browser |
| Consent (GDPR) | Required | Still required |
| Cost and complexity | Low | Hosting and expertise required |
With your own subdomain and server-set cookies, part of the data lost in the browser is recovered: conversions attributed more accurately, returning visitors recognized more reliably. Ad campaigns, which optimize on reported conversions, benefit directly. Be wary of percentage promises: the gain depends on the site, its audience and the setup.
The server is a checkpoint where you decide what is sent: removing IP addresses, stripping personal information, limiting what is shared depending on consent. It helps with GDPR or other privacy laws, but it is not an exemption.
Fewer third-party scripts in the browser means less JavaScript to download and run. Google lists improved performance among the advantages of server-side tagging. For speed metrics, see our guide to LCP, INP and CLS.
The server container easily feeds platform conversion APIs, such as the Meta Conversions API or Google Ads enhanced conversions, and can receive data from other systems (CRM, store back office).
Do your Google Ads conversions not match your sales? See our PPC management services
The main steps to set up Google Tag Manager server side:
metrics.yoursite.com) pointing to the server, to work in a first-party context.This takes technical skills (DNS, Google Cloud, tag configuration) and serious testing: a misconfiguration can lose more data than it recovers.

Setup takes several days of work for an ecommerce site: audit of current tracking, server and subdomain configuration, tag setup, testing and documentation. It also requires a clear tracking plan: poorly designed browser tracking stays poorly designed on the server.
The server is billed on computing power and traffic, whether on Google Cloud or with a specialized host. High-traffic sites also need maintenance: container updates, monitoring and adjustments when a platform changes its rules. Google provides a pricing calculator to estimate Cloud Run costs for your volume.
This is the most common misconception: server side tagging does not let you skip consent. As soon as you set cookies or track visitors for advertising, GDPR and cookie rules apply, whether the tag runs in the browser or on a server. The cookie banner remains mandatory.
Server-side does, however, work very well with Google Consent Mode v2: the visitor’s choice is sent to the server with each event, and server tags respect it. The server also lets you go beyond what the law requires, for example by removing IP addresses before anything is sent.
Server side tagging improves data quality, site speed and control over what you send to platforms. It costs hosting, expertise and maintenance, and never removes the need for consent. Our advice: start with clean client-side tracking and a properly configured Consent Mode v2; move to server-side when ad spend, the gap between sales and measured conversions, or compliance requirements justify it.
No. GDPR and cookie rules apply wherever tags run. Server-side gives you more control over the data sent and lets you respect visitor choices more precisely, but collecting consent remains mandatory for advertising measurement.
Google Tag Manager server side is the most used, hosted on Google Cloud Run or with a specialized host such as Stape. It is often combined with platform conversion APIs, such as the Meta Conversions API or Google Ads enhanced conversions.
No, in most cases it complements it. A tag stays in the browser to capture interactions and send events to the server, which then distributes them to each tool. The number of third-party scripts loaded by the site drops sharply.
The visitor’s consent status is sent to the server container with each event. Server tags follow it: full data if the visitor accepts, limited cookieless signals if they decline. The server can also remove certain data before anything is sent.
The Meta Conversions API sends events (purchases, leads) directly from a server to Meta, without relying on the browser pixel. A server-side Google Tag Manager container is one of the simplest ways to feed it, alongside the pixel.
Google’s recommended option is Cloud Run, created automatically during provisioning and then sized for production. You can also use your own infrastructure or a specialized host, which simplifies setup and maintenance for a subscription.
EXCELLENT Based on 22 reviews Posted on Google pierre lenfantTrustindex verifies that the original source of the review is Google. Aurone is a web agency like no other! Very responsive, highly flexible in the way they work and always at the cutting edge of technology: you can count on real professionals for all your web projects!Posted on Google Sami Yassine TurkiTrustindex verifies that the original source of the review is Google. As Secretary General of the Lina Ben Mhenni association, it was a pleasure to work with the AURONE agency, which developed our website with great professionalism.Posted on Google Gwladys LavergneTrustindex verifies that the original source of the review is Google. Responsive, attentive and highly skilled: we are delighted to work with Aurone, who meet our expectations perfectly, both in graphic design and in technical expertise. I highly recommend their support!Posted on Google Perrine AmalTrustindex verifies that the original source of the review is Google. Aurone is a human, responsive and efficient company. The work was done quickly and promptly. I highly recommend them and hope to continue this collaboration in the future.Posted on Google Stephanie WillmanTrustindex verifies that the original source of the review is Google. We have been working with Aurone since 2016 and are delighted. We first called on their services for a project in Tunisia, and the quality of their work means we now rely on Aurone for services in other countries too. The team is dynamic, creative, responsive and enthusiastic. They have always understood our needs for our diverse and complex web presences, and do their best to meet them. Web platforms, training workshops on the platforms, video tutorials and graphic design for various products are just some of the excellent services Aurone provides. The technical quality of their web services is top-notch, and we always get good advice, both technical and creative. We highly recommend them.Posted on Google Raphaël GianassoTrustindex verifies that the original source of the review is Google. For your e-commerce and digital marketing projects, the Aurone team is attentive, experienced, available and responsive. A team you can count on, for whom customer satisfaction comes first.Posted on Google Samuel DechometsTrustindex verifies that the original source of the review is Google. At Aurone I found everything you can expect from a good web agency: quality, responsiveness, flexibility, relevance... Well done and thank you!Posted on Google Karim DjebbarTrustindex verifies that the original source of the review is Google. Our whole network worked with the Aurone agency for several years. A few adjustments were needed at the start of our partnership back then, but quality quickly followed.
The teams worked very professionally, adapting to the requirements of the French clients we soon put them in touch with.
A great deal of agility from its founder.
Thank you for these great years!
27 Avenue Taieb Mhiri, Immeuble Yasmina
2080 Ariana, Tunis, Tunisia
Made with in Tunis | Copyright © 2007-2026 Aurone | Legal notice | Privacy policy | Shop