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

Experiment Authoring

Showing 10

Add rule type property to decision object

While the decision object allows you to see which rule delivered a feature, it does not specify whether this rule is an A/B Test, Targeted Delivery, etc. Customer naming conventions could theoretically provide this kind of context, but we've recei...
2 months ago in Feature Experimentation / APIs / Experiment Authoring / Feature Flagging Workflows / SDKs & Agent 0 Future consideration

Let Editors create flag rules in production

It would be great if our Editor-level collaborators could create flag rules in the production environment. Particularly, because some of the experiments they create are going to be integrated with Contentful. And in Contentful, we want Editors to ...

In-rule definition and visibility of variables

In Feature Experimentation, the user has to create a variation and define variables before being able to select that variation (and thereby the variables) in a rule. This feature request is about the "in-rule definition and visibility of variables...

Be able to use preset values for flag variables

As experimentation program owners, we'd like our fellow developers and experimenters to input "safe" values when filling out flag variables. For example colors and font sizes that match our design system. A preset list of values (created by an adm...
10 months ago in Feature Experimentation / Experiment Authoring 1 Planned

Enable a batch of changes to be processed as an atomic transaction

As an experiment manager I want to be able to combine multiple configuration changes into single update so that clients cannot retrieve the data file in an inconsistent state (with only some of the changes applied) resulting in predictable applica...

CMS + FX

We need an integration between FX and CMS similar to the one Contentful has but better.
about 1 year ago in Feature Experimentation / Experiment Authoring 0 Investigating

Support for mobile devices/adaptive ui for feature experimentation

Currently only the latest version of the Desktop Chrome browser is supported for building experiments and campaigns within the Optimizely Experimentation app. But this is a limitation, as sometimes you need to configure feature flags on the go thr...
over 1 year ago in Feature Experimentation / Experiment Authoring 1 Future consideration

Grant Editors to have access to configure roll out rules in Production, while restricting them from configuring experiments

The goal is for us to make sure only members from the Experimentation Operations function can configure launch experiments in production, but the Product team can control roll outs in production.
about 2 years ago in Feature Experimentation / Experiment Authoring 0 Future consideration

Clone or copy experiment

It would be helpful to have a clone or copy functionality. This way it is much easier to setup an experiment that is similar to another one.
about 2 years ago in Feature Experimentation / Experiment Authoring 1 Already exists

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