Holdout Tests for Lifecycle Marketing: Prove the Lift

The short answer
- A holdout test keeps a random share of eligible people from getting a message, so the difference in outcomes between the two groups is the message's real lift.
- Choose the holdout size and the success metric before launch, then do not stop the test early because a dashboard looks good.
- Report lift with a confidence interval and judge journeys on retention, LTV and payback rather than opens and clicks.
What is a holdout test in lifecycle marketing?
A holdout test splits an audience at random into two groups. One group receives the journey as normal. The other, the holdout, is eligible for it but receives nothing. Because the split is random, the two groups are alike in every way except the message, so any difference in what they do afterwards can be credited to the message.
This answers the question most lifecycle reports skip: would these people have converted anyway? Open and click rates cannot answer it. A welcome email can have a strong click rate and still change nothing, because the people who click were already going to activate. The holdout shows the part of the result the email actually caused.
Why are opens and clicks not enough?
Engagement metrics measure attention, not impact. Opens are also less reliable than they used to be, because some mail clients load images automatically. A journey can win on every engagement metric and still lose money if it discounts people who would have paid full price.
When I rebuilt event-triggered nurture at Customer.io, the journeys were moved from being judged on clicks to being judged on LTV, payback and cohort quality, with a 10% holdout that never got the email. Engagement came in +22% against that holdout. The holdout is what made that number mean something.
How big should the holdout be?
Big enough to detect the lift you care about, small enough not to give away much revenue. Many teams use 5–20% of the audience. The right size depends on three things: how many people enter the journey, the baseline conversion rate, and the smallest lift worth acting on. A small audience with a low baseline needs a larger holdout or a longer test.
Work it out before launch with a sample-size calculator and write down the answer. Then keep the test running until each group reaches that size.
- High-volume journeys (onboarding, abandoned cart) can use a small holdout and still reach a result quickly.
- Low-volume journeys (win-back for a niche segment) need a larger holdout or a longer window.
- Keep the same person in the same group for the whole test; reshuffling contaminates the result.
How do you calculate lift and its confidence interval?
Lift compares the treated group's conversion rate with the holdout's. If 6.0% of treated people convert and 5.0% of the holdout convert, the absolute lift is 1.0 percentage point and the relative lift is 20%.
A single number hides uncertainty, so add a confidence interval. For two conversion rates, a common approximation is: difference ± 1.96 × √(p₁(1−p₁)/n₁ + p₂(1−p₂)/n₂), where p is each group's rate and n its size. If the whole interval sits above zero, the journey very likely helps. If it crosses zero, you have not shown a lift yet, whatever the point estimate says.
In the example below, the interval runs from about −0.4 to +2.4 percentage points. It crosses zero, so even a 20% relative lift on paper is not yet proof: the holdout is too small to rule out no effect. These figures are illustrative, not from a client; run your own numbers through an A/B test calculator rather than by hand.
| Group | People | Converted | Rate |
|---|---|---|---|
| Treated (example) | 9,000 | 540 | 6.0% |
| Holdout (example) | 1,000 | 50 | 5.0% |
What mistakes ruin a holdout test?
The most common one is stopping early. If you check results every day and stop the first time they look significant, the false-positive rate climbs far above the 5% you think you are running. Evan Miller's classic explanation shows how repeated checking can push a nominal 5% significance level to over 25%. Decide the sample size in advance and wait for it.
Other mistakes: changing the journey halfway through the test, measuring a metric you picked after seeing the data, letting holdout users receive the same content through another channel, and sending holdout messages through the real sender. Platforms such as Customer.io handle the last one for you: holdout deliveries go to an internal message trap, so conversions can be compared without the email ever being sent.
Which journeys should you hold out first?
Start where the money and the doubt are biggest. Onboarding journeys are a good first test because they reach every new user and their goal, activation, is easy to measure within days. Win-back and discount journeys are the next priority, because they are the most likely to give value away to people who would have returned or paid anyway.
Leave transactional messages out of every test. Receipts, password resets, security alerts and anything a customer needs to use the product are not marketing and should always be sent. Also be careful with journeys that have legal or contractual obligations, such as renewal notices.
Once the first holdout has a clear answer, share it in plain terms: how many extra conversions the journey caused, what they were worth, and what it cost to run. That one result usually changes how a team talks about lifecycle marketing, from how many emails were sent to how much they added.
How do you turn a holdout result into a decision?
Translate the lift into money. Multiply the incremental conversions by the value of a conversion, subtract the cost of running the journey, and compare it with the next-best use of the same effort. A journey with a modest lift on a valuable action can beat a dramatic lift on a minor one.
Then keep a small permanent holdout on your most important journeys. Customer behaviour changes, and a journey that worked last year can quietly stop working. A standing holdout tells you when that happens.
Questions
What is the difference between an A/B test and a holdout test?
An A/B test compares two versions of a message. A holdout test compares a message with no message at all. A/B tests tell you which version is better; holdout tests tell you whether sending anything is better than sending nothing. Mature lifecycle programmes use both.
Is it bad to withhold emails from customers in a holdout?
The holdout only misses the messages being tested, usually a small share of the audience for a limited time. In exchange you learn whether the journey helps at all. If a journey is essential, such as a password reset or receipt, never hold it out.
How long should a lifecycle holdout test run?
Until each group reaches the sample size you calculated before launch, and long enough to cover the outcome you care about. For a seven-day activation goal, that means at least seven days after the last person enters the journey. Do not cut it short.
Can I run a holdout test in Customer.io?
Yes. Customer.io supports holdout tests in campaign workflows: you choose the share of the audience to hold out, and those deliveries go to an internal message trap so the platform can compare conversions without sending the email. You can also use a random cohort branch.
Sources




