Incremental ROAS
The revenue an ad created that would not have happened without it, divided by what you spent. It separates sales the ad caused from sales it simply got credit for.
"Revenue without" is never observed directly. It comes from a control group: a holdout audience, a set of paused regions, or a model.
What is incremental ROAS?
Attribution answers "which ad touched this buyer?" It doesn't answer "would this buyer have bought anyway?" Someone who searches your brand name, or who already had items in their cart, often buys whether or not they see one more ad. Attribution still gives that ad the credit.
Incremental ROAS counts only the sales the ad caused. You find them by comparing a group that saw the ads with a similar group that didn't. The gap between the two is the ad's real effect, and that gap is usually smaller than attributed revenue.
How it's calculated
Every method compares a treated group with a control. The control tells you what revenue would have been without the ads. Subtract it, and what's left is incremental.
| Input | Where it comes from | What it gives us |
|---|---|---|
| test_revenue | All orders from regions or users who could see the ads | Revenue with ads |
| control_revenue | All orders from matched regions or a holdout group with ads off | Baseline, scaled to the test group's size |
| spend | Ad platform, test group only | The denominator |
| attributed_revenue | Your attribution, same period and group | Incrementality factor, to correct future attributed numbers |
How to measure it
Pick the method that fits the channel and your budget. Each gives a point-in-time reading, so rerun it when spend, creative or season changes a lot.
- 1Geo testPause a campaign in a set of matched states or cities and compare total sales against those still running it.
- 2Holdout audienceRandomly exclude a slice of your target audience, often through the platform's own lift study, and compare conversion rates.
- 3Marketing mix modelEstimate each channel's contribution from how sales moved with spend over 12 to 24 months of history.
Worked examples
Example 1: A geo test on a retargeting campaign
An illustrative brand pauses its Meta retargeting campaign in a group of control states for four weeks and keeps it running everywhere else. Before the test, the test states sold exactly twice as much as the control states.
| Line | Value | How we got it |
|---|---|---|
| Control states, all revenue | ₹21,00,000 | Orders, campaign paused |
| Expected test revenue without the campaign | ₹42,00,000 | Control × 2.0 pre-test ratio |
| Test states, all revenue | ₹45,60,000 | Orders, campaign running |
| Incremental revenue | ₹3,60,000 | ₹45,60,000 − ₹42,00,000 |
| Campaign spend in test states | ₹3,00,000 | Meta Ads |
| Attributed revenue in test states | ₹10,50,000 | Attributed ROAS 3.50 |
| Incremental ROAS | 1.20 | ₹3,60,000 ÷ ₹3,00,000 · incrementality factor 34% |
- AttributedA ROAS of 3.5 made this look like one of the best campaigns in the account.
- IncrementalIt caused ₹1.20 of revenue for every rupee. Whether that's profitable depends on break-even ROAS. At a break-even of 2.0, it isn't.
- Going forwardThe 34% factor can be applied to this campaign's attributed ROAS until the next test.
Example 2: Two campaigns, ranked differently
Illustrative results from two tests in the same account. Attribution and incrementality put them in opposite order.
Using incremental ROAS to decide
Use iROAS to set how much you trust each campaign's attributed numbers. Compare it to break-even ROAS, and treat these bands as a starting point.
Common mistakes
- Treating attribution as causationA touch before purchase isn't proof the ad caused it, especially for retargeting and brand search.
- Comparing only attributed salesLift tests compare total revenue in each group. Using attributed sales brings the bias straight back.
- Mismatched regionsMetros vs tier 3 towns will differ for reasons that have nothing to do with ads.
- Testing once, trusting foreverIncrementality shifts with spend, creative and season. Retest at least a couple of times a year.
Frequently asked questions
Is incremental ROAS always lower than attributed ROAS?
Usually, but not always. Upper-funnel video or awareness campaigns can drive buyers who never click, so their incremental effect can exceed what click-based attribution gives them.
Which campaigns should I test first?
The ones with high attributed ROAS that reach people who already know you: retargeting, brand search and existing-customer audiences. That's where the gap between credited and caused tends to be biggest.
How is it different from marginal ROAS?
Incremental ROAS compares ads on vs ads off. Marginal ROAS compares your current budget with a bit more. One tells you whether a campaign works at all, the other whether it's worth growing.
Do I lose sales by running a holdout?
Only the incremental sales in the control group, which is exactly what you're trying to measure. Keep the control small and the test short enough to limit the cost.
Related metrics
Know which sales your ads actually caused
BooleanMaths tracks every order by region and channel, so geo tests and marketing mix models read from the same clean data as your attribution.
Incremental ROAS
The revenue an ad created that would not have happened without it, divided by what you spent. It separates sales the ad caused from sales it simply got credit for.
"Revenue without" is never observed directly. It comes from a control group: a holdout audience, a set of paused regions, or a model.
What is incremental ROAS?
Attribution answers "which ad touched this buyer?" It doesn't answer "would this buyer have bought anyway?" Someone who searches your brand name, or who already had items in their cart, often buys whether or not they see one more ad. Attribution still gives that ad the credit.
Incremental ROAS counts only the sales the ad caused. You find them by comparing a group that saw the ads with a similar group that didn't. The gap between the two is the ad's real effect, and that gap is usually smaller than attributed revenue.
How it's calculated
Every method compares a treated group with a control. The control tells you what revenue would have been without the ads. Subtract it, and what's left is incremental.
| Input | Where it comes from | What it gives us |
|---|---|---|
| test_revenue | All orders from regions or users who could see the ads | Revenue with ads |
| control_revenue | All orders from matched regions or a holdout group with ads off | Baseline, scaled to the test group's size |
| spend | Ad platform, test group only | The denominator |
| attributed_revenue | Your attribution, same period and group | Incrementality factor, to correct future attributed numbers |
How to measure it
Pick the method that fits the channel and your budget. Each gives a point-in-time reading, so rerun it when spend, creative or season changes a lot.
- 1Geo testPause a campaign in a set of matched states or cities and compare total sales against those still running it.
- 2Holdout audienceRandomly exclude a slice of your target audience, often through the platform's own lift study, and compare conversion rates.
- 3Marketing mix modelEstimate each channel's contribution from how sales moved with spend over 12 to 24 months of history.
Worked examples
Example 1: A geo test on a retargeting campaign
An illustrative brand pauses its Meta retargeting campaign in a group of control states for four weeks and keeps it running everywhere else. Before the test, the test states sold exactly twice as much as the control states.
| Line | Value | How we got it |
|---|---|---|
| Control states, all revenue | ₹21,00,000 | Orders, campaign paused |
| Expected test revenue without the campaign | ₹42,00,000 | Control × 2.0 pre-test ratio |
| Test states, all revenue | ₹45,60,000 | Orders, campaign running |
| Incremental revenue | ₹3,60,000 | ₹45,60,000 − ₹42,00,000 |
| Campaign spend in test states | ₹3,00,000 | Meta Ads |
| Attributed revenue in test states | ₹10,50,000 | Attributed ROAS 3.50 |
| Incremental ROAS | 1.20 | ₹3,60,000 ÷ ₹3,00,000 · incrementality factor 34% |
- AttributedA ROAS of 3.5 made this look like one of the best campaigns in the account.
- IncrementalIt caused ₹1.20 of revenue for every rupee. Whether that's profitable depends on break-even ROAS. At a break-even of 2.0, it isn't.
- Going forwardThe 34% factor can be applied to this campaign's attributed ROAS until the next test.
Example 2: Two campaigns, ranked differently
Illustrative results from two tests in the same account. Attribution and incrementality put them in opposite order.
Using incremental ROAS to decide
Use iROAS to set how much you trust each campaign's attributed numbers. Compare it to break-even ROAS, and treat these bands as a starting point.
Common mistakes
- Treating attribution as causationA touch before purchase isn't proof the ad caused it, especially for retargeting and brand search.
- Comparing only attributed salesLift tests compare total revenue in each group. Using attributed sales brings the bias straight back.
- Mismatched regionsMetros vs tier 3 towns will differ for reasons that have nothing to do with ads.
- Testing once, trusting foreverIncrementality shifts with spend, creative and season. Retest at least a couple of times a year.
Frequently asked questions
Is incremental ROAS always lower than attributed ROAS?
Usually, but not always. Upper-funnel video or awareness campaigns can drive buyers who never click, so their incremental effect can exceed what click-based attribution gives them.
Which campaigns should I test first?
The ones with high attributed ROAS that reach people who already know you: retargeting, brand search and existing-customer audiences. That's where the gap between credited and caused tends to be biggest.
How is it different from marginal ROAS?
Incremental ROAS compares ads on vs ads off. Marginal ROAS compares your current budget with a bit more. One tells you whether a campaign works at all, the other whether it's worth growing.
Do I lose sales by running a holdout?
Only the incremental sales in the control group, which is exactly what you're trying to measure. Keep the control small and the test short enough to limit the cost.
Related metrics
Know which sales your ads actually caused
BooleanMaths tracks every order by region and channel, so geo tests and marketing mix models read from the same clean data as your attribution.