Guide · Revenue attribution

Server-Side vs Client-Side Tracking: What Each One Misses

Browser scripts see visits but miss blocked users and off-site payments. Server events see payments but not where visitors came from. How to combine them.

· 3 min read

Source lines meeting at a revenue target

"Server-side tracking" has become a buzzword, sold as the fix for ad blockers and lost conversions. It fixes some things and breaks others. Here is what each side sees, and the combination that works for revenue analytics.

Client-side tracking (in the browser)

A script on your page sends events as people browse.

Sees well: where the visit came from (referrer, UTM tags), which pages were viewed, clicks, scroll and goals, screen size and device.

Misses:

  • Visitors whose browser blocks the script (how many that can be)
  • Visitors who decline consent, if the script waits for it
  • Anything that happens off your site: payments on a provider's checkout page, renewals, refunds

Server-side tracking

Your server (or your payment provider's webhook) sends events directly.

Sees well: every payment, renewal, refund and dispute. Every signup your backend creates. Nothing is blocked, because no browser is involved.

Misses:

  • Where the person came from, unless the browser told you earlier
  • What they looked at before acting
  • Anyone who never reached your server

The combination that works

Use each side for what it sees best, and join them with an id:

  1. 1Browser scriptRecords the visit's source and a visitor id
  2. 2CheckoutThe visitor id travels into the payment's metadata
  3. 3Provider webhook (server side)Reports the payment, renewals and refunds
  4. 4JoinRevenue is credited to the visit's source
Client side and server side together

That is how DataFair works: a light script for visits and sources, and payment provider webhooks for money. Payments are complete even when the script was blocked. What changes is whether they can be matched to a source, and blocked visits show up honestly as unattributed. How the join works.

Proxying the script

Some teams serve their analytics script from their own domain so fewer blockers recognise it. DataFair supports sending events through your own proxy with the data-api option. It's a reasonable step, but respect the visitor's choice: DataFair also honours Global Privacy Control, and its cookieless mode stores nothing in the browser.

What "server-side" doesn't fix

  • Lost referrers. A server can't know a click came from a podcast app if the browser never said.
  • Consent rules. Moving collection to a server doesn't remove the need for a lawful basis.
  • Bad joins. If the visitor id never reaches checkout, server-side payments stay unattributed. Why GA4 often loses Stripe sales is the classic case.
Visitors and revenue together in DataFair
Script-tracked visitors and webhook-tracked revenue on one chart in the DataFair demo (sample data).

Related guide: Revenue attribution for every payment provider.

Questions

Is server-side tracking better than client-side?
Neither is better on its own. Server-side is complete for payments and signups; client-side knows where visitors came from. Revenue attribution needs both.
Does server-side tracking bypass ad blockers?
For events your server sends, yes, because no browser is involved. The visit's source still comes from the browser.
Do I need Google Tag Manager server-side for this?
No. Payment providers already send server-side events through webhooks. A tool that receives them, such as DataFair, does the joining for you.

Related