CUPED for Faster Experimentation in GrowthBook

CUPED is now available for the Frequentist engine in GrowthBook 2.0!

· 4 min read
CUPED for Faster Experimentation in GrowthBook
The figure above shows the decreasing p-values and confidence intervals in the GrowthBook UI when CUPED is enabled.

There are many ways to improve the speed of your experimentation program. One of the easiest is variance reduction via regression adjustment, often called CUPED (short for Controlled Experiment Using Pre-Experiment Data).

To get started using CUPED with GrowthBook, head over to our documentation.

How does it work?

There are many blog posts and papers on how CUPED works to increase experiment velocity. These are excellent resources that include motivation, intuition, code examples, and evidence of impact.

Rather than re-hash the nitty-gritty, let's focus on a high-level example:

Imagine you're running an experiment that looks to increase sales in your online store. You release a new feature in the checkout experience and measure the total value of all purchases by each user. Some users will make large purchases, others small purchases, others make no purchases. In your experiment analysis, you'll average purchase analysis across all of these users in variation A and B and compare them.

Because these users are so different, you are going to have a lot of uncertainty about the average. However, imagine you knew how much each user spent on your site in the month before the experiment. CUPED lets you use that information to adjust purchasing behavior during the experiment, taking away the part that can be easily explained by past behavior!

You can read more about our exact implementation and how it works in our documentation. In a nutshell, we fit a very simple linear model using this pre-experiment (or pre-experiment exposure) data and use it to adjust post-exposure data, reducing the variance of that post-exposure data.

How can you make the most of CUPED?

Measure experiment effects on leading metrics

To best take advantage of CUPED, make sure to estimate effects on predictablerepeated metrics that are leading indicators of key metrics. The more predictable metrics will likely benefit from greater variance reduction.

Why? The correlation between pre- and post-exposure data for metrics that users generate less frequently will tend to be lower. Using our example above, if we don't have reliable historical purchase data for users, then that data won't provide a big advantage in reducing variance. However, if we know how many items a user looks at on our site on each visit, that might be a leading indicator for purchasing and may be more highly correlated over time.

The below figure shows a visual example of the difference in variance reduction from CUPED for different levels of correlation between pre- and post-exposure data. Variance reduction is the difference between the orange and the green distributions; the smaller spread of the green distribution shows how we have reduced variance after using CUPED to adjust metric values. You can see that the variance reduction is greater in the right panel, where the correlation is 0.7.

Correlation will tend to be higher for more frequent metrics, like engagement metrics, than more infrequent metrics, like purchase behavior, and thus CUPED will do more to improve analyses of those more frequently produced metrics.

This advice is not unique to CUPED; the idea of using leading metrics to get faster answers from experiments is widespread. It's just good to note that the value of leading metrics is increased by the availability of CUPED.

Understand your metric behavior and set the right lookback window

GrowthBook uses a (customizable) 14-day lookback window; this is the amount of time before a user is exposed to an experiment that we use to compute their pre-experiment metric totals. The following figure shows you how this works for users that are exposed to the experiment at two different time periods.

We will roll up the green days and use it as the pre-exposure measure to adjust the data from the blue days (post-exposure data).

GrowthBook is highly customizable; you can adjust this lookback window (the green area) using the CUPED settings and you can adjust the post-exposure conversion window (the blue area) using Conversion Windows and Conversion Delays.

We recommend understanding your metrics to learn whether there is enough user behavior at regular cadences to use this 14-day window, or if you need to set a longer lookback window. If the events are rare, you may find that setting a larger lookback window is more beneficial for variance reduction.

Collect data early

Set up and collect metric data before you start experimenting. CUPED only works if you have data on your users from the period before your experiment starts. If you start collecting data as early as you can, then you're more likely to have data available for CUPED to work with.

Sadly, this means that CUPED will not work well for experiments on new users or for metrics that are only collected after experiment exposures happen.

In those instances, you are free to use the customizable settings in GrowthBook to turn CUPED off for an experiment or an individual metric. While leaving CUPED on will rarely make your variance worse, it does require scanning more days of your metric source, and turning it off for metrics that it cannot help could improve query performance.

What's next?

More sophisticated adjustment
Initially, GrowthBook only uses the pre-exposure data of the analysis metric for regression adjustment, but future refinements to incorporate dimensional data, auxiliary metrics, and more complex models are possible.

With great power, comes great responsibility
CUPED enables faster experimentation, but it does not resolve the "peeking" problem (for a discussion of this in both the Frequentist and Bayesian framework, see: In Q2 of 2023, GrowthBook will be adding sequential testing to the Frequentist engine to help mitigate the problem with and without CUPED.

Read next

Want to give GrowthBook a try?

In under two minutes, GrowthBook can be set up and ready for feature flagging and A/B testing, whether you use our cloud or self-host.