How to Set a Realistic Conversion Rate Target
Set a conversion rate target from your own baseline, not from an industry average. Take twelve months of weekly data for one segment, record the median and the normal spread, then add only what the specific fixes you intend to ship can plausibly deliver. State the result as a range with a review date and a named guardrail metric, usually revenue per visitor. A target built this way survives contact with a quiet week, and it tells you what to build rather than only what to hope for. A target copied from a benchmark tells you neither.
- An industry average describes other stores' traffic, so it cannot set your target.
- Your baseline needs its variance recorded, or normal noise reads as failure.
- Segment by device and by new against returning before setting any number.
- Size the target from the specific fixes planned, then discount for the ones that slip.
- Pair every target with a guardrail metric, or the rate can rise while revenue falls.
A conversion rate target is the rate you commit to reaching by a stated date, and most of them are set the wrong way round. The usual method is to find an industry average, notice you are below it, and adopt it as the goal. That produces a number with no route attached, which is why so many of them are quietly abandoned in month two. Last updated: September 2026.
Omniconvert has measured store performance across the CROBenchmark dataset of 7,000+ websites in 15+ industries, against 248+ audit criteria, over 13 years in eCommerce. The pattern that shows up most often in target setting is not ambition, it is arithmetic: teams commit to a figure without ever checking whether the changes they plan to make in the period could add up to it. The gap is rarely small, and it is always visible in advance.
This guide sets out how to build a target from your own numbers, why it should be a range rather than a point, and what to measure alongside it so a rise in rate cannot disguise a fall in revenue. If the prior question is what counts as good in the first place, start with a good conversion rate.
What is a realistic conversion rate target?
The definition does real work, because it excludes the two most common kinds of target. It excludes the borrowed average, which describes stores with different price points, different device mixes and different proportions of returning customers. And it excludes the round-number ambition, the target that is 3% because 3% sounds like a serious number, which has the same relationship to your store as a coin toss.
What survives is a target with a route. If you can point at the four changes that are meant to produce it and say roughly what each is worth, you have a target. If you cannot, you have a wish with a deadline, and the difference becomes obvious around week six.
Why borrowed benchmarks set the wrong conversion rate target
Consider two stores selling the same category at the same price. One gets 70% of its sessions from paid social on mobile, mostly first-time visitors. The other gets 55% from email and direct, mostly people who have bought before. The second will convert several times higher, and no amount of optimisation work at the first store closes that gap, because the gap is composition rather than quality.
This is why the average is useful for one thing and misleading for everything else. It answers whether your rate is unusual for your category, which is worth knowing. It does not answer what your rate could be, because it has no information about your traffic. Baymard Institute's long-running checkout research makes a related point from the other direction: measured cart abandonment sits around 70% across the industry, and the stores that improve on it do so by fixing named, observed problems in their own checkout rather than by aiming at the industry figure.
There is a second, quieter problem with the borrowed target. It gives no diagnosis. A target derived from your own funnel comes with the list of things that are wrong, because you had to find them in order to size it. A target lifted from a report arrives with nothing, so the team's first month goes on deciding what to do, which is the month the target assumed you were already doing it.
The Target Ladder: five rungs to a number you can defend
- Measure the baseline and its variance. Twelve months of weekly conversion rate, for one segment at a time. Record the median and the spread between the quietest and busiest weeks. Most stores discover their normal week-to-week swing is wider than the improvement they were about to promise, which is the single most useful thing this exercise produces.
- Segment before you set anything. Split by device, and by new against returning. A blended target can be hit by a change in device mix while both underlying rates stay flat, and it can be missed the same way. Two numbers are harder to fake and easier to act on.
- Size the fixes you intend to ship. Write down the specific changes planned for the period, attach an expected effect to each, then discount the total for the ones that will not ship on time. Some will not. A plan that assumes all four land is not a plan.
- State the target as a range, with a date. A band drawn from your own measured spread, with the review date fixed and the traffic mix it assumes written next to it. If acquisition changes the mix mid-quarter, the target moves and everyone knows why.
- Set the guardrail metric. Name what must not fall while the rate rises. Usually revenue per visitor, sometimes margin per visitor. Without it, a discount can deliver the target and cost you the quarter.
The ladder is ordered by dependency rather than by effort. The first rung is an afternoon with an analytics export and it determines whether anything above it means anything. The third rung is where most of the argument happens, because it is where a target stops being an aspiration and becomes a list of work somebody has to own.
How much movement is actually available
The table below sets out the situations we see most often and what each one can reasonably support in a quarter. The figures are relative improvements against the store's own baseline, not absolute percentage points, which is the distinction that causes the most confusion in target meetings.
| Store situation | Typical quarterly headroom | Where the movement comes from |
|---|---|---|
| Never audited, visible checkout friction | Large | A handful of named blockers, mostly in checkout and on mobile |
| Audited once, fixes partly shipped | Moderate | Completing the backlog that was already written |
| Running a structured test programme for a year | Small | Incremental wins, compounding rather than dramatic |
| Mature programme, mobile still untouched | Moderate, mobile only | The segment nobody set a separate target for |
| Traffic mix shifting toward paid and new visitors | Negative without work | Composition, not quality; the target must account for it |
| High returning-customer share, thin new-visitor experience | Moderate | First-visit trust and information gaps |
The last row of that table is the one worth reading twice. A store whose acquisition team is successfully buying more new visitors will see its blended conversion rate fall while nothing about the store gets worse. If the target was set without naming the traffic mix it assumed, that quarter ends in an argument nobody can win with the data they have.
What the target is for, and what it cannot do
It cannot replace the diagnosis. A number does not tell anyone what to change, and a team given a target without a list of findings will spend its first weeks producing one. Running the diagnosis first is the cheaper order, and where the funnel has not been examined at all, our companion guide on how to audit it covers the method step by step.
It cannot make work happen. Targets are frequently set on the assumption of engineering time that was never committed. If three of the four planned fixes need a developer and no developer is allocated, the target was decided by the roadmap, not by the CRO plan, and it will be missed for that reason and blamed on something else.
And it cannot protect revenue by itself. This is the failure that looks most like success. Conversion rate rises, the quarter is declared good, and revenue is flat because average order value fell by the amount the discount cost. Statista's eCommerce reporting shows how widely order values move between categories and periods, which is exactly why the rate cannot be read alone. Set revenue per visitor as the guardrail at the same moment you set the target, not after the first surprising month.
What to do this week
- Export twelve months of weekly conversion rate, split by device. Record the median and the gap between your quietest and busiest weeks. That gap is your noise floor and no target should be narrower than it.
- Run a free audit against your own funnel so the target has findings behind it. The CROBenchmark audit produces the list of named blockers that step three of the ladder needs.
- Write down the four fixes you will actually ship, with an owner and an expected effect for each, then cut the total by whatever proportion of your last quarter's plan did not land.
- State the target in one sentence: the range, the segment, the date, the traffic mix assumed, and the guardrail metric. If it does not fit in a sentence, it is not yet a target.
Where the findings need settling rather than debating, Omniconvert Explore is the CRO platform that pairs heatmaps, recordings and surveys with the A/B test that resolves them, averaging a 23.2% conversion uplift across 70,000+ experiments. Where the harder problem is deciding which finding to work first across a long backlog, Nexus by Omniconvert is an AI for eCommerce growth engine that unifies commerce data, ranks experiments by True Profit, and generates campaigns and creative you approve before they go live.
Which signal to believe when the two disagree is the prior question, answered in benchmarks vs your own baseline.
FAQ: conversion rate targets
Should I set my conversion rate target from an industry average?
No. An industry average describes a population of stores with different traffic mixes, price points, and proportions of returning customers, and none of those match yours. Use the average to sanity-check whether your baseline is unusual, then set the target from your own twelve-month baseline and the fixes you intend to ship.
How much can a conversion rate realistically improve in a quarter?
On a store with unresolved friction, a relative improvement in the low tens of percent is achievable in a quarter, and it comes from a handful of specific fixes rather than from general effort. On a store that has already run a serious programme for a year, the same quarter buys much less, because the cheap problems are gone. The honest answer depends on which of those two stores you are, and the audit tells you.
Why should the target be a range instead of a number?
Because weekly conversion rate varies for reasons nobody controls, and a single number turns normal variance into a monthly argument about whether the team is failing. A band drawn from your own measured spread absorbs that noise, so the review discusses the work rather than the weather.
Should mobile and desktop have separate targets?
Yes, and this is the most valuable split most stores are not making. Mobile and desktop convert at different rates for structural reasons, so a blended target can be hit by a shift in device mix while both underlying rates stay flat. Two targets make the improvement visible and stop traffic composition doing the work.
What should I do if we hit the target but revenue did not move?
Treat it as a failed quarter and check the guardrail. A conversion rate can rise because average order value fell, because a discount pulled forward demand, or because paid traffic was cut and the remaining visitors were better qualified. Revenue per visitor is the metric that catches all three, which is why it is set alongside the target rather than after it.
How often should the target be revisited?
Once a quarter, and on a date agreed before the quarter starts. Targets revised in the middle of a bad month tend to be revised downward for reasons that feel compelling at the time, and targets never revisited at all drift out of contact with the store as its traffic mix changes.
The bottom line
A conversion rate target is only as good as the arithmetic underneath it. Pull your own twelve months, record how much the number moves on its own, split it by device and by whether the visitor has bought before, and only then add what your named fixes can plausibly deliver. State the result as a range with a date, and set revenue per visitor beside it so a rise in rate cannot hide a fall in revenue. A target built that way tells the team what to build, survives a quiet week without a crisis meeting, and can be defended in a room where somebody asks where the number came from. A target copied from an industry average answers none of those, and the quarter it costs is not recoverable.