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 10 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

FILTER BY CATEGORY

Feature Experimentation

Showing 47 of 1007

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...
7 months ago in Feature Experimentation / SDKs & Agent 0

Consider turning on Auto Minify on CloudFlare to decrease blocking time

Our pages are being marked as having extremely slow loading times and having high blocking. As a result, Google PageSpeed Insights views our pages as a "bad experience" for the user. While we work on optimizing, if the Auto Minify feature were tur...
9 months ago in Feature Experimentation / Other 0

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...
10 months ago in Feature Experimentation / Feature Flagging Workflows 0

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
12 months ago in Feature Experimentation 0

On any listing page there should be sorting options

No description provided
12 months ago in Feature Experimentation 0

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...
12 months ago in Feature Experimentation 0

When you create a new flag rule it should not default to ON

Currently, as soon as the rule is created, it's ON, even though in many cases, it's not completely ready/configured yet, and needs more adjustments before it should be enabled. So the current workaround when creating a Rule is to pull down the sli...
12 months ago in Feature Experimentation 0

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 1 year 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 1 year ago in Feature Experimentation 0

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 1 year ago in Feature Experimentation 0