Optimizely will be sunsetting Full Stack Experimentation on July 29, 2024. See the recommended Feature Experimentation migration timeline and documentation.

Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

Manage experiments

Use the Experiments dashboard in the Optimizely app to pause, archive, and change experiments.


Running in different environments

An experiment can run in multiple environments at a time.

To pause a running experiment, click the Actions icon (...). Choose Pause from the dropdown menu for the environment you want to pause. After pausing an experiment, all users will start to receive the original experience.


Pause a variation

Once you have started an experiment, you cannot delete a variation. However, you can pause variations instead, usually in order to troubleshoot them. When you pause a variation, traffic from that variation will be redistributed among the experiment's other variations, but the results will still be accessible for the paused variation.


Clicking Confirm alerts Optimizely to stop sending traffic to Var_1. However, the variation can be un-paused later by clicking Resume.

All previous results are still available for any resumed variations.


User profiles and sticky bucketing

Changing an experiment while it is running is not generally best practice. Pausing a variation is only necessary if you are using Optimizely's user profiles feature. User profiles allow Optimizely users to ensure variation assignments are sticky in any SDK. However, if you need to do so, then you will need to implement a user profile. For more information, see the user profile topic in the SDK guides for your language.

For example, if you add variations, change traffic allocation, or change total traffic allocation, then users _without _profiles often get rebucketed. For example, if you dialed back experiment traffic from 50% down to 10%, then increased it back to 50%, Optimizely would start from scratch and rebucket everyone. For more information, see How bucketing works.

If you are working with user profiles and want to ensure that a variation no longer receives any new traffic, you have two options:

  • Pause the variation, which ensures that it will no longer receive any traffic.
  • Set variation traffic distribution percentage to zero to ensure the variation will no longer receive new traffic. At the same time, users who have previously been exposed to the experiment will remain in their assigned variation.

If you have not implemented user profiles in the SDK, pausing a variation is no different than setting that variation's traffic distribution percentage to zero.

Archive an experiment

Archive an experiment to remove it from the Experiments dashboard. Optimizely keeps your experiment data, so you can unarchive the experiment later if you wish.

To archive an experiment, click the Actions icon (...) for the experiment and choose Archive from the dropdown menu.


Change experiment parameters



Be careful when you are changing experiment parameters, especially the experiment key and variation keys for a running experiment.

Do not change the experiment key or variation keys unless you are making the corresponding changes in your code. If you use a key that isn’t referenced in your code, no traffic will be sent to that experiment or variation.

You can change the experiment parameters, such as traffic allocation, variations, audiences, and events, directly in the Experiments dashboard.

  1. Click the experiment name to open it.
  2. Change your experiment parameters as desired.
  3. Click Save Experiment.

Changing your experiments will update your project’s datafile within a few seconds. It may take some time before your experiments are updated in production, depending on how often you retrieve datafile updates.

If you want your experiments to update in real-time, use webhooks to receive datafile updates.