Sarah Ager
Mar 30, 2026
visibility 1372
star star star star star
(0 votes)

Prove what your experimentation program is worth with Holdouts

Running experiments is one thing. Knowing whether your experimentation program is moving the business forward? That's the harder question. 

Most teams can point to individual test wins. A headline change that lifted click-through. A checkout flow that cut abandonment. But when leadership asks "what is all this experimentation worth?" the answer gets complicated fast. 

Today, that question gets a lot easier to answer. Holdoutis now available in Optimizely Feature Experimentation. 

Shape 

What Holdouts do 

Holdoutreserves a fixed percentage of your users from all running experiments. That group sees no test variants, no changes, nothing different. They're your global control. 

At the end of a measurement period, you compare what happened to the holdout group against everyone else. The difference is the net lift of your entire experimentation program. Not one test. All of them. 

It's the cleanest answer to the question every experimentation leader eventually faces: "What would have happened if we hadn't run any experiments at all?" 

Shape 

Why it matters for mature programs 

If you're running multiple experiments concurrently, individual test results only tell part of the story. Experiments interact. Variants overlap. And without a clean baseline, you're measuring performance against a constantly shifting target. 

 

Holdoutfix that. It gives you an unbiased comparison point that sits outside your test traffic. The result is a measurement you can take to leadership with confidence. 

 

Not a collection of test summaries. A defensible number that answers the question your CFO is asking. 

Shape 

Built for the programs that need it most 

This feature is designed for teams running at scale. If you're running a handful of experiments a year, individual test metrics serve you well. But if your program spans multiple teams, products, and concurrent tests, Holdout Groups gives you the program-level view you've been missing. 

And it works alongside your existing setup. No changes to individual experiments. No disruption to running tests. Just an additional layer of measurement that sits above everything you're already doing. 

Shape 

What you can do now 

Create a Holdout group in your Flags > Holdouts tab. Set your holdout percentage, select what metrics to measure like Overall Revenue, what Audience, and this holdout will get added to your next experimentation based on the criteria. (I typically recomennd holding back between 1-5% of your traffic). Your next leadership review can include a number that answers the question that matters: what is our experimentation program delivering? 

 

For a full explanation of how holdoutwork, see the Holdouts Glossary Page. 

 

 

Mar 30, 2026

Comments

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |