Skip to content
Tracking mechanics

What is Server-side tracking?

Server-side tracking sends analytics events from your own server instead of from the visitor's browser. Because there is no third-party request from the page, ad blockers and browser protections do not intercept it. It changes where the data is collected, not what is collected — the privacy obligations follow the data, not the transport.

What it changes

Client-sideServer-side
Where the event originatesThe visitor’s browserYour server
Blocked by ad blockersOftenRarely
Sees client details (screen, referrer)YesOnly what you forward
Page weight costA script downloadNone
SetupA script tagReal engineering

The completeness gain is genuine. Client-side measurement misses every visitor running a blocker, and that share is large and not randomly distributed — it skews technical, which is exactly the audience many products care most about.

What it does not change

Two things people expect it to fix, and it does not:

Legal position. Privacy law follows the data. Collecting an IP address on your server rather than in the browser leaves it personal data. Setting an identifier from the server still counts as storage on the device under ePrivacy. Server-side collection used specifically to evade browser privacy controls has drawn regulator attention on exactly these grounds.

Data quality, automatically. The server sees requests, not people. Bots, prefetches and health checks all arrive as traffic and have to be filtered deliberately — filtering the browser used to do for you, badly but for free.

The honest positions

There are two defensible reasons to run server-side, and one that is not:

  • Completeness — you genuinely need to count visitors that client-side measurement misses. Legitimate.
  • Performance — no script on the page at all. Legitimate, and increasingly attractive.
  • Evading privacy controls — routing third-party trackers through your own domain so they survive protections the visitor deliberately enabled. That is the use regulators have criticised, and it is a different activity wearing the same name.
Questions

Frequently asked.

Cookies, install and pricing, answered. Still stuck? Ask us anything .

01 Can sonex show revenue next to my traffic?

Yes. Connect Stripe or Polar with a read-only key and sonex reads revenue straight from your payment provider, per website. Revenue then appears as a focusable series on the Overview chart and as its own report, beside the traffic that earned it. No tracked event is needed for it to work.

02 Does sonex use cookies?

No. sonex sets no cookies and needs no consent banner. It counts visits without cookies, fingerprinting, or any personal data, so it is GDPR, PECR and CCPA-ready by default.

03 How do I install sonex?

Add one script tag to your site's <head> with your website id. It is a single lightweight tracker — no build step and no SDK required.

04 Is sonex a Google Analytics alternative?

Yes. sonex gives you the reports that matter — visitors, pages, referrers, funnels, revenue and a world map — without surveilling your audience or drowning you in configuration.

05 How is sonex priced?

By monthly tracked events. Free covers 2k events, Pro is $20/mo for 200k events, and Business is $200/mo for 2M events with team seats.

See what your traffic actually earns.

Revenue beside the visitors that produced it. No cookies, no credit card, no consent banner.

Get started