Incrementality testing for Google Shopping, step by step
How to run an incrementality test: holdout and geo designs, the incremental ROAS formula, a worked example and a decision rule you set before you start.
Your ad account says a product group returns a ROAS of 4.0. It cannot say how many of those orders the ads caused and how many would have arrived anyway. An incrementality test answers that by switching the ads off for a comparable group and counting what happens.
The definition on its own is in the incrementality glossary entry. This page is about running the test on Google Shopping and reading what comes out.
Two groups, one difference
ROAS credits every order that follows an ad. An incrementality test counts only the orders your ads added, by comparing a group that saw them with a comparable group that did not. A test asks the question attribution cannot: what would have happened without the ad?
Picture two groups of 10,000 people. The group that saw your ads placed 200 orders. The group that did not see them placed 150. The ads added 50 orders, and the other 150 would have come anyway.
Two groups of 10,000 people: how many orders did the ads add?
Show the dataHide the data
| Group of 10,000 people, and the difference | Number of orders |
|---|---|
| Saw ads | 200 |
| Did not see ads | 150 |
| Caused by the ads | 50 |
The test does not say which click earned which order. It says how many orders the ads added in total, and that total is what a budget decision runs on.
How do you calculate incremental ROAS?
Incremental ROAS is incremental revenue divided by ad spend. Incremental revenue is the revenue from the orders the ads added, so it can never be larger than the revenue credited to the ads.
| Step | Result |
|---|---|
| Incremental orders (200 − 150) | 50 |
| Revenue credited to the ads (200 × €80.00) | €16,000.00 |
| Incremental revenue (50 × €80.00) | €4,000.00 |
| ROAS (€16,000.00 ÷ €4,000.00) | 4.0 |
| Incremental ROAS (€4,000.00 ÷ €4,000.00) | 1.0 |
Illustrative data.
The ad spend is €4,000.00 in both ratios. Only the revenue on top changes, so the same campaign is a 4.0 or a 1.0 depending on the question you ask.
Same €4,000.00 of ads: ROAS with every order credited, and with only the added orders
Show the dataHide the data
| Which orders count | Revenue per €1.00 of ads |
|---|---|
| ROAS (200 orders credited) | 4 |
| Incremental ROAS (50 orders) | 1 |
Google Ads Help gives the same formula for its Conversion Lift tool: incremental return on ad spend is incremental conversion value divided by total ad spend. The groups need to be the same size. If they are not, scale the control group’s orders to the size of the test group before you subtract.
Holdout, geo split or time-based
A holdout or a geo split gives you a comparison group in the same period, and a time-based test does not. That difference matters more than anything else in the design.
| Design | Groups |
|---|---|
| Holdout | Shown vs held back |
| Geo split | Matched regions |
| Time-based | Ads on vs off, by week |
A holdout is the cleanest: you choose, at random, a share of people who will not see the ads. A geo split suits cases where individuals cannot be split. Google Ads Help describes Conversion Lift in both forms, based on users and based on geography, with treatment regions that see your ads and control regions where they are withheld. It also says Conversion Lift is not available for all accounts.
A time-based test is the weakest, because you compare two different weeks. If orders fall when you switch the ads off, you cannot tell the ads from the weather, a competitor’s sale or your own price change. Use it only when nothing else is possible, and treat the result as a hint.
Four things to have before you start
Missing any one of these makes the result impossible to act on.
| You need | Because |
|---|---|
| Enough orders | If each group would get only a handful of orders, a real difference looks the same as chance. A product group with thousands of products and steady sales can be tested. A single slow product usually cannot. |
| A clean split | The holdout must not see the ads, and the two groups must be alike. Other campaigns, other channels and your own emails can leak into the holdout. |
| A stable period | Do not run a sale, change prices or run out of stock in one group only. Leave tracking alone too: a change halfway through breaks the comparison. |
| A decision rule | Write down, before you see the result, what incremental ROAS you need and what you will do about it. |
The control group sets the answer. Keep the 200 orders from the group that saw ads, change only the control, and incremental ROAS swings from 2.0 to 0.2.
Same 200 orders with ads: how incremental ROAS falls as the control group buys more
Show the dataHide the data
| Orders in the control group (no ads) | Incremental ROAS: added revenue per €1.00 of ads |
|---|---|
| 100 | 2 |
| 150 | 1 |
| 170 | 0.6 |
| 190 | 0.2 |
Decide with a rule written in advance
Compare incremental ROAS with the product’s break-even ROAS, which is 1 ÷ contribution margin. A result above it means the added orders paid for the ads. A result below it means they did not, whatever the attributed ROAS says.
At a 40% contribution margin, break-even ROAS is 1 ÷ 0.40 = 2.5. The attributed ROAS of 4.0 clears it comfortably. The incremental ROAS of 1.0 does not: the 50 added orders earn €1,600.00 of profit before ad spend, against €4,000.00 spent.
In POAS terms, which is ROAS × contribution margin and has a break-even of 1.0, the attributed return is 1.6 and the incremental return is 0.4. POAS vs ROAS explains the link, and the break-even ROAS calculator gives the floor for your own margin.
At a 40% margin: POAS when every order counts, and when only added orders count
- POAS: profit per €1.00 of ads
- Break-even: POAS 1 (1.0)
- Profit
- Loss
Show the dataHide the data
| Which orders count | POAS: profit per €1.00 of ads |
|---|---|
| Attributed POAS | 1.6 |
| Incremental POAS | 0.4 |
Put the other way round, the same €4,000.00 of spend needs a certain number of added orders to pay for itself, and the margin sets that number.
How many extra orders must €4,000.00 of ads add to break even, at each margin?
Show the dataHide the data
| Contribution margin | Added orders needed to break even |
|---|---|
| 20% | 250 |
| 25% | 200 |
| 40% | 125 |
| 50% | 100 |
A usable rule has three parts: the number you compare with, what you do above it (increase priority), and what you do below it (lower priority, or fix price and costs first). Add a fourth for when the result is too close to call: run the test again, longer or on a larger group.
Read the result per product group
Two groups with the same ROAS can differ a lot in what the ads added. Group products by something that matches how you run campaigns, such as brand, category or margin band.
One hypothesis to test: products that people already search for by name, and products you retarget, can show a strong ROAS and weak increments. Those shoppers may have been about to buy anyway, so the ads get credit for orders they did not cause. It is a hypothesis, not a finding, and a test is how you check it for your own products.
A hypothesis: ROAS and incremental ROAS can rank product groups the other way round
- ROAS (every attributed order)
- Incremental ROAS (added orders only)
Show the dataHide the data
| Product group | ROAS (every attributed order) | Incremental ROAS (added orders only) |
|---|---|---|
| Products people search for by name | 8 | 0.8 |
| Retargeted products | 6 | 1.5 |
| Other products | 3 | 2.4 |
Each group needs enough orders on its own, so split a test only as far as your volume allows. Product Segmentation segments products by advertising clicks and attributed return, and a test shows how much of that return the ads added.
A simple test plan
Start with one product group and one question, and follow the steps in order. The mistake to avoid is skipping the second step and choosing the rule after the result is in, which turns a test into a story.
- Pick one question and one product groupFor example: do the ads for these products add orders? Choose a group with enough orders for a difference to show.
- Write the decision rule downDecide what incremental ROAS you need, usually the break-even ROAS, and what you will do above and below it.
- Split at randomHold back part of the audience, or a set of comparable regions, and keep everything else the same in both groups.
- Run it for the planned periodDo not change prices, budgets or targeting mid-test, and do not stop early because the first days look good.
- Calculate and apply the ruleIncremental orders × order value ÷ ad spend gives incremental ROAS. Compare it with the rule you wrote in step 2.
When the test ends, calculate incremental orders and incremental ROAS as in the worked example above, and apply your rule. Write down the dates, the split and the result, so the next test can start from them.
What ROAS and MER can’t tell you
ROAS counts the orders the ad platform credits to your ads, and MER counts all shop revenue against all marketing spend. Neither compares what happened with the ads to what would have happened without them.
ROAS can be high because the ads reached people who were going to buy. ROAS says how much revenue each euro of ads is credited with, and what is a good ROAS shows how to read it against break-even.
MER does not depend on one platform’s attribution, but it counts all revenue, including orders that would have come anyway, so it cannot show what the ads added or be read per product. ROAS, MER, POAS and nCAC compares the metrics, and break-even ROAS per product shows how to set the floor for each one.
An incrementality test checks both. It is slower and takes planning, so save it for the decisions that move the most spend.
Test your biggest spender first
The break-even ROAS calculator gives you the floor for the rule.
Pick the product group that takes the most spend and write its decision rule today: its break-even ROAS, and what you will do above and below it. Then plan one holdout or geo split for that group, with a start date and a length you will not change.
Keep reading.
Break-even ROAS per product: why one target hides losses
Break-even ROAS = 1 ÷ contribution margin. See how one account-wide ROAS target funds loss-making products, with a three-product example.
Competitive pricing examples: 9 real companies, sourced
Competitive pricing examples from Tesco, Currys, Aldi, Costco, Amazon and Delta, plus a worked trainer example: when to price above, at or below the median.
Customer acquisition cost formula for ecommerce
Customer acquisition cost is ad spend divided by new customers. See the formula, a worked example, and the most you can pay for a first order.
Frequently asked questions.
What is the difference between A/B testing and incrementality testing?
How do you calculate incrementality?
How do I calculate incremental ROAS?
How do you prove incrementality?
See which of your products to push, fix or pause. Start with your own products, or a 30-second estimate.
Check one product first: work out its break-even ROAS in the calculator. Then see where all your products stand.
Not ready to connect? Book a demo: a video call with Berend, then a demo account.