Server-side tracking is a method of collecting marketing conversion data on a server you control instead of in the visitor's browser. It recovers the 20-35% of conversions ad blockers, Safari ITP, and iOS attribution caps strip from client-side tracking, giving your ad platforms the signal they need to optimize bidding.
- What it recovers
- 20-35% of conversions stripped by ad blockers and browser privacy controls
- Where data is collected
- A first-party endpoint on your subdomain (e.g. tracking.yourdomain.com)
- Primary tools
- Server-side GTM, GA4, Google Ads Enhanced Conversions, Meta CAPI
- Setup time
- Five business days for standard ecommerce and lead-gen stacks
- Best fit
- Accounts spending $30K+/month on Google Ads, Meta, or TikTok
Server-Side Tracking at a Glance
What is server-side tracking?
Server-side tracking is the practice of collecting analytics events on a server you control before forwarding them to platforms like Google Analytics, Google Ads, and Meta. Three components define a server-side tracking setup:
- First-party endpoint on your subdomain, typically tracking.yourdomain.com
- Server-side container running on Google Cloud Run, App Engine, or a managed service like Stape.io
- Outbound API connections to GA4, Google Ads Enhanced Conversions, Meta CAPI, and TikTok Events API
How does server-side tracking work?
- The visitor's browser fires an event from a lightweight first-party tag, typically web GTM configured to forward to your server endpoint.
- The event reaches your server-side container on your subdomain.
- The container enriches the event (hashed email for Enhanced Conversions, server-resolved geo, custom parameters).
- The container forwards the enriched event to each downstream platform via its server-side API.
Server-side tracking vs client-side tracking
| Aspect | Client-Side | Server-Side |
|---|---|---|
| Where events fire from | Visitor's browser | Your server |
| Affected by ad blockers | Yes | No |
| Affected by Safari ITP | Yes | Minimally |
| Conversion recovery | Baseline | +20-35% |
| Setup time | Hours | Five business days |
Who needs server-side tracking?
- Ecommerce running $30K+/month in paid acquisition where iOS and Safari are a meaningful share of traffic.
- B2B with HubSpot or Salesforce mid-funnel where closed-won revenue lives in the CRM and ad platforms cannot see it.
- Any account with >15% GA4-to-ad-platform variance.If your platforms disagree on yesterday's conversions, at least one is bidding on bad data.
How to set up server-side tracking
A standard server-side tracking implementation runs five business days end to end:
- Audit. Reconcile 30 days of GA4 against ad-platform reporting to size the recovery gap.
- Container. Provision a server-side GTM container on your subdomain (tracking.yourdomain.com), hosted on Google Cloud Run, App Engine, or Stape.io.
- Platforms. Connect GA4 Measurement Protocol, Google Ads Enhanced Conversions, Meta CAPI, and TikTok Events API.
- QA. Run a 48-hour parallel between client-side and server-side. Verify the recovery percentage matches the audit forecast.
- Handoff. Deliver documentation, edge cases, and source access to the in-house team.
DataSolvd installs server-side tracking on a fixed-price five-business-day engagement. Read the full service description.
What does server-side tracking do that client-side tracking can't?
Server-side tracking captures conversion events that ad blockers, Safari's Intelligent Tracking Prevention, and iOS attribution limits strip from client-side tracking. Because events fire from a first-party server you control instead of a third-party tag in the browser, browser privacy controls cannot block or truncate them. Most accounts recover 20-35% of conversions previously invisible to Google Ads and Meta.
Is server-side tracking the same as server-side GTM?
Server-side GTM is the most common implementation of server-side tracking, but the terms are not identical. Server-side tracking is the general practice of collecting analytics data on a server before forwarding it. Server-side GTM is Google's specific product for running that server. Other implementations include Stape.io managed containers and direct API integrations.
Do I still need client-side tracking if I have server-side tracking?
Yes. Most accounts run both. Client-side handles user-experience events like clicks and scroll depth. Server-side handles conversions, identity stitching, and any event that needs to survive ad blockers and privacy controls. The two are complementary, not substitutes.
Ready to size the recovery in your account?
15 minutes is enough to forecast what server-side tracking would recover and what a five-day implementation would look like.