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 52

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
about 1 year ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Allow results metrics to measure conversions per session

Optimizely FX customers should have the option to be able to measure their conversions (and revenue) against the number of user sessions, rather than just against unique visitors. This could potentially work similarly to how Personalization Campai...
about 1 year ago in Feature Experimentation / Project / Account Configuration / Settings 1 Future consideration

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...
8 months ago in Feature Experimentation / Project / Account Configuration / Settings 0 Future consideration

Feature Flag Lifecylcle Analytics

One of my goals as an administrator of feature flags is to understand the lifecycle of our feature flags. When it was created and the various data points for it's rollout. I struggle to maintain the lifespan of our flags without alot of manual work.
about 3 years ago in Feature Experimentation / Feature Flagging Workflows 1 Future consideration

Supporting Custom Javascript or some inbuilt functions in the Audience Builder

We would like to be able to perform some minimal data manipulation before matching when creating audiences. Either supporting custom javascript in Audience Builder in the Full Stack version, or accommodating common Javascript or optimizely custom ...
over 2 years ago in Feature Experimentation / SDKs & Agent 0 Future consideration

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...
almost 2 years ago in Feature Experimentation / SDKs & Agent 1 Future consideration

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

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