Claim and evidence
Adjust each user's metric with their pre-experiment data to cut noise and reach conclusions faster.
No dated example yet. Treat this tactic as a hypothesis.
Vendor claim
A tool vendor reports numbers about its own customers or product. Useful, but not independent.
Working · 2026-11 On by default in Statsig Cloud; also in GrowthBook for both engines.
What the numbers show
No published number for this tactic has passed our word-for-word check yet, so there is no chart.
Why it works
Part of each user's behavior is predictable from before the test. Removing it shrinks variance, so a smaller effect is detectable with the same traffic.
How to run it
- Enable pre-exposure data in the platform
- Choose a pre-exposure window (7 days is common)
- Handle users without history
- Check results with and without adjustment
- Document the setting
Ways to run it
Design options to test, not promised results.
- Option APlatform setting
Turn on pre-exposure adjustment in the experimentation platform and document the window used.
- Option BNew-user handling
Decide how to treat users with no history, since they gain nothing from the adjustment.
- Option CSide-by-side readout
Report results with and without adjustment so reviewers can see what it changed.
Timeline
- 12013 first documented: Deng, Xu, Kohavi and Walker, as cited by Statsig
- 22026-11 status checked: Working
Dated examples
No dated example yet. Treat this tactic as a hypothesis.
Does it still work?
On by default in Statsig Cloud; also in GrowthBook for both engines. source
Risks
- Little gain for new users with no history
- Needs reliable pre-period data
Sources
- docs.statsig.com
“reduces a metric's variance by adjusting each user's metric value with that user's pre-exposure data.”
✓ quote checked word-for-word on the page - docs.growthbook.io
“In fact, tools like CUPED are available for both engines.”
✓ quote checked word-for-word on the page
Change log
- 2026-11-20 — harvest v0.1 (ops-ai)