ROAS Calculator
The formula
What the roas tells you
Return on ad spend — revenue credited per media dollar; the real-time scoreboard of paid channels, best read against a margin-derived break-even.
Calculation: ROAS = attributed revenue ÷ ad spend. Enter your inputs and every substitution is shown below the result.
Reading the result
A 3× ROAS at 25% margin loses money; 1.6× at 70% margin profits — the break-even column is the number platforms omit from every dashboard.
Rules of thumb: Ecommerce 2–4× typical, profitable above break-even; app installs judged on post-install event ROAS
Limitations and best practice
Blended ROAS includes organic and repeat buyers that arrive anyway; incremental ROAS from holdouts is usually 30–60% lower — plan budgets on the incremental figure.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Why not just target the highest ROAS?
Does ROAS count returns and refunds?
Source & methodology
Paid-media standard (break-even ROAS = 1/margin).
How ROAS works — and what your result really means
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. There are plenty of pages about ROAS; almost none of them show the working. This one does: the formula, every input, a fully computed example, and a sensitivity analysis calculated live from this engine’s own defaults.
Most confusion about ROAS comes from mixing up the input you control with the input you merely observe. The formula treats them identically, but your decisions should not: one deserves measurement, the other deserves a defensible estimate.
The discipline ROAS enforces is naming your assumptions. Ad spend ($) and Ad-attributed revenue ($) are guesses dressed as inputs; once they are on paper, the argument stops being about vibes and starts being about whether the guesses are defensible — which is how good decisions get made.
What makes a calculation page trustworthy is that its copy is derived from its own arithmetic: here ROAS = 6.97 : 1, recomputed every time a field changes, and the sensitivity section ranks the inputs that move the result — Ad spend first, at ≈11.1 % of the headline for a ten-percent error either way in that input — which is the thread the rest of this guide pulls on.
Inside the ROAS calculation: formula and every input
The engine implements a single stated model: ROAS = attributed revenue ÷ ad spend. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Ad spend ($) (example value 9,000) is a measured number in the unit named by the label; the formula does not convert for you. Use the figure exactly as the source document states it, not a rounded memory of it — an omitted line is the classic silent error.
Ad-attributed revenue ($) (example value 62,750) is a measured number in the unit named by the label; the formula does not convert for you. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
Gross margin (%) (example value 69) is a quantity rather than a category — precision here is cheap and worth having. Check the convention first: if the source says “6.5 % per year”, type 6.5 and let the formula do the rest.
A fully worked ROAS example
Abstract formulas are hard to trust, so here is the complete substitution using the default inputs, written the way an examiner would want it. Starting figures: Ad spend ($), Ad-attributed revenue ($), Gross margin (%). The computed ROAS comes out at 6.97 : 1, which the interpretation band labels “Above the 1.45× break-even at 69% margin”.
- ROAS = $62,750 ÷ $9,000 = 6.97×
- Break-even = 100 ÷ 69 = 1.45× — the margin number, not the platform default, sets the bar
Break-even ROAS at this margin — 1.45 : 1. Read next to the headline, this is the figure that shows the shape of the trade-off.
Gross profit from the campaign — $34,298. This is the number experienced users quote when the headline alone would mislead.
Revenue needed for 2× break-even ROAS — $26,087. This is the number experienced users quote when the headline alone would mislead.
Overwrite any input above and every line of this example updates with it — the substitution is live, not a screenshot of somebody else’s numbers.
Scenario table: ROAS at ±10 % and ±20 % of the key input
The honest version of any estimate is a corridor, and this one is cheap to produce: ROAS was recomputed at 5 points along the dominant input, with every other field left untouched.
| Ad spend setting | ROAS |
|---|---|
| 80 % of the example value | 8.72 : 1 |
| 90 % of the example value | 7.75 : 1 |
| example inputs | 6.97 : 1 |
| 110 % of the example value | 6.34 : 1 |
| 120 % of the example value | 5.81 : 1 |
That spread — 5.81 : 1 at the low end, 8.72 : 1 at the high — is what a careful read of ROAS looks like: a band you can state out loud, with the reason for each edge. Reproduce it in the form above by editing Ad spend alone; the substitution steps will follow your figures exactly.
Where ROAS is fragile — and where it is not
This list was computed for this specific engine just now: each numeric input was nudged ±10 % while every other field held its example value, and the ROAS was recalculated from scratch. Read it as a map of where ROAS is fragile — drawn for the example inputs, which is the map you want when deciding what to measure carefully.
- Nudge Ad spend by ±10 % and ROAS lands between 6.34 : 1 and 7.75 : 1 (sensitivity ≈11.1 %)
- Ad-attributed revenue +10 % → ROAS = 7.67 : 1 · −10 % → 6.28 : 1 (the ROAS shifts ≈10.0 %)
Ad spend is the dominant lever here: ten percent either way moves the result by about 11.1 %, from 6.34 : 1 to 7.75 : 1. Measure that input from a document rather than from memory, and treat Ad-attributed revenue as the second priority (≈10.0 % per ten percent). The remaining fields can sit at safe defaults without materially changing the answer — knowing which is which is what separates a careful calculation from an anxious one.
Is your ROAS good — reading the result bands
Nobody acts on a bare figure — they act on a figure with a comparison attached. The verdict attached to the default calculation — “Above the 1.45× break-even at 69% margin” — is one band on a ladder your own figure may sit somewhere else on. How much of that band is luck? On Ad spend alone ten percent either way covers 6.34 : 1 to 7.75 : 1. The practical reading rules: ask what would have to change to move you one band. If the answer is “a small, plausible input difference”, the band itself is not the finding — the uncertainty is.
The comparison worth making is not with somebody else’s ROAS but with the version of your own situation measured last quarter — same formula, same conventions, different inputs.
Common mistakes with ROAS (and the fix)
Blended ROAS includes organic and repeat buyers that arrive anyway; incremental ROAS from holdouts is usually 30–60% lower — plan budgets on the incremental figure. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Treating the example inputs as a recommendation. They are a demonstration of the mechanism — a decision-grade ROAS begins the moment your own figures replace them.
This model has its own particular trap: Ad spend carries ≈11.1 % of the response per ten percent of error, so effort spent elsewhere is largely decorative.
A final trap is presentation: reporting ROAS to more decimal places than the inputs support. The tool prints what the arithmetic gives; you should quote only what your least precise field justifies.
Six things to confirm before acting on ROAS
- Compare the output against one published benchmark or a colleague’s independent estimate.
- Confirm the example values are plausible for your own situation before replacing them.
- Put Ad spend under a magnifier; the sensitivity table above is the reason why.
- Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
- Note the date and the inputs beside the number so the figure can be audited later.
- Run the ±10 % stress on the top two levers and check that your conclusion survives both.
Five steps from raw inputs to a figure you can defend
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — collect, then type. Everything this tool asks for is listed above (ad spend ($), ad-attributed revenue ($), gross margin (%)). Pull each figure from something you can point at — paperwork, a dashboard, a label — before touching a field. Guesswork at the input stage cannot be repaired at the interpretation stage. The fastest sanity test is to guess the answer first and see how far the calculation disagrees.
Step 2 — enter the conservative case first. Resist the flattering scenario. Type the inputs you would defend in front of a sceptical reader, read the ROAS (6.97 : 1 for the example values), and note the verdict band. A figure nobody can reproduce is a figure nobody will act on twice.
Step 3 — change one input at a time. Nudge a single field by ten percent, watch the headline and its companions move, then undo it. Two or three fields will dominate — the sensitivity table above already ranks them for this engine. Note the assumption you are least sure about; that is where the real risk lives.
Step 4 — ask what would have to be true. Take the result you want and work backwards through the inputs until you find the assumption that produces it; then decide honestly whether that assumption is defensible. If a result feels obviously right, that is the moment to check the inputs hardest.
Step 5 — write the one-line memo. “ROAS = 6.97 : 1 on this date, from these inputs.” That line is the entire deliverable; everything else on this page is how you earned the right to write it. One decimal place more than your data supports is one decimal place of fiction.
Where ROAS matters in practice
Business & Entrepreneurship arguments end at arithmetic or they do not end. ROAS is the arithmetic: 6.97 : 1 on the example inputs, reproducible by anyone who types the same numbers. Comparisons are cheap: run the identical calculation for the alternative and look at the gap.
The audience for this page is people who need one trustworthy number before their next decision. In professional Marketing & Growth practice the pattern is always the same — screen with ROAS, then invest slow analysis only in whatever survives the screen. When two sources disagree, it is almost never the arithmetic that differs.
There is a personal-administration use people overlook: periodic self-checking. ROAS quietly drifts as life changes — rates move, bodies change, costs compound — and re-running it a few times a year catches drift while correction is still cheap. The input you reach for first is usually the one you measured longest ago.
ROAS — frequently asked questions
What affects ROAS the most?
ROAS is driven above all by Ad spend. Perturbing only that field by ten percent either way produced 6.34 : 1 against the 6.97 : 1 baseline — a ≈11.1 % response, while Ad-attributed revenue manages ≈10.0 %.
Which matters more: ad-attributed revenue or ad spend?
For ROAS, Ad spend wins the head-to-head (≈11.1 % against ≈10.0 % per ten-percent change). Knowing which input dominates is the difference between careful work and merely slow work.
What is a typical ROAS?
With the example inputs on this page the result is 6.97 : 1, labelled “Above the 1.45× break-even at 69% margin”. “Typical” varies with situation, which is why every result here ships with its verdict band and its sensitivity list: they turn one figure into a range you can locate yourself inside.
How do I calculate ROAS by hand?
Three steps: write the formula (ROAS = attributed revenue ÷ ad spend), insert your values, and simplify. The worked example section shows exactly that chain for the default inputs; replicating it once on paper teaches you more about ROAS than any number of calculator runs.
What happens to ROAS if ad spend changes by 10 %?
On these inputs a ±10 % change in ad spend takes ROAS to 6.34 : 1 against the 6.97 : 1 example — around 11.1 % of the headline. The same test on every other field is in the sensitivity section.
Is the ROAS result of 6.97 : 1 good or bad?
The tool answers “what”, not “whether”: 6.97 : 1 carries the verdict “Above the 1.45× break-even at 69% margin” for the default case, which is a starting interpretation rather than a verdict on your situation. Re-run with your own figures and compare the bands.
Can ROAS be negative or empty?
Yes, and that is informative rather than broken: a negative ROAS usually means the inputs encode an outflow or a shortfall, and the verdict band above labels exactly that situation instead of hiding it.
Should I use ROAS before launching?
Yes — an ROAS run on honest inputs before spending is the cheapest consulting an entrepreneur can buy. Re-run at every pricing change; the number moves more often than founders expect.
Why not just target the highest ROAS?
Because ROAS falls as spend scales (marginal buyers cost more) — profit maximisation buys volume past the point of best ROAS.
Does ROAS count returns and refunds?
Attribution windows rarely wait for return windows — report post-return ROAS once refunds are known or the channel overstates.
Can this tool see the numbers I type?
It cannot. There is no submission step: the calculation happens in your browser and the result disappears when you close the page. Treat the fields above as a scratchpad rather than a form.
The vocabulary of ROAS
- Break-even ROAS at this margin
- 1.45 : 1 in the default ROAS calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Gross profit from the campaign
- $34,298 on the example inputs — a companion figure printed beside the headline of ROAS so that no result is read in isolation.
- Revenue needed for 2× break-even ROAS
- $26,087 in the default ROAS calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- ROAS
- The primary output of this tool: 6.97 : 1 for the default inputs, computed exactly from ROAS = attributed revenue ÷ ad spend.
- Worked example
- The step-by-step substitution printed above, so the arithmetic can be re-derived by hand or in a spreadsheet.
- Verdict band
- The interpretation attached to a result (“Above the 1.45× break-even at 69% margin” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the ROAS moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Methodology, sources and limits
There is no black box on this page — the engine evaluates ROAS = attributed revenue ÷ ad spend. Source of record: Paid-media standard (break-even ROAS = 1/margin). Specialist software layers extra coefficients on top of the same algebra; none are hidden here, and that transparency is what makes a disagreement traceable to a specific input instead of a black box.
Nothing here replaces a qualified professional, and nothing here is approximate either — the arithmetic is exact, and the honesty is in the inputs you supply. The design constraint was set by usefulness rather than by comfort: an estimate you can interrogate beats an answer you have to trust.
Next steps after the calculation
Save the number together with its inputs and today’s date; an ROAS figure without context is unusable the moment an input changes.
This page was written for people who need one trustworthy number before their next decision, and the promise is that nothing above required trust. Bookmark the tool, re-run it whenever an input moves by more than a few percent, and keep the date with the number.