iROAS and ROAS at a glance
ROAS is the figure every ad platform reports by default. The platform records a conversion when someone who saw or clicked an ad later buys within the attribution window, attaches the order value, adds it up across the campaign and divides by the spend. It is fast, free and available at every level of the account, which is why bid strategies, dashboards and most weekly reviews run on it. Its weakness is that it is a record of coincidence: it credits every sale the ad was present for, whether or not the ad changed anything. The performance economics guide explains where ROAS sits in the chain from spend to margin and why a target taken from a platform rather than from unit economics misleads.
Incremental ROAS asks the counterfactual question directly. Some people or regions are withheld from the campaign at random, the rest are exposed, and the difference in revenue between the two groups is the revenue the campaign caused. Divide that by the spend and you have iROAS. The incrementality testing guide covers the designs that produce it: user-level holdouts, platform lift studies and geo tests, each with its own trade-off between cleanliness and practicality. Both Google Ads and Meta document lift measurement products in their help centres, and both note eligibility and spend requirements, so not every campaign can be tested on demand.
The two figures answer different questions. ROAS asks how much revenue the platform associates with each unit of spend. iROAS asks how much revenue the spend produced that the business would not otherwise have had. When an audience was going to buy anyway, the two diverge sharply; when the ads reach people who would never have found the brand, they move closer together. That divergence is itself useful information, and reading it is most of the skill.
Compare table
ROAS vs Incremental ROAS (iROAS)
| Row label | ROAS | Incremental ROAS (iROAS) |
|---|---|---|
| What is counted | Revenue from every conversion the platform attributes to the ads | Only the revenue that differs between exposed and holdout groups |
| Where the figure comes from | The platform's conversion tracking and attribution settings | A lift study, a geo test or a user-level holdout |
| Causality | None: it records association within a window | Causal, within the limits of the test design and its power |
| Speed | Available daily, at campaign, ad set and ad level | Available once a test has run its course, often weeks later |
| Cost to produce | Free once tracking is in place | Withheld spend, analyst time and sometimes a minimum budget to qualify |
| Who reports it | The platform being judged | The team or a neutral method, though platform lift studies are run by the platform |
| Use in bidding | Directly: bid strategies optimise towards it | Indirectly: it calibrates what the platform target should be |
| Use in budgeting | Weak: it rewards channels that harvest existing demand | Strong: it shows what an extra or a removed budget would change |
| Typical relationship | Higher, sometimes far higher, for warm audiences | Lower, and closest to ROAS for genuinely new audiences |
The rows that matter most are the two on bidding and budgeting. ROAS is the number the platform's own optimisation targets, so it is the number you have to speak when you set a bid. iROAS is the number the finance team should care about, because it is the only one that predicts what happens to revenue when the budget moves.
When to use ROAS
Use platform ROAS to run the campaign. It is the signal bid strategies optimise against, the figure that shows within days whether a new ad, audience or landing page is pulling its weight, and the common language between the people who build campaigns and the platforms that deliver them. Comparing ads within an ad set, ad sets within a campaign or this week with last week on ROAS is reasonable, because the attribution bias is broadly similar across the things being compared.
ROAS also works as a tripwire. A sudden fall usually means something broke: a tracking change, a feed problem, a landing page error or a shift in the auction. Those problems are worth catching the same day, and no experiment can do that.
Where ROAS stops being useful is at the boundaries between things whose bias differs. Comparing a remarketing campaign with a prospecting campaign, a branded search campaign with a generic one, or one channel with another on ROAS rewards whichever reaches people closest to buying. Before ROAS goes into any decision about how to split money, check that the business can afford the return at all: the marginal returns guide shows why the average return a campaign reports says little about the return on the next slice of spend, and the ROAS calculator does the basic arithmetic once revenue and spend are agreed.
When to use iROAS
Use incremental ROAS to decide budgets. Whenever the question is whether to add, cut or move money between channels, the answer depends on what each channel causes, and only IncrementalityConversions caused by marketing. testing measures that. The largest and most contested budget lines deserve a test first: remarketing, branded search, affiliate and any channel whose platform ROAS looks too good to question.
iROAS is also the right figure for setting expectations with finance. A board that sees platform ROAS summed across channels will usually see more revenue claimed than the business booked, because each platform counts the same customer. Incremental figures from tests, or from a model calibrated with tests, do not add up to more than the total, and they survive the reconciliation that platform figures fail. The comparison of marketing mix modelling and multi-touch attribution explains how a model extends a handful of test results to the whole budget.
The cost is time and certainty. A test measures one channel at one spend level over one period, and a result that is not statistically clear is not a result. Plan tests around the decisions they will inform, write down the smallest effect that would change the decision before starting, and accept that the answer will need refreshing as audiences and creative change.
A homeware retailer tests its remarketing
Fennel & Finch, an online homeware retailer, spends £20,000 a month on social remarketing that reports a platform ROAS of 9.0, or £180,000 in attributed revenue. It runs a four-week holdout, withholding the ads from a random 20% of the remarketing audience. Exposed shoppers buy at a revenue per person only slightly higher than the holdout, and scaled to the full audience the difference is £36,000 a month: an iROAS of 1.8. The retailer's contribution margin is 40%, so the campaign returns £14,400 of margin for £20,000 of spend. It cuts remarketing to the cart-abandoner segment, where the test showed most of the lift, and moves the rest of the budget into prospecting, which it schedules for its own test the following quarter.
Decision table
| Situation | Use | Why |
|---|---|---|
| Choosing between two ads or audiences in one campaign | ROAS | The bias is similar on both sides and the answer is needed fast |
| Setting a bid strategy target | ROAS, calibrated by a past test | The platform optimises against what it records |
| Deciding whether to keep, cut or grow a channel | iROAS | Only caused revenue predicts what a budget change will do |
| Remarketing or branded search looks unusually profitable | iROAS | These audiences were closest to buying, so attribution flatters them most |
| Explaining marketing's return to finance | iROAS, or a model calibrated by tests | Incremental figures reconcile with booked revenue |
| Spotting a tracking or delivery problem | ROAS | A sudden change shows within a day |
| Channel too small to reach a readable test | ROAS with caution, and a model | A weak test result is not an answer |
Reporting both without confusing anyone
The cleanest reports show both figures for the channels that have been tested, side by side, with the ratio between them. That ratio is the useful part: if a channel's iROAS is a stable fraction of its platform ROAS across tests, the platform figure can be read through that ratio between tests, and the bid target can be set to deliver the incremental return the business needs. For untested channels, say so in the report rather than leaving platform ROAS to stand in silently.
Label every figure with its source and its window. "ROAS (platform, attributed)" and "iROAS (holdout test, dated)" are clumsy, but they stop the two from being summed, averaged or compared across channels. Keep the test date visible, because an incremental result describes the channel at the spend level and creative of the test period and goes stale as either changes.
Common mistakes
- Summing platform ROAS across channels and presenting the total as marketing's return, when each platform counts the same customers.
- Comparing channels on platform ROAS, which rewards whichever reaches people closest to buying rather than whichever adds the most revenue.
- Calling a figure incremental without a holdout, such as a share of attributed revenue picked by judgement.
- Setting a bid target in iROAS terms, which the platform cannot see, instead of translating it into the platform's own ROAS.
- Treating one test as permanent. Incremental returns shift with spend level, creative, season and audience.
- Reading an underpowered test as proof of no effect, when the test was too small to detect the effect that mattered.
- Ignoring margin. An iROAS that clears one still loses money if the contribution margin on the caused revenue does not cover the spend.
