Revenue Per Visitor: Formula, Examples, Targets

Revenue per visitor (RPV) is the revenue you earned in a period divided by the number of unique visitors in that period. If 8,000 people visited your site in September and you took $1,600 in payments, your RPV is $0.20. It's the one metric that combines how many visitors convert, how much they pay and how good your traffic is into a single number — which is why it's the metric we think indie hackers should watch instead of visitors.

How do you calculate revenue per visitor?

The formula is simple. The decisions inside it are what make the number trustworthy.

Revenue per visitor = Revenue in period ÷ Unique visitors in period

Equivalent form:
Revenue per visitor = Visitor-to-customer conversion rate × Revenue per customer

Example: 8,000 visitors, 40 customers, $1,600 revenue
  RPV = $1,600 ÷ 8,000 = $0.20
  Check: 0.5% conversion × $40 per customer = $0.20

1. 1.Pick the period. A month is the usual choice; for products with a long time-to-buy, use 90 days so slow converters land in the same window as the visits that produced them.
2. 2.Count unique visitors, not sessions or pageviews. Sessions double-count returning buyers and make RPV look lower than it is.
3. 3.Exclude bots. Automated visits inflate the denominator without ever paying; Imperva estimates that more than half of all web traffic in 2025 was automated, and the share that runs your analytics script still dilutes RPV. See bot traffic in analytics.
4. 4.Decide what revenue means: gross payments, or net of refunds. Net is more honest; use it consistently.
5. 5.Convert currencies to one reporting currency, or compute RPV per currency.
6. 6.Divide, then segment by channel, landing page, country and device — the overall number is only the starting point.

The revenue per visitor calculator does the arithmetic, and the traffic-to-revenue calculator runs it backwards: how many visitors you need for a revenue goal at your current RPV.

Why should indie hackers watch revenue per visitor instead of traffic?

Because traffic is the input you're tempted to chase and RPV is the efficiency you actually control. Doubling traffic is hard, expensive and often temporary. Doubling RPV — by converting a higher share, raising prices, or getting more of your traffic from channels whose visitors buy — is frequently easier, and it compounds with every future visitor.

RPV also keeps you honest about channels. A Hacker News front page can send 15,000 visitors and $150 in revenue ($0.01 per visitor). A comparison page might send 900 visitors a month and $540 ($0.60 per visitor). Measured in traffic, the first one looks 16 times better. Measured in RPV, the second is 60 times better per visitor — and it repeats every month. Which marketing channels bring paying customers works through a full channel review built on this idea.

How do you calculate revenue per visitor for a SaaS?

Subscription revenue arrives over months, so “revenue in the period” undercounts what a visitor is worth. Track two versions.

Here's lifetime RPV with real-world inputs. Say your plan is $29/month and your monthly customer churn is 6.5% — the median for SaaS companies under $300k ARR in ChartMogul's benchmark data. A simple LTV estimate is ARPU ÷ churn: $29 ÷ 0.065 ≈ $446. If 0.6% of visitors become paying customers, each visitor is worth about $2.68 over their lifetime, even though first-payment RPV is only $0.17. That gap is why a sponsorship that looks unprofitable on first payments can be clearly profitable on lifetime value. Run your own numbers with the LTV calculator and the churn rate calculator.

What is a good revenue per visitor?

There's no universal benchmark worth trusting, because RPV depends on price more than anything. A $9 tool and a $299 tool with the same conversion rate have RPVs 33 times apart. Published e-commerce RPV benchmarks don't transfer to SaaS, and SaaS benchmarks rarely separate first-payment from lifetime revenue. Useful targets are relative:

• Against your own past: RPV this quarter versus last quarter, at a similar traffic mix.
• Against your own channels: every channel's RPV versus your site-wide average. Above average deserves more effort; far below average needs a fix or a smaller share of your time.
• Against cost: lifetime RPV should comfortably exceed what you pay per visitor on any paid channel, with margin for the uncertainty in your LTV estimate.

As a rough sanity check for self-serve SaaS: with typical visitor-to-signup rates of 1–5% and trial-to-paid rates that vary from under 10% to around 50% depending on whether a card is required, visitor-to-paid usually lands between 0.1% and 1.5%. Multiply by your monthly price for an order-of-magnitude first-month RPV. If yours is far below that range, look for bots in the denominator or a leak in your SaaS conversion funnel.

How do you use revenue per visitor to compare pages and channels?

Segmenting is where RPV earns its place. Here's a 90-day example for a $19–$49/month SaaS, segmented by landing page (the first page each visitor saw).

The tutorial is the biggest traffic page and the lowest-value one per visitor. That doesn't mean delete it — it builds authority and links — but it does mean adding a clear path from it to the comparison and pricing pages is worth more than writing another tutorial. The comparison page, meanwhile, earns as much per visitor as pricing itself; more pages like it is the obvious next bet. You can't see any of this from a pageview report.

How do you increase revenue per visitor?

Pricing is the most under-used lever for indie products. A 30% price increase that costs you 10% of conversions raises RPV by about 17% (1.3 × 0.9 = 1.17) — and that applies to every future visitor without any extra traffic. Test it on new customers only and watch RPV, not signups.

What are the most common revenue per visitor mistakes?

• Judging a channel before its customers have had time to pay. If your median days-to-convert is 12, a campaign that started last week has an artificially low RPV. Use a window of at least two to three times your median conversion time.
• Crediting revenue to the wrong visit. Period RPV puts renewals from customers acquired a year ago next to this month's new visitors. For channel and page comparisons, credit each payment to the visitor's first touch instead — first-touch vs last-touch attribution explains the difference.
• Letting one big customer decide. A single annual team plan can make a small channel look like a goldmine. Under about 10 customers per segment, read customer counts alongside RPV.
• Comparing across price changes. If you raised prices in July, RPV before and after aren't comparable without noting it.
• Forgetting refunds and chargebacks. A channel that brings impulse buyers who refund within a week has a lower real RPV than its gross number.

Where do you get revenue per visitor from?

You need two things joined: unique visitors per segment from analytics, and revenue per segment from payments. A spreadsheet works — export visitors by source and landing page, export payments from Stripe, and match them through whatever you stored at checkout. It's tedious but honest.

Analytics tools with revenue attribution do the join for you. In VisitTrack, the Revenue view shows revenue per visitor next to total revenue, conversions, average order value and days to convert, and breaks revenue down by referrer, campaign and landing page; humans only by default. The setup is a webhook and one field passed at checkout — see how to track revenue by traffic source and the revenue docs. For how this works for small teams, the indie hackers use case has a walkthrough.