About Tracking

Ad Platform Tracking

Meta Pixel + CAPI TikTok CAPI LinkedIn CAPI Snapchat CAPI Pinterest CAPI Quora Pixel Bing + UET Tag

Google Ecosystem

Google Ads Tracking GA4 Setup & Audit Google Tag Manager

Advanced Solutions

Server-Side Tracking Looker Studio Offline Conversion
Case Studies Blog Free Checklist Book Free Audit →
Home/Server-Side Tracking
Server-Side Tracking Setup

Browsers Block Your Pixels.
Your Server Never Will.

Ad blockers, iOS restrictions, and cookie expiry are silently killing 25–40% of your tracking data. Server-side tracking routes your events through your own server — so every conversion reaches GA4, Meta, Google Ads, and TikTok.

 2% data loss (vs 38%)  All 4 platforms  2-year cookie lifetime
Server-Side Event Pipeline
🌐
Your Store
🔗
GTM Server
All platforms
GA4
98%
Meta
97%
Google Ads
99%
TikTok
93%
The Problem

Every browser that blocks your pixel costs you a conversion you’ll never know about.

Three things are destroying your tracking data right now:

40%

Ad blockers silently block your pixels

uBlock Origin, Brave browser, and Safari’s built-in protection block client-side pixels. 25–40% of your users run some form of ad blocking. Every blocked pixel is a purchase your platforms never see.

7 days

Safari caps your cookies at 7 days

Safari’s Intelligent Tracking Prevention (ITP) limits 1st-party cookie lifetime to 7 days. Customers who visit and buy 2 weeks later aren’t attributed. Your GA4 direct traffic is actually lost attribution.

4 pixels

Managing 4 separate browser pixels is fragile

GA4, Meta, Google Ads, TikTok — four separate browser pixels means four separate points of failure. One bad update breaks everything. Server-side routes all four through one reliable pipeline.

Real Client Pipeline

Same site. Same traffic. Just the server now doing the tracking.

Here’s what a client’s event delivery looked like before and after server-side setup:

Before — Browser only, 38% data loss
Server-Side Event Monitor
⚠ Data loss detected
Est. Data Loss
38%
Browser blocking + cookie expiry
Event Source
Browser only
Pixel fires in browser — blockable
Cookie Lifetime
7 days
Safari ITP cap — attribution breaks
Browser-only pipeline (lossy)
🌐
Your Store

Browser pixel
GA4
61%
Meta
58%
Google Ads
64%
TikTok
22%
After — Server-side, 2% data loss
Server-Side Event Monitor
✓ All systems healthy
Est. Data Loss
2%
Server-side active — near zero loss
Event Source
Server + Browser
GTM Server Container active
Cookie Lifetime
2 years
1st-party server-side cookie
Server-side pipeline (complete)
🌐
Your Store

GTM Server
GA4
98%
Meta
97%
Google Ads
99%
TikTok
93%
PK
Priya K.
E-commerce / SaaS · United States
✓ Verified Client
Data Loss Rate
Before: ~36% lost
2%
↑ Near-zero data loss now
Attributed Revenue
Before: Missing ~$8k/mo
+31%
↑ Revenue finally visible in GA4

“We were running ads and thought our ROAS was 1.4x. After server-side setup, we realised we’d been attributing less than 65% of conversions. The real ROAS was 2.1x all along — we just couldn’t see it.”

How It Works

Your own server. Routing events to every platform reliably.

1
GTM Server Container Setup
We spin up a GTM Server Container on Google Cloud Run. This is your private event processing server — all conversion data flows through it, under your control.
2
Route All Platform Events
GA4, Meta CAPI, Google Ads, TikTok Events API — all configured as server-side destinations. One event from your store fans out to every platform correctly.
3
Server-Side Cookie Extension
We set your GA4 and attribution cookies server-side via HTTP response headers. Instead of 7-day Safari limit, your cookies last 2 years — full attribution window.
4
Monitor & Maintain
We configure event health monitoring so you can see data delivery rates across all platforms in real time. If anything drops, you know immediately.
Platform Coverage After Setup
GA4
Data delivery
98%
Meta CAPI
Match rate
97%
Google Ads
Conv. delivery
99%
TikTok
Match quality
93%
Additional Benefits
2-year server-side cookies (vs 7-day Safari)
Ad blocker bypass — events from your domain
Page load speed improves (fewer browser scripts)
GDPR-friendly — you control what data is sent
Server-Side FAQ

Questions about server-side tracking.

Client-side tracking fires from the visitor’s browser — which can be blocked by ad blockers, limited by Safari ITP, or fail due to connection issues. Server-side tracking fires from your own server after a conversion happens. Browsers can block your server as easily as they block themselves — they can’t.
Yes. Server-side tracking uses GTM’s Server Container, which works alongside your existing web container. If you don’t have GTM set up yet, we handle both — web GTM setup and server container setup — as part of the same engagement.
The GTM Server Container runs on Google Cloud Run, which is billed by usage. For most ecommerce stores under 50k monthly visits, the infrastructure cost is $5–$20/month. We help you size the container correctly and show you how to monitor costs in the Cloud Console.
Server-side tracking gives you MORE control, not less — you decide exactly what data leaves your server and goes to each platform. You can filter PII, honour consent signals from your CMP, and choose which events fire for opted-out users. It’s more privacy-friendly than client-side pixels if configured correctly.
All four major platforms benefit significantly: GA4 (purchase events recovered from blocked browsers), Meta CAPI (iOS purchase attribution recovered), Google Ads (Enhanced Conversions via server), and TikTok Events API (match rate improvement). Stores running ads on multiple platforms see the biggest total improvement.
🔗 Server-Side Specialist

Stop losing 38% of your data.
Start tracking from your server.

Free 20-minute audit. We check your current data loss rate and show you exactly what’s being missed before you pay anything.

Book Free Server-Side Audit →