Skip to content

Update Rollouts-and-experiments.mdx #439

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update Rollouts-and-experiments.mdx #439

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 12 additions & 3 deletions docs/faq/Rollouts-and-experiments.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,18 @@ See the [Rollout FAQ](/deep-dives/experimenter/rollouts) for general rollout inf
Can a client be in a rollout and an experiment for the same feature at the same time?

### Answer
**Yes**, we have separate namespaces which means you can run rollouts and experiments simultaneously and each namespace does its
accounting for users separately.
You can run a 100% rollout and a 5% experiment and both will fill up, but everyone in the experiment is also in the rollout.
**Yes**, we have separate namespaces which means you can run rollouts and experiments for the same feature simultaneously and each namespace does its accounting for users separately.
You can run a 100% rollout and a 5% experiment and both will fill up, but everyone in the experiment is also in the rollout. When a user is in both an experiment and a rollout for the same feature - they will get see the experiment. When the experiment ends - the rollout will apply.

The rules:
- Users can be in only 1 experiment for each feature at a time.
- Users can only be in 1 rollout for each feature at a time.
- Users CAN be in multiple experiments + rollouts on DIFFERENT Features.

After 100% of users are in a Feature Rollout - users will not enroll for new rollouts for that same feature. New Experiments or rollouts that launch (when their feature's experiment or rollout respectively is at 100%) will see low to no enrollment.


<img width="219" alt="image" src="https://github.com/mozilla/experimenter-docs/assets/8192232/ea351529-9b2b-446c-a671-2eb4d203dae0">

----

Expand Down