Frequently Asked Questions

A curated summary of the top questions asked on our Slack community, often relating to implementation, functionality, and building better products generally.
Statsig FAQs

How to configure holdouts to measure the impact of different product teams?

To measure the cumulative impact of different product teams' work, you can create separate holdouts for each team. Here's how you can do it:

1. Navigate to the Holdouts section on the Statsig console.

2. Click the "Create New" button and enter the name and description of the holdout that you want to create for the first team.

3. Select a Holdout size in terms of a percentage of all users. A small holdout percentage, typically between 1% and 5%, is recommended.

4. If there are any existing features that are already gated by the first team, you can select those gates at the bottom to make sure they respect the holdout moving forward.

5. Repeat the process to create a separate holdout for the second team.

Remember, you should not make these holdouts global. Instead, each team should add their gates/experiments/etc to their appropriate holdout as they create them. If there are gates/features that should be attributed to both teams, you can add that gate to both holdouts - and it will just keep out the union of their holdout audiences.

The percentage you set your holdout at will depend on how many users you expect to be impacted by the changes of each team. General guidance is in the neighborhood of 1-5%, but you can use the power analysis calculator to generate some intuition if you’re already logging those KPI metrics.

For further information, you can refer to the following resources:

- Getting in on Holdouts - Statsig Holdouts Documentation - Power Analysis Calculator

Join the #1 Community for Product Experimentation

Connect with like-minded product leaders, data scientists, and engineers to share the latest in product experimentation.

Try Statsig Today

Get started for free. Add your whole team!

What builders love about us

OpenAI OpenAI
Brex Brex
Notion Notion
SoundCloud SoundCloud
Ancestry Ancestry
At OpenAI, we want to iterate as fast as possible. Statsig enables us to grow, scale, and learn efficiently. Integrating experimentation with product analytics and feature flagging has been crucial for quickly understanding and addressing our users' top priorities.
Dave Cummings
Engineering Manager, ChatGPT
Brex's mission is to help businesses move fast. Statsig is now helping our engineers move fast. It has been a game changer to automate the manual lift typical to running experiments and has helped product teams ship the right features to their users quickly.
Karandeep Anand
At Notion, we're continuously learning what our users value and want every team to run experiments to learn more. It’s also critical to maintain speed as a habit. Statsig's experimentation platform enables both this speed and learning for us.
Mengying Li
Data Science Manager
We evaluated Optimizely, LaunchDarkly, Split, and Eppo, but ultimately selected Statsig due to its comprehensive end-to-end integration. We wanted a complete solution rather than a partial one, including everything from the stats engine to data ingestion.
Don Browning
SVP, Data & Platform Engineering
We only had so many analysts. Statsig provided the necessary tools to remove the bottleneck. I know that we are able to impact our key business metrics in a positive way with Statsig. We are definitely heading in the right direction with Statsig.
Partha Sarathi
Director of Engineering
We use cookies to ensure you get the best experience on our website.
Privacy Policy