Server Side Tagging: A Practical Guide to Server-Side Tracking

Last updated on 14 Nov 2026
Server side tagging: tracking data goes through a server before being sent to marketing tools
An online store records 120 orders in its back office this month, but Google Ads only reports 85. Where did the others go? Ad blockers, cookies wiped by Safari, declined consent, scripts that fail to load on mobile: browser-based tracking loses part of the data. Server side tagging is one answer to this problem.

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 routes tracking data through a server you control before sending it to GA4, Google Ads or Meta.
  • It improves data quality, reduces the JavaScript loaded on the site and lets you filter what tools receive.
  • It does not remove the need for consent: GDPR and the cookie banner still apply.
  • With Google Tag Manager, the server container is hosted on Google Cloud Run or with a specialized host.
  • It requires hosting budget and technical skills: it pays off mainly for sites investing in advertising.

What is server side tagging?

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.

Client-side tracking and its limits

How does client-side tracking work?

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.

Where client-side tracking falls short

  • Ad blockers often stop tracking scripts from loading.
  • Browser restrictions: Safari sharply limits the lifetime of cookies set by JavaScript, which skews returning-visitor tracking.
  • Performance: every script adds code to run, hurting speed, especially on mobile.
  • Data control: each tool collects what it wants straight from the browser; you don’t see everything that leaves.

How does server-side tracking 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.

Client-side vs server-side tracking: many scripts in the browser versus a single stream to a server

Server side tagging vs client-side: comparison

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
Client-side vs server-side tagging: the differences.

The benefits of server side tagging

Better data quality

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.

More control for compliance

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.

A faster site

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.

Server-to-server integrations

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

Is server side tagging right for you?

Check what matches your situation
Is server-side tagging right for you? 9-point self-check (indicative, nothing is saved)

Setting up server side tagging with Google Tag Manager

The main steps to set up Google Tag Manager server side:

  1. Create a server container in Google Tag Manager, alongside your existing web container.
  2. Host the server: automatic provisioning, recommended by Google to get started, creates a Google Cloud project and a Cloud Run server. Google notes that this initial deployment has limited resources and is meant for testing low traffic volumes, so it must then be sized for production. Specialized hosts such as Stape also offer a simplified setup.
  3. Configure a subdomain of your site (for example metrics.yoursite.com) pointing to the server, to work in a first-party context.
  4. Send data to the server: the site’s Google tag is configured to forward events to the server URL.
  5. Configure clients and server tags: GA4 client, GA4 tag, Google Ads conversion tag, Meta Conversions API and so on.
  6. Test in preview mode, compare data before and after, then publish.

This takes technical skills (DNS, Google Cloud, tag configuration) and serious testing: a misconfiguration can lose more data than it recovers.

Server side tagging setup: cloud server container, subdomain and visitor consent

Server-side tracking tools

  • Google Tag Manager server side, the most widespread option, hosted on Google Cloud Run or other infrastructure.
  • Specialized hosts for server GTM containers, which manage the infrastructure for you.
  • Platform conversion APIs: Meta Conversions API, social network APIs, Google Ads enhanced conversions.
  • Customer data platforms and server-side analytics for more advanced organizations.

Costs and constraints of server-side GTM

Initial investment

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.

Ongoing costs

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.

Common mistakes

  • Believing server-side replaces the cookie banner.
  • Keeping the test provisioning in production, with an undersized server.
  • Skipping the first-party subdomain, which cancels much of the benefit.
  • Double-counting conversions by leaving old browser tags active.
  • Not comparing data before and after the switch.
  • Not documenting the setup, which makes it impossible to maintain.

Conclusion: an investment for the right cases

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.

Frequently asked questions about server side tagging

Does server-side tagging remove the need for a cookie banner?

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.

What are the most common server-side tagging tools?

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.

Does server-side completely replace client-side tracking?

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.

How does server-side tagging work with Google Consent Mode v2?

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.

What is the Meta Conversions API and how does it relate to server-side?

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.

Where should you host a server-side Google Tag Manager container?

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.

Sources