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

My feedback: Feature Experimentation

Showing 75 of 1837

Feature: visionOS Support

No description provided
11 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...
11 months ago in Feature Experimentation / Feature Flagging Workflows 0

Logger having error categorised into types

The Optimizely logger indicates different types of errors. Our client suggests to divide the different types of errors by type. Example use case: our client is currently using a Regex to identify the error messages received for the error "not in d...
about 2 years ago in Feature Experimentation / SDKs & Agent 1 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.
about 1 year ago in Feature Experimentation / Feature Flagging Workflows 0 Planned

Batch Decisions for Bulk User IDs

Customers who desire to use Full Stack as part of their experimentation program for batch activities such as email sends, SMS, or push notifications would benefit from having a single method call in the SDK that can accept an array or list of user...
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 3 years ago in Feature Experimentation 0 Future consideration

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

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...
over 1 year ago in Feature Experimentation / Feature Flagging Workflows 0 Future consideration

Optimizely should use standard v3 Nuget feed.

We raised a support ticket regarding Optimizely Nuget feed v2 not being compatible with Artifactory which support the industry standard v3 feed by default. Our use case was explained that for security reasons we cannot download new nuget packages ...
about 3 years ago in Feature Experimentation 1 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...
over 1 year ago in Feature Experimentation / Experiment Authoring 1 Future consideration