# Server-side tracking

https://seo7.es/en/servicios/trafico/server-side-tracking  
Updated: 2026-10-05

*Ads & traffic*

Browser tracking loses data to ad blockers and iOS: server-side tracking restores conversion accuracy.

Server-side tracking moves event data collection from the browser to a secure server. Result: ad blockers and cookie restrictions no longer affect campaign statistics. The basics of setup and the underlying principle are explained on this page.

- **Ad blockers don't interfere** Requests go from the server directly to GA4, Meta and other platforms, bypassing browser extensions.
- **Conversion accuracy** Server GTM captures events that the browser container loses due to iOS ITP and Safari restrictions.
- **Long-lived cookies** First-party cookies set via the server last up to 400 days instead of 7 days with a browser script.
- **Single control point** The server GTM container centralises all tags and simplifies GDPR and ePrivacy compliance.

## Quick answer

Server-side tracking collects site event data through a secure server instead of the user's browser. Ad blockers, iOS ITP and cookie restrictions cause browser tracking to lose a significant share of conversions. The Google Tag Manager server container (server GTM) solves this problem, restoring accuracy for GA4 and advertising platform data. Request a quote and we reply within 24-48 hours.

Here we cover the basics of server-side tracking for businesses in Valencia and across Spain. We explain why browser tracking is failing today (ad blockers have become widespread, Safari and iOS cut cookie lifespan to 7 days through the ITP mechanism, and third-party cookies are disappearing) and how the Google Tag Manager server container (server GTM) restores data accuracy. This is the entry-level page: the core problem, how server-side tracking works, a comparison with browser tracking, the main setup steps and answers to common questions. Advanced scenarios (conversion modelling, Consent Mode v2, Meta CAPI integrations, Enhanced Conversions) are covered on a separate page. At the end: our "Ads & traffic" packages with real prices and related services.

## Why does browser tracking stop working?

### Three causes: ad blockers, iOS ITP and cookie restrictions

Browser tracking consists of JavaScript tags running in the visitor's browser. The problem is that the browser-controlled environment is becoming increasingly hostile to advertising scripts. Blocking extensions (uBlock Origin, AdBlock) block requests to Google Analytics, Meta Pixel and similar servers. Safari's Intelligent Tracking Prevention (ITP) mechanism limits first-party cookies set via JavaScript to just 7 days. As a result, iOS and Mac Safari users drop out of attribution within a week. The Google Tag Manager server container eliminates all three problems: requests leave from your server rather than the browser, cookies are set via HTTP headers and last up to 400 days.

1. Check the share of users with ad blockers in Google Analytics 4: compare GA4 sessions with server data (CRM, orders).
2. Assess the gap: if the difference exceeds 15-20%, browser tracking is losing conversions.
3. Choose a platform for the server container: Google Cloud Run, Stape.io or your own VPS.
4. Deploy the Google Tag Manager server container and configure a subdomain (e.g. metrics.yourdomain.com).
5. Configure the GTM client container to send events to your server endpoint instead of direct requests to GA4 and Meta.
6. Configure the GA4 server tag and forward data to Google Analytics. Verify in real-time mode.
7. Replace JavaScript cookies with first-party HTTP cookies with a long lifespan (up to 400 days).
8. Cross-check server GTM data against CRM and advertising platform data. The gap should drop to 5-8%.

## How does server-side tracking differ from browser tracking?

### The key difference is where the code runs and where requests originate

With browser tracking, JavaScript tags load in the visitor's browser and send requests directly to GA4, Meta Pixel and Google Ads servers. Any ad blocker or browser privacy policy can interrupt those requests. With server-side tracking, the browser sends a minimal request to your own domain, and the GTM server container then forwards the required data to GA4, Meta and other platforms. Ad blockers cannot see this exchange. The table below shows the key differences.

**Browser tracking vs server-side tracking**

