Implement Server-Side Tracking

Track users accurately, even when ad blockers are running.

Track users accurately even with ad blockers. Here’s how.

Why Server-Side

You’re losing data. Not because your tracking is misconfigured, but because browsers and ad blockers are actively preventing collection.

Client-side tracking fails when:

• User has ad blocker (~Many users)
• Browser blocks third-party cookies
• ITP/ETP limits cookie lifetime

Server-side tracking sends data from your server, not the user’s browser.

How It Works

Traditional:
Browser → gtag.js → Google Analytics

Server-side:
Browser → Your Server → Google Analytics

Ad blockers block requests to google-analytics.com. They don’t block requests to your own domain.

Setup Options

Pick the option that matches your team’s technical ability. Option 1 gives the most control. Option 2 is the fastest path to production. Option 3 is for teams that want to skip GTM entirely.

Option 1: Google Tag Manager Server-Side

Google’s official solution. Requires:

• Google Cloud Platform account
• Cloud Run container (starts at ~$30/month)

Setup: GTM Server-Side docs

Option 2: Stape.io

Managed GTM server-side hosting:

• Free tier: 500K requests/month
• Handles setup complexity
• Custom domain included

Setup: Stape GTM guide

Option 3: Custom Implementation

Send events from your backend:

Note: Replace G-XXXXXXXXXX with your GA4 Measurement ID and YOUR_API_SECRET with your Measurement Protocol API secret (found in GA4 Admin → Data Streams → Measurement Protocol API secrets).

// Node.js example
async function trackEvent(userId, eventName, params) {
 await fetch('https://www.google-analytics.com/mp/collect?measurement_id=G-XXXXXXXXXX&api_secret=YOUR_API_SECRET', {
 method: 'POST',
 body: JSON.stringify({
 client_id: userId,
 events: [{ name: eventName, params }]
 }),
 headers: {
 'Content-Type': 'application/json'
 }
 });
}

What to Track Server-Side

Not everything needs server-side tracking. Move your high-value events — the ones ad blockers are costing you — and leave the rest client-side.

• Conversions – Purchases, signups (most important)
• Form submissions – After server validates
• API events – Webhook triggers

Keep client-side for:

• Page views
• Scroll depth
• Time on page

First-Party Data

Server-side tracking lets you attach data you already have — CRM records, purchase history, account status — to analytics events before they reach GA4. This data never touches the browser, so it stays private and can’t be blocked.

• Customer lifetime value
• Subscription status
• Purchase history

This data never goes to the browser.

Privacy Considerations

Server-side doesn’t bypass consent requirements:

• Still need consent for EU visitors
• Still need to honor opt-outs

Just more reliable tracking for consenting users.

Verify It’s Working

The simplest test: simulate the conditions that break client-side tracking and check if your data still arrives.

1. Enable ad blocker
2. Trigger a conversion
3. Check GA4 Realtime report

Event should still appear.

Validate Server-Side Data Matches Client-Side

After setup, compare server-side event counts against client-side for the same period. Some discrepancy is normal — you should see more events server-side. That’s the whole point. If server-side shows fewer, something is misconfigured.

Start with Stape.io free tier. Set up purchase and conversion tracking first — that’s where ad blocker losses cost you the most.

Sources

• Google – Server-Side Tag Manager
• Google – GA4 Developer Documentation
• MDN – Beacon API (Client-Side Tracking Reference)