Přeskočit na obsah
GETTING STARTED

Server-side GTM basics

What sGTM is, how it works, why you need it, and its advantages over client-side tracking.

10 min čtení Začátečník Aktualizováno 5.6.2026

What is server-side GTM?

Server-side Google Tag Manager (sGTM) is a way of measuring where data is first sent to your own server and only forwarded from there to analytics and advertising platforms (GA4, Meta, Google Ads, etc.).

Compared to traditional client-side GTM, where all scripts load in the visitor's browser, the server-side approach brings fundamental advantages.

Why isn't client-side tracking enough?

  • Ad-blockers block ~30-40% of data (uBlock, AdGuard, Brave)
  • ITP (Safari) limits cookies to 7 days → you lose returning visitors
  • Tracking Protection (Firefox, Edge) blocks third-party cookies
  • Slow loading — dozens of scripts slow the site down

How does server-side tracking work?

  1. 1
    The web browser sends data

    Client-side GTM sends the event to your subdomain (e.g. sgtm.yoursite.cz)

  2. 2
    Your server processes the data

    The sGTM container on the server receives, validates, and transforms the data

  3. 3
    The server sends it to the platforms

    Data is sent server-to-server to GA4, Meta, Google Ads, TikTok, Seznam, etc.

Benefits of server-side tracking

📈 More accurate data

Bypass ad-blockers and ITP → capture 20-40% more conversions

🔒 First-party cookies

Cookies set by the server last 2 years (vs. 7 days with ITP)

⚡ Faster site

Fewer scripts in the browser = faster page loads

🛡️ Better GDPR compliance

Full control over data, IP masking, EU servers

🎯 Better conversions

Meta Event Match Quality +20-30%, Google Ads Enhanced Conversions

🔧 Full control

Filtering, enrichment, and transformation of data on the server

Ready to start?

A server in the EU (Hetzner, Germany), automatic provisioning within 5 minutes, SSL, monitoring, and Czech support.

Try it free →
Pomohl vám tento článek?
✓ Děkujeme za zpětnou vazbu