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 66 of 1542

Enhanced Datafile Management

Submitting on behalf of the customer. In order for us to easily debug datafile issues, for the Optimizely datafile, provide an easy way for us to retrieve the below information through the UI instead of having to reach out to Optimizely support: A...
9 days ago in Feature Experimentation / Project / Account Configuration / Settings 0 Future consideration

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...
17 days ago in Feature Experimentation / Experiment Authoring 1 Future consideration

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

Feature: visionOS Support

No description provided
about 2 months ago in Feature Experimentation / SDKs & Agent 0

One-click cleanup for obsolete Audiences/Events/Experiments

The GUI tends to get cluttered (at the same time blowing up the datafile). It would be great to have an option to automatically archive elements that are beyond a certain threshhold - such as experiments that are stopped for +6 months, Audiences/a...
about 2 months ago in Feature Experimentation / Project / Account Configuration / Settings 1 Future consideration

Error Application Log: Failed to determine user's country. Error message: Invalid URI: The format of the URI could not be determined.

There are a bunch of error application logs saying " Failed to determine user's country. Error message: Invalid URI: The format of the URI could not be determined. " when the geocoding settings are not provided. These error messages should be prev...

Support setting userAttribute through Optimizely agent environment variable.

We have an enhancement request for https://github.com/optimizely/agent?tab=readme-ov-file#configuration-options. We want to be able to add a property or an environment variable so that we can add a key-value pair for the userAttribute mentioned in...
3 months ago in Feature Experimentation 0

Support OpenFeature

As a developer I want to be able to use an Optimizely provider for the CNCF OpenFeature project so that I don't have to learn a vendor-specific SDK to integrate my codebase with Optimizely resulting in faster adoption of Optimizely in my applications
4 months ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Confirmation When Archiving Flag

Is it possible to have a confirmation box, or at least the option of enforcing one, when archiving/deleting a flag? I noticed that flags can easily be archived by mistake, and can be a breaking experience on the website.
5 months ago in Feature Experimentation / Feature Flagging Workflows 0 Planned

Feedback from a POC customer on usability

Here is some feedback I got from someone who's running a POC of Feature Experimentation. Frustrating that Development environment is chosen by default when clicking a Flag. This person has made changes to the wrong environment many times before re...