| Parameter | Browser tracking | Server-side tracking |
| --- | --- | --- |
| Where code runs | In the user's browser | On your server |
| Ad blocker impact | Partially blocked | Not affected |
| Cookie lifespan (iOS Safari) | Up to 7 days (ITP) | Up to 400 days (HTTP cookie) |
| Data control | Limited | Full (on your domain) |
| Page load speed | Slowed by multiple tags | No impact (tags don't load in browser) |
| GDPR compliance | Depends on consent settings | Simplified: one container manages data |

## How does the Google Tag Manager server container work?

### Server GTM acts as an intermediary between the browser and advertising platforms

The GTM server container is deployed on a cloud server and receives events (page_view, purchase, lead) from your site via a dedicated client, the Google Analytics 4 Client or a Custom Client. The container processes these events and forwards them to the relevant platforms: GA4, Meta Conversions API, Google Ads, LinkedIn. Since all exchange happens between servers, ad blockers and browser restrictions are bypassed entirely. Google itself recommends server-side tagging as the solution for data accuracy in the face of growing ad blocker usage and tightening privacy policies.

### Expert opinion

> Browser-based tracking is becoming less reliable due to cookie restrictions and ad blockers; server-side tagging improves the accuracy and reliability of conversion data.
>
> Google, Server-side Google Tag Manager (documentation). Source: https://developers.google.com/tag-platform/tag-manager/server-side

## In short: why server-side tracking matters and where to start

Server-side tracking is the answer to a systemic problem: browser tracking loses a significant share of conversions due to ad blockers, iOS ITP and the disappearance of third-party cookies. The Google Tag Manager server container moves event collection from the browser to your server: ad blockers cannot see it, first-party cookies last up to 400 days, and GA4 and advertising platform data accuracy is restored. This page covers the basics: the problem and how server GTM works. Setup takes 2-4 weeks and includes container deployment, tag reconfiguration, testing and data verification. Request a quote and we will prepare your "Ads & traffic" plan and estimate within 24-48 hours.

## Frequently asked questions

### What is server-side tracking in simple terms?

It means sending data about user actions (page view, purchase, form submission) not through JavaScript in the browser but through your own server. Ad blockers and iOS restrictions cannot see this exchange, so data reaches GA4 and advertising platforms without losses.

### What is iOS ITP and how does it affect tracking?

ITP (Intelligent Tracking Prevention) is Safari's and iOS's built-in mechanism that limits first-party cookies set via JavaScript to a 7-day lifespan. This means a user who visited the site a week ago is treated as new on their next visit. Server HTTP cookies are not affected by ITP.

### Do I need server-side tracking if I run a small business?

If you spend more than 500-1000 € per month on advertising and see a gap between GA4 data and actual orders, server-side tracking pays off quickly. More accurate conversion data improves Google Ads algorithm training and reduces cost per lead.

### What is the Google Tag Manager server container?

It is a special version of GTM deployed on a cloud server (Google Cloud, AWS, VPS) that acts as an intermediary between the visitor's browser and advertising platforms. It contains clients (to receive events) and tags (to send data to GA4, Meta, Google Ads).

### How much does server-side tracking setup cost?

Cost depends on the scope: number of platforms (GA4, Meta, Google Ads, LinkedIn), container type and required integrations. Exact prices for "Ads & traffic" are in the packages block. Request a quote and we reply within 24-48 hours. Before quoting we look at the current tag setup, so the price reflects the real scope of work.

### How long does server GTM setup take?

Basic setup with GA4 and one advertising platform takes 2-3 weeks: server deployment, tag reconfiguration, testing and data verification. Full integration with multiple platforms takes 3-4 weeks. Data is verified before and after the switch, so the difference is shown in figures.

### Is server-side tracking compliant with GDPR?

Server-side tracking does not exempt you from GDPR requirements on its own: user consent is still required. But server GTM simplifies data management: you control which data is sent where, and it's easier to integrate Consent Mode v2 for correct consent handling.

### What happens to data if the server container is unavailable?

A correctly configured system uses the browser container as a fallback path. If the server endpoint is unavailable, events are sent directly from the browser. This reduces the risk of total data loss if the server has issues. Server availability is monitored, so we learn about a failure before data goes missing.

### Can Meta Pixel be connected through server GTM?

Yes. The server GTM container supports the Meta Conversions API (CAPI), the server-side equivalent of Meta Pixel. CAPI sends purchase, registration and other conversion events directly from the server to Meta, bypassing ad blockers and iOS restrictions, which improves ad attribution in Facebook and Instagram.

### In which languages do you run the server-side tracking setup project?

We run the project in Russian, Spanish and English, the three working languages of the SEO7.ES studio. We deliver documentation, instructions and analytics reports in your preferred language. Event and parameter names are also agreed in your team's language. Instructions for the team are written in the same language.