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

Link back to the experiment on the results page on new FS UI

Hi team, there is no easy way to move between an experiment and the result at the moment. Customers need to keep both experiment and the result open in different tabs if they want to refer between both so they are asking for a link back in the res...
over 1 year ago in Feature Experimentation / Other 1 Already exists

Ability to customize the logger

Sixt has thousands of users and optimizely currently logs in unstructured manner. We would like to include some custom fields for each request that comes into our servers in order to facilitate easier logging, review and optimizely logs search. As...
over 1 year ago in Feature Experimentation / SDKs & Agent 1 Future consideration

Clinets request a way to differentiate experiment state (active, paused, archived, invalid)

This has been requested via FS swift-sdk github issues (https://github.com/optimizely/swift-sdk/issues/291) Currently SDK provides an error experimentKeyInvalid which says "Experiment key ((key)) is not in datafile. It is either invalid, paused, o...
over 1 year ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Handle the error the occurs when copying rules from another environment

When one environment already has an experiment in it, and you try to add a new rule by copying over the rules from another environment, the UI throws a confusing error that says "Updating production ruleset for flag <flagKey> failed. {"Inval...
almost 2 years ago in Feature Experimentation / Feature Flagging Workflows 1 Future consideration

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
about 2 years ago in Feature Experimentation / Experiment Authoring 1 Future consideration

On any listing page there should be sorting options

No description provided
about 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...
about 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...
about 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...
about 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 :(
over 2 years ago in Feature Experimentation 0 Future consideration