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 74 of 1806

Add possibility to define Variations directly within a Rule

Currently, Variations are created separately. It should be similar to Page targeting settings in Web, which also can be defined separately and reused, OR defined directly in the experiment
over 2 years ago in Feature Experimentation / Experiment Authoring 1 Future consideration

On any listing page there should be sorting options

No description provided
over 2 years ago in Feature Experimentation 1 Future consideration

On the Results page, the Name of the Flag that an experiment is based on should be displayed

Currently, only the "Rule key" is displayed, not the Flag name or key. The Rule keycan include the name (/key) of the Flag, but it doesn't have to. So especially when having multiple Results pages open side by side, it's very difficult to distingu...
over 2 years ago in Feature Experimentation 1 Future consideration

Make React SDK Provider less brittle

React SDK provider should just be a context provider with its own useOptimiselyContext hook for getting and setting context. If setting the client and user id were separated either with their own functions or even when initialising context somehow...
over 2 years ago in Feature Experimentation 0 Future consideration

Notification listeners - send data to analytics reporting only experiment decision data, NOT everyone that was evaluated for the flag.

(SDK 4.0) Considering an experiment which is set on top of a flag with only % of traffic being assign to it, the 'leftovers' (users not assigned) receive the same control experience as assigned in expriment (flag/variant = Off). Because of this, w...
over 2 years ago in Feature Experimentation 0 Future consideration

Being able to see experiment data before the last reset

This would give more transparency about the development of an experiment. Now the data is simply gone :(
almost 3 years ago in Feature Experimentation 0 Future consideration

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 ...
almost 3 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...
about 3 years ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Intelligent Rollback and Deploy (Experiments + Features)

No description provided
over 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).
over 3 years ago in Feature Experimentation 0 Future consideration