Data you trust
Server-side events are not blocked by ad blockers or browser privacy settings. You see what actually happened, not what the browser was allowed to report.
Service / Server-Side Tracking
Stop losing data. Own your measurement.
Browser-based tracking is losing ground — ad blockers, iOS privacy changes, and cookie restrictions mean a significant share of your conversions are invisible to your platforms. Server-side GTM moves your data collection server-first, so you see the full picture again.
GA4 Server-Side
Google Ads
Meta CAPI
BigQuery
First-Party Data
Cloud Run
GA4 Server-Side
Google Ads
Meta CAPI
BigQuery
First-Party Data
Cloud Run
How It Works
The data route changes. Everything else stays the same.
Your existing Google Tag Manager container and website stay in place. What changes is where the data goes after the browser fires a tag — instead of sending directly to Google or Meta, it routes through a server endpoint you control, which then forwards to each platform. You keep the same tags and triggers. You gain ownership, reliability, and control.
The Data Flow
Browser to server to platform.
1
Browser fires
Your Web GTM container fires a tag as it always has — page view, purchase, form submit. Nothing changes for the visitor.
2
Your server receives
The event hits a first-party endpoint on your own subdomain (e.g. data.yoursite.com), hosted on Google Cloud Run. It looks like your own server to any browser or ad blocker.
3
Platforms receive clean data
Your GTM Server container enriches and forwards the event to GA4, Google Ads, Meta CAPI, or BigQuery — from a trusted server IP, not a blocked browser.
Why It Matters
More data confidence, less platform dependency.
When your conversions are tracked server-side, you regain the signal that browsers are losing. Ad platforms bid on what they can see — if they only see 60% of your conversions, they optimise for the wrong audience. Server-side tracking restores visibility across Google Ads, Meta, and your own analytics simultaneously.
Better ad performance
Google Ads and Meta use conversion signals to optimise campaigns. More complete data means better audience modelling, lower CPAs, and smarter bidding.
One source of truth
GA4, Google Ads, and Meta CAPI all receive events from the same server-side source, eliminating the discrepancies between platform-reported numbers.
Future-proof
As third-party cookies continue to disappear, first-party server-side tracking becomes the standard, not the exception. Get ahead of it now.
Implementation
A phased rollout — validate before you scale.
Phase 1
GA4 Foundation
Set up GTM Server on Google Cloud Run, map your existing Web GTM events to server-side, configure GA4 server-side tag, run dual-tagging validation, and decommission client-side GA4 once confirmed.
Phase 2
Ads & Platforms
Add Google Ads Enhanced Conversions and Meta Conversions API (CAPI) via the server container. Deduplication configured so platforms do not double-count browser and server events.
Phase 3
BigQuery & Reporting
Stream events to BigQuery for raw-level analysis. Build dashboards on clean, server-confirmed data. Optional: serve your own analytics scripts as first-party to further reduce blocking.
What Is Included
End-to-end — not just the setup.
GTM Server provisioning
Google Cloud Run deployment, subdomain DNS mapping, SSL, budget alerts, and monitoring.
Web GTM audit & migration
Full audit of your existing container, event mapping, and migration of priority tags to server-side.
GA4 server-side configuration
Server-side GA4 tag, event enrichment, user ID mapping, and GA4 DebugView validation.
QA & handover documentation
Systematic QA across DNS, browser network, server preview, GA4 Realtime, and duplicate checks. Full handover runbook so your team can manage it ongoing.
Contact
Not sure if server-side tracking is right for you?
Send me a note with your setup — current tag manager, analytics stack, ad platforms — and I will give you an honest assessment of what you stand to gain and what it would take. No obligation.