Governance and strategy
Feature Experimentation FAQs
Optimizely Feature Experimentation Optimizely Feature Experimentation is feature management and A/B testing for product teams. Feature flags and targeted deliveries help launch features safely and give you a kill switch if unanticipated issues arise.
Change approvals in Feature Experimentation
Optimizely Feature Experimentation Change approvals improve control and reduce risk in software releases by requiring a review of feature flag changes before they launch. Approvers review each change before it goes live.
Change history in Feature Experimentation
Optimizely Feature Experimentation Optimizely Feature Experimentation logs actions performed for a project and for a flag, such as creating an event, modifying a rule, and adding and removing audiences. These actions are listed in the change history, which displays the record of user activity for each of your projects and flags .
Mutually exclusive experiments in Feature Experimentation
Optimizely Feature Experimentation In Optimizely Feature Experimentation, experiments may overlap, exposing a single user to multiple experiments simultaneously. Mutually exclusive ..
Global holdouts
Global holdouts help you accurately measure the true impact of your A/B testing and experimentation efforts. You designate a small percentage of users as a control group, ensuring they do not experience any experiments or new feature rollouts.
Local holdouts
Local holdouts extend Optimizely global holdout capabilities. A global holdout applies to one or more entire projects.