Skip to Main Content
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 63 of 1504

Roku SDK

No description provided
over 2 years ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Workflow approval

Clients wants to be able to have an approval workflow before a flag or test is started. They do this because they want to ensure that someone needs to get approval before changing the configuration of a flag to ensure a second pair of eyes before ...
over 2 years ago in Feature Experimentation 0 Future consideration

Manage Collaborators via API

Customers wants to manage collaborators via REST api, so that they can programmatically grant permissions via their existing permissioning tool that they've created. They do this because it's far more convenient for them to manage this in a centra...
over 2 years ago in Feature Experimentation 0 Future consideration

Event tags to segment results and create metrics- Segment integration

Customers wants to create Optimizely events via Segment. They do this because they already have evnts in Segment and then data is nicely aligned. They wish that Optimizely had the option to filter results by event tags and use the atgs to create m...
over 2 years ago in Feature Experimentation 0 Future consideration

Option to change the variants order in Flags

In Flags, it is not possible to change the order of variants and have a different “Baseline” variation by default in the Results Page. Regardless the possible workaround (change the baseline variation from the results page), the proper behaviour w...
over 1 year ago in Feature Experimentation / Project / Account Configuration / Settings 0 Future consideration

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