Key takeaway
ROAS (return on ad spend) shows attributed revenue per unit of ad spend. $1,000 spend and $4,000 revenue is 4.00x ROAS.
It compares campaigns and channels — it is not full profit after COGS, fees and overhead.
What it means
ROAS = revenue ÷ ad spend, said as a multiple or percent.
Attributed revenue depends on attribution windows and tracking quality.
ROAS is narrower than ROI, which usually folds in more costs.
Analogy: $10 of flyers driving $40 of flyer-mentioned sales is 4x before product costs.
When you would use it
Use when spend and revenue share a measurable window.
Weaker for long offline cycles or broken pixels.
Targets should reflect your margins, not random blog averages.
How to use the tool
Use the matching TCB Tools page and work top to bottom:
- Open the ROAS Calculator.
- Enter ad spend.
- Enter attributed revenue.
- Read the live multiple.
- Try example chips or modes.
- Share a brief if needed.
No account is required. Results update as you type.
Formula / method + worked example
ROAS = Revenue ÷ Ad Spend.
4000÷1000=4.00x.
12500÷5000=2.50x.
Spend must be > 0.
With 40% gross margin, $4,000 revenue implies ~$1,600 gross profit before other overhead.
How to read the result
Above 1.0x means revenue exceeds ad spend before COGS/overhead — not automatic profit.
Compare brand vs non-brand using your baselines.
Planning aid, not professional financial advice.
Common mistakes
- Calling ROAS profit. Include COGS/fees.
- Mismatched dates. Align windows.
- Scaling one lucky day. Use stable periods.
- Broken tracking. Reconcile samples.
- Mixed currencies. Convert first.
- Ignoring incrementality. Ask what happens without ads.
Related ideas
Pair with CPC and CTR. Read ROAS by channel.
View-through credit can inflate display ROAS.
Refunds change true revenue.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit ROAS weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure ROAS; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about ROAS, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions ROAS.
If leadership wants only a headline, still keep working notes for ROAS in your own folder.
Seasonality and promotions change ROAS; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for ROAS.
Revisit assumptions about ROAS after tool, tracking or pricing changes.
A short checklist for ROAS beats relying on memory during busy weeks.
View-through credit can inflate display ROAS.
Refunds change true revenue.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit ROAS weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure ROAS; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about ROAS, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions ROAS.
If leadership wants only a headline, still keep working notes for ROAS in your own folder.
Seasonality and promotions change ROAS; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for ROAS.
Revisit assumptions about ROAS after tool, tracking or pricing changes.
A short checklist for ROAS beats relying on memory during busy weeks.
View-through credit can inflate display ROAS.
Refunds change true revenue.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit ROAS weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure ROAS; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about ROAS, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions ROAS.
If leadership wants only a headline, still keep working notes for ROAS in your own folder.
Seasonality and promotions change ROAS; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for ROAS.
Revisit assumptions about ROAS after tool, tracking or pricing changes.
A short checklist for ROAS beats relying on memory during busy weeks.
Try the tools
Open the ROAS Calculator with $1,000 / $4,000.
