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 70 of 1642

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

Feature: visionOS Support

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

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

CMS + FX

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

Use human language on key experiment changes

We want to quickly find the dates of an experiment starts, ends, ramp-up percentage changes, so that we can keep track of the changes made in the experiment. Currently in the history, only the code changes are listed and we have to read through th...
about 1 year ago in Feature Experimentation / Feature Flagging Workflows 0 Future consideration

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

support SPM binaryTarget

See https://github.com/optimizely/swift-sdk/issues/478. Do you have any plan to support SPM binaryTarget? Like what https://github.com/airbnb/lottie-spm Lottie do or Facebook sdk https://github.com/facebook/facebook-ios-sdk/blob/main/Package.swift...
about 1 year ago in Feature Experimentation / APIs 1 Will not implement