Table of content
If you manage advertising budgets for your clients, you have probably already seen the gap: the back office reports 100 sales, Google Ads claims 70, Meta 50, and no one knows who's telling the truth anymore. This isn't a bug. It's the slow death of traditional tracking — and server-side tracking is the answer.
At A-Track, we deploy this architecture every week for Swiss agencies and advertisers. Here is what server-side tracking really is, why it has become essential, and how it works — without unnecessary jargon.
What is server-side tracking? (Definition)
Server-side tracking is a data-collection method that shifts processing from the user's browser (the "client") to a server you control. Instead of sending data straight from the browser to Google, Meta or TikTok, it routes the data through an intermediate step: your own tagging server.
To grasp the difference, let's compare the two approaches.
1. Client-side tracking (the "Pixel" method)
This is the legacy method. The user's browser (Chrome, Safari) loads dozens of third-party scripts (the GA4 tag, the Meta Pixel, the LinkedIn insight tag…) and sends data directly to each platform.
Diagram 1 — Client-side tracking. Browser (Chrome, Safari) → direct send → Google Ads · Meta · GA4 · TikTok · LinkedIn. This flow is blocked by AdBlockers, ITP and the end of third-party cookies: 15 to 30% of conversions are lost.
The problem: this flow is increasingly blocked. Ad blockers (used by 25–30% of Swiss users), Apple's ITP capping cookie lifetime at 7 days, and the phase-out of third-party cookies erode your data. The result: you lose data, and your Smart Bidding algorithms run blind.
2. Server-side tracking
Here, the browser sends data to an intermediate server hosted on a subdomain of your client (e.g. data.yourclient.ch). This server — usually a server-side Google Tag Manager (sGTM) container — cleans, anonymizes and then forwards the data to the platforms via their server-side APIs.
Diagram 2 — Server-side tracking (A-Track). Browser → A-Track server (1st-party subdomain · sGTM via Stape, EU · cleansing · anonymization · API) → Google Ads · Meta · GA4 · TikTok · LinkedIn. Result: nFADP / GDPR compliant and up to 40% of data recovered.
The advantage is twofold: requests originate from your own domain (invisible to blockers), and you decide exactly which data goes to each platform.
The benefits of server-side for your campaigns
Beyond the technicalities, here is what server-side concretely changes:
More reliable collection. By bypassing ITP and ad blockers, you recover the 15–40% of lost conversions — the raw material of your advertising algorithms.
Durable first-party cookies. With a dedicated subdomain, cookie lifetime goes from 7 days (ITP) to 400 days. Your attribution windows become realistic again.
Resistance to blockers. Since requests leave from your main domain, they are no longer flagged as "third-party tracking".
Data control (governance). Each platform receives only what you configured. No more uncontrolled harvesting by Google or Meta on your client's site.
Enrichment. The server can complete the data (order value, CRM status, offline conversions) before sending it.
A faster site. Fewer third-party scripts in the browser means better Core Web Vitals — a meaningful SEO bonus.
nFADP / GDPR compliance. You can filter an IP or an email before sending data to US servers. That's "Privacy by Design", highly valued by Swiss DPOs and auditors.
The most common use cases
Server-side isn't a technical fad: it answers very concrete needs. The most common ones:
Meta Conversions API (CAPI): sending events from your server to Meta, including for opt-out iOS users.
GA4 server-side: extending cookie lifetime and cleaning data before Google.
Google Ads server-side: moving conversion tags to the server for more reliable tracking and a faster site.
TikTok Events API: essential for a 100% mobile audience where the in-app browser breaks classic tracking.
LinkedIn CAPI: reliable tracking of high-value B2B leads.
Offline & CRM conversions: reconciling phone, in-store or CRM-signed sales with online campaigns.
Server-side = server-side Google Tag Manager (sGTM)
Several tools can do server-side, but our default choice remains the server-side Google Tag Manager container. Why?
No license cost: you only pay for server hosting.
A version-control system: every change is traceable and reversible.
Multi-user mode and a mature template ecosystem.
For hosting, we favour Stape (EU servers), far simpler and cheaper than a hand-managed Google Cloud instance, with key features such as the Custom Loader anti-AdBlock.
Understanding tracking as a 3-layer system
The clearest way to picture modern tracking is as a three-layer structure where each layer complements the others.
Diagram 3 — The 3 layers of web tracking:
Layer 1 — Browser: collection (interactions, dataLayer, consent via the CMP).
Layer 2 — Tagging server (sGTM): control, compliance, data cleansing and enrichment.
Layer 3 — Destinations: GA4, Google Ads, Meta, TikTok, LinkedIn.
Client-side and server-side don't compete: they cooperate. The server layer is simply the one that gives you back control, reliability and compliance.
The A-Track method: server-side AND compliant
Enabling server-side without thinking about compliance just moves the problem. Our approach systematically combines performance and legal safety:
EU hosting via Stape, to limit transfers outside Europe.
1st-party subdomain for durable cookies and reliable measurement.
Data cleansing (IPs, emails) before any send to the platforms.
Hybrid setup Pixel + CAPI with deduplication, so no event is lost.
CMP & Consent Mode v2 properly configured, because non-consented data has no value.
Server-side is not "an option for large accounts". The moment a client invests in online advertising, every lost conversion is wasted budget. The real question isn't "should we switch to server-side?" but "how much does not having done it cost?".
Your clients are losing conversions without knowing it
Entrust the tracking "engine" to specialists and focus on the performance of your campaigns. See also our complete 2026 guide to server-side in Switzerland.
Your clients are losing conversions without knowing it.
Between Apple's ITP and ad blockers, up to 40% of conversions vanish from your reports. A-Track deploys a reliable, nFADP/GDPR-compliant server-side architecture hosted in the EU via Stape. Hand us the tracking engine and focus on campaign performance.
