Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

ADD FEEDBACK

Feature Experimentation

Showing 68 of 1573

Filtering for conversions by whitelisted users

Conversions from whitelisted users are useful for debugging and QA. They can however be distorting results from live data - especially on low total conversion metrics. Optimizely could mark the events in the moment of processing and offer an easy ...
over 2 years ago in Feature Experimentation 0 Future consideration

Set Seed of Experiment Allocation

It would be helpful to set the seed of traffic allocation so that you know the same user (same user ID) would be in the same variation on both experiments. Essentially the distribution of V1 vs V2 would be the same numbers (between 0-10000) in bot...
over 2 years ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Intelligent Rollback and Deploy (Experiments + Features)

No description provided
almost 3 years ago in Feature Experimentation 0 Future consideration

Folders for Full Stack Features

Currently using an in-house tool for feature flags and have over 2200 live at any give time. Projects help organize these, but would like to have another layer of organization (such as folders).
almost 3 years ago in Feature Experimentation 0 Future consideration

Method to return if user is bucketed into an experiment

Create a method that returns a boolean to check if a user is in an experiment or not. Something similar to isFeatureEnabled, but for the whole experiment (for server side SDKs). I know that it could be built with some code, but having a simple isI...
about 1 year ago in Feature Experimentation / SDKs & Agent 1 Future consideration

Limit number of visitors for an experiment

Add the option to set up an absolute number of customers for an experiment or a variation. For example, an experiment supposed to be run only for the first 10000 visitors (instead of using the percentage).
about 1 year ago in Feature Experimentation / APIs 1 Will not implement

Using standard "off" variation multiple times.

This feedback is on behalf of Vistaprint. - Mauricio Acebal and Lukas Vermeer. This feedback is related to the special treatment of the standard "Off" variation. Vistaprint are happy they are capable of turning off a variation without changing tra...
about 1 year ago in Feature Experimentation / Feature Flagging Workflows 0 Future consideration

More intuitive design for managing features

I would like to add a few suggestions on behalf of Busra from Mural regarding a more intuitive design for managing features in our legacy platform: Have radio buttons instead of the "Status" drop-down menu on the Features tab Should not be able to...
over 1 year ago in Feature Experimentation / Feature Flagging Workflows 1 Future consideration