// case study
Recovering Lost Conversions with Server-Side Tracking
Lead technologist, end-to-end migration from client-side to server-side trackingMultiple mid-market e-commerce and lead-gen clients at a US digital agencyOngoing since 2024
Server-Side Google Tag Manager on GCPMeta Conversions APIGoogle Ads Enhanced Conversions APIGA4Advanced Consent Mode v2
The Problem
After iOS privacy restrictions and ad blocker adoption grew, clients were seeing 15 to 30 percent of their tracked conversions disappear from their ad platforms, even though the actual conversions were still happening. This directly hurt bidding models and made ROAS look worse than it was.
The Approach
- Deployed Server-Side GTM containers on GCP, one per client, with proper environment separation
- Routed first-party events from the browser to the sGTM container using a custom subdomain to bypass tracking prevention
- Integrated cross-platform Conversions APIs (Meta, Google, and others per client stack)
- Layered Advanced Consent Mode v2 on top so consent state is respected throughout the pipeline
- Built server-side data-quality checks: event volume drops, missing IDs, and consent-state anomalies
The Result
15 to 30 percent of previously lost conversions recovered, depending on client vertical and prior setup. Improved ROAS reporting accuracy and, in several cases, improved ad platform bidding.
// reflection
What I would do differently
Standardize the sGTM template earlier. My first three migrations each reinvented details that could have been templated. This is why I now maintain a shared sGTM template library.