Skip to content
01 · Start here

Introduction

What sonex counts, what it deliberately does not, and how the pieces fit together.

All pages

sonex answers one kind of question well: what is happening on my website, and did the thing I changed make money? It counts visits, shows them in realtime, breaks them down by page, source, device and country, lets you build funnels and goals on top, and — once you connect Stripe or Polar — plots revenue beside all of it (Revenue).

It does that without cookies, without fingerprinting, and without storing personal data. There is nothing to consent to, so there is no banner to add.

The three pieces

  1. The tracker. One script tag, roughly 3 kB, that you paste into your site’s <head>. It sends a small event when someone views a page, and whenever you ask it to. Core Web Vitals ride in a second file the tracker fetches only if you opt in (Install the tracker).
  2. Your website in sonex. Each site you measure has a website id. The tracker puts that id on every event so sonex knows where it belongs.
  3. The dashboard. Everything you read: Overview, Realtime, Events, Sessions, Compare, Reports, Tracking, Settings.

What you can ask it

QuestionWhere to look
Is traffic up or down?Overview, then Compare
Is anyone on my site right now?Realtime
Which pages and sources bring people in?Overview breakdown panels
Who are my visitors, roughly?Sessions
Did people do the thing I wanted?Events and Reports
Where do people drop out of a flow?Funnel in Reports
Did that campaign make money?Revenue

What it will not do

Being honest about the edges saves you time:

  • No per-person profiles. Sessions are counted in aggregate. You cannot open a visitor and read their life story, because sonex never collected one.
  • No cross-site tracking. A visitor on your site and the same visitor on someone else’s site are unrelated data.
  • No precise location. Geography is country, region and city, derived coarsely. Never a pin on a map.
  • No session replay. There are no recordings of visitor screens.

Words this documentation uses

  • Event. Anything the tracker sends. A pageview is an event; so is a signup you fire yourself.
  • View. One pageview event.
  • Session (or visit). One browsing sitting on your site.
  • Visitor. One recognised browser, counted once no matter how many times it comes back inside the range you are looking at.
  • Workspace. The account that owns websites and can hold teammates. Created for you during onboarding.

Concepts explains how those are counted, and why the numbers will not match Google Analytics.

Next: Quickstart, which takes you from nothing to your first recorded visit.

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