Case File 01 · Services
Server-Side Tracking
Recover the 20-35% of conversions ad blockers, iOS, and Safari strip from your tracking. Server-side GTM, GA4, Google Ads, and Meta CAPI implemented in five business days.
TL;DR
Server-side tracking moves conversion data collection from the visitor's browser onto a server you control, recovering 20-35% of conversions that ad blockers and browser privacy controls strip from client-side tracking.
The Value
Why Server-Side Tracking Matters
Conversions become visible again
Server-side tracking captures the 20-35% of conversions Safari's ITP, iOS attribution caps, and ad blockers strip from client-side tracking before they leave the browser.
Bidding optimizes on real revenue
When Google Ads, Meta, and TikTok can see real conversions, their Smart Bidding algorithms shift spend toward campaigns that actually produce them. Most accounts see CPA drop 15-30% within 60 days on equivalent spend.
You own the data path
A server-side GTM container runs on your subdomain. You control retention, identifier hashing, and which platforms receive what. Browser policy changes don't break your stack.
Suspects of Interest
Who Needs Server-Side Tracking
Ecommerce, $30K+/mo ad spend
iOS and Safari are >25% of traffic. GA4 reports fewer purchases than your store does.
B2B with HubSpot or Salesforce mid-funnel
Long sales cycles. No closed-won data flows back to Google Ads or Meta for bidding.
Any account with >15% GA4-to-ad-platform variance
Your platforms can't agree on yesterday's conversion count, which means at least one is bidding on bad data.
Scope of Work
What's Included
- Server-side GTM container on your subdomain (Cloud Run, App Engine, or Stape.io)
- GA4, Google Ads Enhanced Conversions, Meta CAPI, and TikTok Events API connections
- Identity stitching with hashed email + user_id for cross-platform matching
- Consent Mode v2 wired for EU/GDPR traffic
- 48-hour parallel-run QA plus a reconciliation report showing actual recovery
- Source-of-truth documentation handed to your team
Fixed price · Five business days · Pay when complete
The Process
5-Day Process
Day 1
Audit
Map current stack. Reconcile 30 days of GA4 vs. ad-platform data. Gap report delivered.
Day 2
Container
Server-side GTM provisioned on tracking.yourdomain.com. GA4 client wired and tested.
Day 3
Platforms
Google Ads, Meta CAPI, and TikTok Events API connected. Deduplication keys configured.
Day 4
QA
Full-day parallel run. Client vs. server counts reconciled. Recovery percentage verified.
Day 5
Handoff
Walkthrough call. Documentation delivered. Edge cases noted. Keys handed over.
Evidence Locker
Tech Stack
- Google Tag Manager (Web)
- Server-Side GTM
- GA4 Measurement Protocol
- Google Ads Enhanced Conversions
- Meta Conversions API
- TikTok Events API
- Stape.io
- Google Cloud Run
- Consent Mode v2
From the Files
Result Snapshot
“Recovered 24% of conversions our client-side container was missing. Google Ads spend held steady. Reported conversions up 20% year-over-year the next quarter.”
Interrogation
Frequently Asked Questions
What is server-side tracking?
Server-side tracking is a method of collecting analytics and conversion data on a server you control before forwarding it to platforms like Google Analytics, Google Ads, and Meta. The visitor's browser fires a single first-party request to a container on your subdomain. The container enriches the data and routes it to each platform via their server-side API. Ad blockers and browser privacy controls can't strip data they never see.
How much conversion data does server-side tracking recover?
20-35% in most accounts. Recovery scales with iOS/Safari share and ad-block penetration in your audience. We forecast a recovery range during the discovery audit so the result is verifiable, not estimated. Verification happens in the parallel-run QA at the end of week one.
How long does server-side tracking setup take?
Five business days for standard ecommerce and lead-gen stacks: one day audit, two days container and platform configuration, one day QA, one day handoff. Custom CRMs or multi-domain architectures can add a few days, which we flag during discovery before quoting fixed price.
Do I need server-side tracking?
If you spend over $30K/month on Google Ads, Meta, or TikTok and the platforms depend on conversion signal to optimize, yes. You're almost certainly losing 20-35% of conversion signal to ad blockers and iOS, which means the platforms are bidding on incomplete data and your cost-per-acquisition is artificially high.
Does server-side tracking work with iOS 14+ and Safari?
Yes. That's a primary reason it exists. Server-side cookies are set on your own subdomain (first-party from the browser's perspective), which iOS and Safari don't truncate. Cookie lifetimes return to standard durations and events that would have died on the wire reach the server intact.
Ready to open your own case?
15 minutes is enough to size the recovery in your account and tell you whether server-side tracking is the right opening move.