Server-side tracking: the only setup guide you'll need

If you've ever opened your Google Ads dashboard and wondered why "Conversions" looks lower than what your sales CRM is reporting — this article is for you. The gap is almost always tracking, not actual sales loss.

By the end of this guide you'll understand: what server-side tracking is, why it matters in 2026, exactly how to set it up, and what it'll cost.

What is server-side tracking?

Traditionally, tracking pixels (GA4, Facebook Pixel, Google Ads tag) load in the user's browser and send data directly to the platform. This is client-side tracking.

Problems with client-side:

• Ad blockers strip the pixels — you lose 20-30% of data immediately.
• iOS Safari's ITP wipes cookies after 7 days.
• Slow page load — every pixel is a network request.
• Browsers and OS updates keep tightening the screws.

Server-side tracking moves the data flow to your own server. The browser sends one event to a server you control (or rent), and that server forwards the event to GA4, Meta, Google Ads, etc. Result: you bypass ad blockers, you're not affected by browser updates, and you control exactly what data gets passed.

Most clients we migrate to server-side see a 25-40% lift in tracked conversions within 14 days. The conversions were always there — you just couldn't see them.

Why this matters for your ads

Smart bidding (Maximise Conversions, tCPA, tROAS) optimises based on the conversion data you feed it. If 30% of your conversions are missing, the algorithm is making decisions on partial information. That means:

• It under-bids on audiences that actually convert.
• Your reported CPA looks higher than reality.
• Your scaling decisions are based on bad data.

Fix the tracking and your bids get smarter — automatically. We've seen accounts gain 15-25% efficiency from server-side tracking alone, before changing anything else.

The components you need

For a full server-side setup, you'll need:

1. Google Tag Manager (GTM) Web container. Already on most sites.
2. GTM Server container. The new bit. Hosted on Google Cloud, your own server, or a managed service.
3. Custom subdomain. Like data.yoursite.com — first-party domain that ad blockers don't recognise.
4. GA4 with server-side configuration.
5. Meta Conversions API (CAPI). Server-side equivalent of the Pixel.
6. Google Ads Enhanced Conversions for Web.

Step-by-step setup

Step 1: Spin up a server-side GTM container

In your existing GTM account, create a new container, choose Server as the type. Google will guide you through provisioning either on Google Cloud (recommended for most), or you can self-host or use a managed provider like Stape.io (cheapest path under ₹2,000/month).

Step 2: Set up your custom subdomain

This is the critical bit that bypasses ad blockers. Point a subdomain (e.g., track.yourdomain.com) to your server-side GTM endpoint via your DNS. Now your tracking calls go to your domain — not to Google's.

Step 3: Reroute GA4 client-side to your server-side container

In your existing web GTM container, change your GA4 Configuration tag's Server Container URL to your custom subdomain. Now all GA4 events go through your server instead of directly to Google.

Step 4: Add a GA4 client & tag in the server container

In the server container: add a "GA4" client (default) and a "GA4 Tag" that forwards events to GA4. Test in Preview Mode — events should flow through.

Step 5: Add Meta CAPI

Install the Meta Conversions API tag template (community-built, free) in your server container. You'll need your Pixel ID and a Meta CAPI access token (generated in Meta Events Manager). Set up event parameters to match your existing Pixel events.

Pro tip: keep both Pixel (client-side) and CAPI (server-side) running in parallel. Meta deduplicates them via the event_id parameter — give them the same event_id and Meta picks the better one.

Step 6: Add Google Ads Enhanced Conversions

In your server container, add the Google Ads Conversion Tracking tag and enable Enhanced Conversions. Pass hashed user data (email, phone) — Google uses this for first-party matching.

Step 7: Test relentlessly

Use GTM Preview, Tag Assistant, Meta Events Manager Test Events, and Google Ads conversion diagnostics. Verify every conversion is firing once per platform per event. Watch for duplicates and missing data.

What it costs

• Google Cloud hosting: ₹3,000-8,000/month for most sites (under 1M events/month).
• Stape.io managed: ₹1,500-4,000/month — easiest path.
• Setup time: 12-20 hours for someone who's done it before. 30-50 hours if it's your first time.
• Maintenance: 1-2 hours per month, plus updates when platforms change requirements.

For most accounts spending ₹2L+/month on ads, server-side tracking pays for itself in 14-30 days through better bidding alone.

Common mistakes to avoid

• Sending raw PII without hashing. Google and Meta require SHA-256 hashing on user data. Don't ship plaintext emails.
• Forgetting the consent layer. If you're in the EU/UK, you still need cookie consent — server-side doesn't bypass GDPR.
• Not deduplicating Pixel + CAPI. Without matching event_ids, you double-count conversions.
• Skipping the test phase. Server-side errors are silent — pages still load, but no data flows. Test obsessively.

What about Cloudflare Workers, Stape, etc.?

You don't have to use Google's server container. Alternatives:

• Stape.io — managed Google sGTM at lower cost. Good for most.
• Cloudflare Workers — DIY route, very cheap, but more engineering work.
• Segment + Function — if you're already on Segment, route conversions server-side via Functions.
• Custom Node/Python service — for in-house engineering teams who want full control.

The bottom line

Server-side tracking isn't optional any more. It's the difference between making bidding decisions on 70% of your data versus 95-98% of your data. The brands that set this up in 2024-25 have a measurable performance advantage today.

If you're not technical and this all sounds like a lot — it is. It's the kind of thing that takes a week to set up properly and then quietly powers everything for years. Worth doing once, doing right.

Want us to set this up for you? Server-side tracking is included by default on our Scale plan, and available as a one-time engagement. Get in touch →