Conversion rate in every direction: rate from visitors and conversions, conversions needed for a target rate, visitors needed for a target — plus revenue, a revenue-goal chain and the payoff from a small rate lift. Everything updates live and runs in your browser; the defaults are the worked example.
The maths: conversion rate = conversions ÷ visitors × 100. Revenue = conversions × AOV. Revenue per visitor = revenue ÷ visitors.
Rates are only comparable like-for-like: the same conversion definition, the same traffic mix and the same period. A blended rate hides the channels and pages that actually move.
—
Conversions needed = visitors × target rate. Use it to turn a traffic forecast into a sales or leads target.
Visitors needed = conversions ÷ rate. Use it to size the traffic a target actually requires at your real rate.
Each step feeds the next: revenue goal ÷ AOV gives the conversions, and conversions ÷ rate gives the traffic. Change any input and the whole chain re-plans itself.
Conversion rate in every direction — rate, conversions needed, visitors needed, revenue and the value of a small rate lift.
100% free · No sign-up · No daily limits · No watermarks · Processed in your browser — files never leave your device
Work out your conversion rate from visitors and conversions — then solve it backwards: the conversions a target rate demands, the visitors a target needs, the revenue those conversions bring, and what a small rate lift is worth at the same traffic.
A store gets 5,800 sessions and 145 orders. The rate is 145 ÷ 5,800 × 100 = 2.5%. At a $64 average order value, revenue is 145 × $64 = $9,280. Lifting the rate by half a point to 3.0% at the same 5,800 sessions gives 174 orders — 29 extra orders worth 29 × $64 = $1,856 more, with no extra traffic. Working backwards, 10,000 visitors at a 3.2% target rate needs 320 conversions, and a $9,280 revenue goal at $64 AOV and a 2.5% rate chains back to 145 conversions from 5,800 visitors.
Conversion rate = conversions × 100 ÷ visitors, computed in that order so clean figures stay exact. The backwards solvers invert it: conversions needed = visitors × target rate ÷ 100, and visitors needed = conversions ÷ (rate ÷ 100). Revenue = conversions × average order value, revenue per visitor = revenue ÷ visitors, and the revenue-goal chain divides the goal by the AOV to get conversions, then divides those by the rate to get visitors. The improvement scenario adds the chosen points to the current rate and re-prices the same visitor count — it never assumes extra traffic. Any division by zero (no visitors, a 0% rate, a $0 AOV) shows a dash instead of a number.
It depends entirely on what converts and where the traffic comes from. Ecommerce product pages often sit between 1% and 4%, warm email traffic can run far higher, and cold display traffic far lower. Your own trend — this month against last month on the same definition — is a far better benchmark than any published average.
Either works, as long as you are consistent: the rate is conversions divided by the denominator you chose. Sessions is the common analytics default; unique visitors suits signup and lead funnels where one person converting twice should count once. Mixing the two between periods makes the comparison meaningless.
Because it compounds on traffic you already have. On 5,800 visitors, half a point is 29 extra conversions — the same gain as buying roughly 1,160 extra visitors at the old 2.5% rate. Small rate gains on existing traffic are usually cheaper than equivalent traffic gains.
The average value of one conversion: for leads, the value of a won customer multiplied by your close rate — a $2,000 job you win one time in five makes each lead worth about $400. For signups, use expected revenue per signup over a sensible window. The revenue figures are only as good as this estimate.
A dash means the maths has no answer yet: a rate needs at least one visitor, visitors-needed needs a rate above 0%, and the revenue chain needs an AOV above $0. It is the calculator refusing to divide by zero rather than showing a wrong number.
Counts are shown rounded to whole visitors and conversions because you cannot have a fraction of an order, but the underlying maths keeps full precision — the revenue-goal chain, for example, divides the unrounded conversion count. A plan that needs 5,800.4 visitors really needs 5,801 people, so round targets up when you plan.
What is missing, broken, or could be better on this tool? Tell us — we read every suggestion.
✅ Thanks — your suggestion has been received. Suggestions like yours shape what we build next.