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 68 of 1571

GCP Cloud Functions + Edge SDK

Since we are now on Google Cloud a customer has asked us about the possibility of Edge functions similar to AWS Lambda for GCP
11 months ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Bounce/exit metrics in Optimizely Full Stack

Bounce and exit rate are key metrics for our business, as they often reach statistical significance and are crucial for us as an indication of experiment performance. At present, these metrics are only available in the Optimizely Web product and n...
almost 2 years ago in Feature Experimentation / Other 1 Future consideration

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
5 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.
6 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.
7 months ago in Feature Experimentation / Experiment Authoring 0 Investigating

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.
over 2 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 ...
almost 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...
over 1 year 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 1 year ago in Feature Experimentation / SDKs & Agent 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...
11 months ago in Feature Experimentation / Feature Flagging Workflows 0 Future consideration