Server-Side Tracking Isn't Optional Any More

Client-Side Is Dying

Traditional client-side tracking (JavaScript tags firing in the browser) faces compounding threats:

• • Ad blockers: 30-40% of users now run some form of ad/tracking blocker
• • Safari ITP: First-party cookies limited to 7 days, third-party blocked entirely
• • Firefox ETP: Similar restrictions to Safari, affecting ~8% of traffic
• • Brave, DuckDuckGo: Growing privacy-first browsers that block all tracking by default
• • Consent Mode: Users declining cookies removes tracking entirely under GDPR compliance

The cumulative effect: depending on your audience, 15-40% of conversions are invisible to Google Ads. Your reported ROAS is understated, your Smart Bidding is under-informed, and your campaign decisions are based on incomplete data.

The Scale of Data Loss

We audited 40+ ecommerce accounts in 2025. Average client-side tracking data loss:

• • Fashion/beauty: 18-25% (younger, mobile-heavy audience)
• • Electronics: 30-40% (tech-savvy audience with higher ad blocker usage)
• • Home/garden: 15-22% (older demographic, lower ad blocker adoption)
• • B2B ecommerce: 35-45% (tech-savvy buyers on corporate networks with network-level blocking)

If you're spending £50k/month on Google Ads and losing 25% of conversion data, Smart Bidding is making decisions on a £37.5k view of reality. The missing £12.5k in tracked value changes everything about optimal bid levels.

Impact on Smart Bidding

Smart Bidding (tCPA, tROAS, Maximise Conversion Value) relies on conversion data to learn. When data is missing:

• • The algorithm undervalues high-performing segments (because it can't see their conversions)
• • CPCs are set lower than optimal (because reported conversion value is understated)
• • You lose auctions to competitors with better tracking (they can afford to bid higher because they see more data)
• • Campaign learning periods take longer (fewer data points mean slower learning)

This is a competitive disadvantage. Brands with server-side tracking feed 20-30% more conversion data to their algorithms. That data advantage compounds over months.

Server-Side Explained

Server-side tracking works differently from client-side:

• • Client-side: Browser fires JavaScript tag → data sent from browser to Google
• • Server-side: Browser sends data to your server → your server sends data to Google

Because the data goes server-to-server, it bypasses ad blockers, browser restrictions, and cookie limitations. The server has the complete picture - it knows the order happened regardless of what the browser blocks.

This doesn't circumvent consent. You still respect user consent preferences. But for users who do consent to tracking, you capture 95-99% of their conversions instead of 60-80%.

Implementation Options

The main approaches:

• • Google Tag Manager Server Container: Google's native solution. Runs on Google Cloud. £50-150/month hosting. Best integration with Google Ads.
• • Stape.io: Managed GTM server-side hosting. Easier setup, £20-100/month. Good for Shopify.
• • Shopify native: Shopify's Customer Events API with server-side dispatch. Simplest for Shopify stores.
• • Custom API integration: Direct server-to-server via Google Ads Conversion Upload API. Most accurate but requires development resources.

Consent Mode Interaction

Server-side tracking and Consent Mode v2 work together. Consent Mode handles the legal framework (what you're allowed to track). Server-side tracking handles the technical framework (how you capture data that users consent to share).

With both in place, you maximise data capture within legal boundaries. Without server-side, even consenting users' data gets lost to technical blockers. That's data you have permission to use but can't capture.

Next Steps