# Server-side Tracking: Recover the conversions your tracking is missing

Learn how Server-side Tracking recovers conversions lost to browser restrictions, improves control and creates a first-party data foundation.

Source: https://taggrs.io/server-side-tracking/
Author: Małgorzata Poddębniak, Content Marketer · [LinkedIn](https://www.linkedin.com/in/malgorzatapoddebniak/)
Updated: 2026-11-13

---

Roughly 20% of traffic now sits outside conventional tracking, blocked by browsers, cookie limits and ad blockers. Server-side Tracking moves data collection onto a server you control, so you recover those conversions and build a strong first-party foundation.

## What is Server-side Tracking?

Server-side Tracking moves data collection out of the visitor's browser and onto a server you control. Instead of your website sending data straight to Google Analytics, Meta or Google Ads, it sends data to your own server first. From there, you decide which data gets forwarded, where and in what form.

- **Third-party cookies blocked**: Safari, Firefox and Brave block third-party cookies by default, which puts roughly 20% of global traffic outside the reach of conventional tracking.
- **Cookies capped at seven days**: Safari's ITP caps the life of browser cookies at as little as seven days, so a visitor who converts two weeks after clicking your ad can't be attributed to the channel that brought them in.
- **Ad blockers**: Ad blockers strip requests before they ever fire. Google's decision to keep third-party cookies in Chrome didn't fix any of this: the erosion of browser-collected data is gradual and not tied to a single deadline.

**~20%** of global traffic sits outside the reach of conventional tracking.

Server-side Tracking helps you get a first-party data foundation that survives the next browser update.

## Where do you want to start?

### See what data you're currently losing

Scan your site and get every ad pixel, server-side connection, cookie and consent setting in one report, each with a status and a recommended fix. Free, no account needed.

### Understand the fundamentals

A 13-chapter guide explaining where tracking breaks, what the gaps cost your campaigns, plus a five-question self-assessment.

### Start building your setup

The full Server-side Tracking implementation checklist, from web container through subdomain to hosting.

## Server-side Tracking vs. Client-side tracking

Server-side Tracking is an alternative to client-side tracking, the traditional way of tagging. Here you place pixels and cookies directly in the user's browser. From there, user data is sent to the software you use, such as Google Analytics 4 and Google Ads. The disadvantage is that this data stream can be blocked.

With Server-side Tracking, the data flow runs differently. You load the tracking scripts from your own domain and send the data to your own server first. This creates an intermediate layer. From your own server, you can decide which data to share with which software. The big advantage is that the data stream is far harder to block.

|  | Client-side | Server-side |
| --- | --- | --- |
| Where data is collected | The visitor's browser | A server you control |
| Blocked by ad blockers | Yes | Rarely |
| Third-party cookies in Safari, Firefox and Brave | Blocked | Not dependent on them |
| Cookie lifespan under ITP | As short as 7 days | Extendable |
| Control over what each platform receives | None | Per destination, before it leaves |
| Effect on page load | Every pixel is another script | Handled off-browser |
| Where data is processed | Wherever the vendor's servers are | The region you choose |
| Setup effort | Low | Moderate |

## The benefits of Server-side Tracking

Here are five things you get back when data collection moves to the server.

### More data at your disposal

Server-side collection picks up conversions that browser-based tracking either loses or can't connect to a campaign, such as a request an ad blocker would have filtered out, or a purchase that happens two weeks after the click, long after Safari has dropped the cookie that identified it. Those events reach your server because they don't depend on a third-party request surviving browser limitations.

### Privacy compliance

Server-side Tracking doesn't remove the need for consent, but it does change how much of the data flow you can see and control. You choose the region where your processing happens and decide which fields go into each request before it is forwarded. For instance, Google Ads can receive a conversion value without the visitor's IP address.

### Improved site performance

Every client-side pixel is a separate script the browser has to fetch and run, on the same device that's rendering your page. Each one sets up its own third-party connection.

### More control over your data

With client-side tracking, you make the data available to every tag you install. A pixel running on the page can read what's around it, such as the URL and its parameters, the data layer and, in some cases, even form fields.

### Better flexibility

Your most valuable conversion data often isn't on your website, but rather in your CRM, transaction system or call tracking.

## Set up Server-side Tracking for your platform

Each platform has its own setup. Pick yours for the step-by-step guide.

### Ad platforms

- GA4
- Meta / Facebook
- Meta CAPI Gateway (Fully hosted)
- Google Ads
- LinkedIn
- TikTok
- Pinterest
- Snapchat

### CMS & CRM

- Shopify
- HubSpot

## Are there any disadvantages to Server-side Tracking?

Every solution has some drawbacks, and so does Server-side Tracking. The four main disadvantages are:

### Not every software has the capability for Server-side Tracking yet

A good example is Hotjar. You can only install this tag client-side.

With the Google Tag Manager setup we recommend, this is not a problem: you can install both server-side and client-side tags in it.

### The complexity

Server-side Tracking is an additional dimension you add to the existing structure, and debugging is less familiar than in the web container.

Our documentation and debugging guide cover the setup step by step.

### The cost

To use Server-side Tracking through Google Tag Manager, you need server space, which you can arrange through Google Cloud. However, this typically costs more than €100 per month.

TAGGRS offers a focused Server-side Tracking hosting product with a free subscription up to 10,000 requests, while paid subscriptions start at €25 per month. [Find the plan that fits your tracking needs.](/prices/)

### Your numbers will change

After switching, you'll usually see more conversions recorded than before. This is one of your goals, but it means historical comparisons break at the switchover date.

Plan for a period of parallel measurement so you can explain the shift to stakeholders and aren't surprised by it.

## What is the difference between a web container and a server container?

### Web container

A web container runs in the visitor's browser. Tags fire there and send data straight to the platforms you've configured.

### Server container

A server container runs on a server you control. It receives data first and from there, you decide what gets sent to which platform.

In most setups, the two work together. The web container collects the event and passes it to the server container, which handles the forwarding.

## What the regulations actually require

Server-side Tracking is not a way around consent. Under the ePrivacy Directive, storing or reading information on a user's device requires consent regardless of whether the cookie is first-party or third-party. A first-party setup doesn't exempt you, and server-side setups still set cookies. Moving collection to your own server changes where data is processed and who controls it, but it doesn't change whether you need user permission to collect it.

What it does change is your position. You decide what leaves your server, you can anonymize or drop fields before forwarding data to other tools, and you choose the region where processing happens. That's a considerably stronger place to answer a DPO's questions.

## How do you get started with Server-side Tracking?

There are several ways to implement Server-side Tracking, but we prefer Google Tag Manager. Most companies are already using it, so you're extending your existing tag structure rather than starting over. You can also remove it again just as easily, which makes it low-risk to test. If you only need Meta, the Meta CAPI Gateway is a more specific, fully hosted alternative that skips the container setup.

1. A Google Tag Manager web container
2. A Google Tag Manager server container
3. A subdomain for the server
4. Hosting for the server
5. Optional: A working data layer (recommended for ecommerce)

## Questions and answers

**Do I still need Server-side Tracking now that Google kept third-party cookies in Chrome?**

Yes. Chrome keeping third-party cookies doesn’t affect Safari, Firefox or Brave, which block them by default. It also doesn’t affect ad blockers or ITP, which caps the lifespan of browser-set cookies at as little as seven days. The Chrome deadline was never the whole problem. It was just the most publicized part of it.

**How much data am I losing without Server-side Tracking?**

It depends on your audience and the browsers they use. Safari, Firefox and Brave block third-party cookies by default, which puts roughly 20% of global traffic outside the reach of conventional tracking, and ad blockers and Safari’s cookie limits cost you more data on top of that. The free TAGGRS [Tracking Checker](/website-tracking-checker/) scans your site and checks your ad pixels, server-side connections, cookies and consent settings. You get a tracking score with a status and a recommended fix for each item. No sign-up required.

**Does Server-side Tracking work against ad blockers?**

Yes. Ad blockers rarely block server-side requests. With Server-side Tracking, you load the tracking scripts from your own domain and send data to your own server first, which makes the data stream far harder to block. The TAGGRS Enhanced Tracking Script also defends against ad blockers and ITP with advanced masking techniques.

**How much does Server-side Tracking cost?**

Server-side Tracking through Google Tag Manager needs server space to host your server container. You can arrange this through Google Cloud, which typically costs over €100 a month. TAGGRS is a focused Server-side Tracking hosting product with a free plan of up to 10,000 requests a month and paid plans from €22 a month. See all [plans and prices](/prices/).

**How do I switch from client-side to Server-side Tracking?**

You don’t have to switch everything at once. With Google Tag Manager, you extend your existing tag structure rather than starting over, and you can remove the server-side setup just as easily, which makes it low-risk to test. Plan for a period of parallel measurement, so you can compare results and explain the change in your numbers to stakeholders. Our [Server-side Tracking checklist](/server-side-tracking/checklist/) takes you through the setup step by step.

## Get started with Server-side Tracking

Move data collection onto a server you control, recover missed conversions and build a strong first-party foundation.

- [Create a free account](https://dashboard.taggrs.io/register)
- [Talk to us](/demo/)
