Skip to content
ML Academy

Statistics, experimentation, causal reasoning · insight-1002

Check how well the pre-period predicts the metric before counting on CUPED to save traffic

Evidence type
documented fact
Difficulty
medium
Roles
Data scientist, Data analyst
Industries
e-commerce, saas, aviation

Summary: situation, action, reason, boundary

  1. Situation

    A test plan halves the duration "because we use CUPED", but the metric is first-visit conversion or the population is mostly new customers.

  2. Action

    Measure the correlation between the pre-period covariate and the in-test metric on past data, per segment. Expect a variance reduction near 1 minus the squared correlation and size the test with that factor. Where no history exists, adjust only for attributes known at assignment, such as market or device.

  3. Reason

    CUPED removes the part of the metric that pre-experiment data predict; without predictability there is nothing to remove.

  4. Boundary

    User-level metrics with a usable history, such as repeat bookers.

Symptom or risk

The covariate barely correlates with the outcome, or does not exist for new users, so variance hardly falls and the shortened test is underpowered.

Exceptions

Strongly persistent metrics, for example pre-period spend for loyalty members, where the gain can approach the reported order of magnitude.

Trade-offs

Extra pipeline complexity for a gain that may be small.

Pitfalls

Using a covariate measured after assignment, which can absorb part of the treatment effect.

Example

Hypothetical correlations: 0.3 cuts variance by about 9%, 0.7 by about 51%.

Lessons and concepts

Claims and their sources