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

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

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

Auto Maintenance Page when origin server is not reachable

It will be good to have a maintenance page or custom error page automatically put up when origin server is not reachable e.g. 403, 502, 503 error response. So that user are not just seeing a genric error page which may impact business image.
7 months ago in Feature Experimentation / Other 2

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

Archive Unused Rules (vs deleting them)

From a customer: The options are only to “Move To Top, Duplicate or Delete”. One does not necessarily want to delete past rules, in case one wants to re-use them or use them to duplicate them to create a slightly different rule etc. Therefore, the...
9 months ago in Feature Experimentation / Feature Flagging Workflows 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...
10 months ago in Feature Experimentation / Feature Flagging Workflows 0 Future consideration

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
10 months ago in Feature Experimentation / SDKs & Agent 0 Future consideration

enable optimizely node sdk to work behind proxy

If sdk is meant to be initialised in air tight environment and you are meant to use proxy for security and audit reasons, then its impossible to do so with createInstance method from neither react nor node SDKs. Datafile wont be fetched, App will ...
12 months ago in Feature Experimentation / SDKs & Agent 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...
12 months ago in Feature Experimentation / Experiment Authoring 1 Future consideration