Skip to content
Metrics

What is Unique visitor?

A unique visitor is one distinct person visiting within a period, counted once no matter how many times they return. No tool can observe a person, so every visitor count is an estimate produced by deciding which requests belong to the same someone. The method chosen determines both how accurate the number is and how much privacy it costs.

Every method is a trade

MethodHow it recognises a visitorCost
First-party cookieAn identifier stored in the browserNeeds consent in the EU and UK; cleared and blocked often
FingerprintingA profile built from device characteristicsWorks without storage, and is exactly the tracking privacy law targets
Rotating salted hashA daily-rotating hash of request attributesNo storage, no consent needed, and no cross-day identity
Logged-in identityThe account the person signed intoPrecise, but only for signed-in traffic

sonex uses the third. A visitor is recognised for the day, and when the salt rotates the identity cannot be reconstructed even by us. The deliberate cost of that: someone who visits on Monday and again on Friday counts as two visitors, because the alternative is keeping a durable identifier for a person who never agreed to one.

Why totals never match across tools

Sum daily visitors across a month and you will get a much larger number than the monthly unique count, because a person who visited eight days is counted eight times in the first and once in the second. Both are correct; they answer different questions. Any comparison of “visitors” between two tools without matching the period and the method is comparing nothing.

Ad blockers add another gap. A tool blocked for 20% of an audience reports 20% fewer visitors, and reports it confidently.

Reading it well

Treat visitor counts as a consistent index rather than a headcount. Measured the same way over time, the direction and magnitude of change are reliable even when the absolute level is not. That is enough for nearly every decision a visitor count is used for.

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