Synchronizing Multiple Feature Launches
Coordinate a synchronized launch across multiple Statsig feature gates and experiments so related changes go live atomically to a defined audience.
Synchronize multiple Statsig feature gates so related features launch together as a single release. You create a release gate, then add a "Passes Target Gate" condition to each feature gate so they follow the release gate's rollout. Flip the release gate when you're ready, and every dependent feature goes live at the same percentage. This approach needs no code or development workflow changes.
Launching Features 1 and 2 as part of Release A
Say you're working on Features 1 and 2. An engineer has created Feature Gates for each one: Feature 1 and Feature 2. You roll out each feature only to internal stakeholders while implementation is ongoing.
Later, you decide you want these two features to launch at the same time as part of Release A.
First, create your release gate: Release A. Because you aren't launching yet, leave the release gate returning false for everyone.
Next, make Feature 1 and Feature 2 gates depend on Release A by adding a “Passes Target Gate” condition at the top. “Passes target gate” means: if the listed gate passes, also pass for this gate. Set the pass percentage to 100 so that anyone passing the release gate also passes each feature gate. The release gate still fails, so your features remain unavailable to anyone outside your existing gating conditions.
After you configure both gates, you can continue developing until you're ready to launch.
When you're ready to launch, each of your features depends on the “Release A” gate. Change that gate to pass for the percentage rollout you want.
For example, to roll out to 10% of your user base and check the associated pulse metrics, create an “Everyone, 10%” rollout. The release gate warns you at the top that Feature 1 and Feature 2 depend on it.
Now, checks in code for Feature Gate A and Feature Gate B pass 10% of the time. You can measure the combined impact of these changes together in the pulse view for the Release A gate.
Advanced rollout with Pulse
To measure the impact of these features independently, add a partial rollout on Feature Gate A, Feature Gate B, and the release gate. This lets you compare Feature 1 vs Control, Feature 2 vs Control, and Feature 1 & 2 vs Control. You can't compare Feature 1 vs Feature 2, and Statsig doesn't enforce mutual exclusion between Features 1 and 2. For those comparison types or for mutual exclusivity, go to Experiments.Was this helpful?