Skip to content
Revenue and attribution

What is Revenue per visitor?

Revenue per visitor (RPV) is total revenue divided by the number of visitors over the same period. It answers what an average visit is worth. Because it is a per-head figure rather than a total, it lets you compare a channel sending 200 visits with one sending 20,000 without the larger one automatically winning.

The formula

Revenue per visitor = revenue in period ÷ visitors in period

It decomposes cleanly into two levers, which is what makes it useful rather than merely descriptive:

Revenue per visitor = conversion rate × average order value

A falling RPV is therefore always one of two problems. Either fewer visitors are buying, or the ones who buy are spending less. The decomposition tells you which before you start guessing.

Why it beats raw revenue for comparing channels

Total revenue rewards size. A channel that sends ten times the traffic will usually earn more money in absolute terms even if every individual visit is worth a fraction as much. Ranking by totals therefore tells you where your traffic already is, not where it is worth going next.

Revenue per visitor normalises that away. It is the number that reveals the small newsletter outperforming the large aggregator, and it is the one to look at before deciding to spend more on a channel — because spending more buys you additional visits at roughly the current per-visit value, not at the blended average.

Cautions

  • Small samples lie. On a channel with 40 visits and one sale, RPV is a single customer’s order size wearing a statistic’s clothing. Give it enough volume before acting on it.
  • Pick one denominator and keep it. Visitors, sessions and pageviews all produce a defensible “per visit” number and none of them are comparable to each other. Sessions inflate the count against visitors; pageviews inflate it dramatically.
  • Delayed revenue distorts the window. If people buy two weeks after first arriving, this month’s revenue belongs partly to last month’s visitors. Widen the period until the lag is small relative to it.
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