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 Flagging Workflows

Showing 14

Add rule type property to decision object

While the decision object allows you to see which rule delivered a feature, it does not specify whether this rule is an A/B Test, Targeted Delivery, etc. Customer naming conventions could theoretically provide this kind of context, but we've recei...
about 1 month ago in Feature Experimentation / APIs / Experiment Authoring / Feature Flagging Workflows / SDKs & Agent 0 Future consideration

Apply Audience Automatically At The Project Level

As an experimenter I would like to be able to have an audience auto populate for an entire project. The bot filtering provided within Optimizely does not exclude additional bots that we need to remove from testing as an organization, and therefore...

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

Full Stack Experiment Scheduler

What is the problem you’re trying to solve with this request?Rather than providing a solution, please try to describe the problem in as much detail as possible. Calendar Experiment scheduling - on and off Repeatability Weekly, Monthly, Yearly, Cus...
about 3 years ago in Feature Experimentation / Feature Flagging Workflows 4 Already exists

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

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

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

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

Request for low level api method to manually update datafile in javascript/react sdk

Currently, developers can't manually update datafiles. They can only configure time intervals on how often the SDK will refresh the datafile itself. Some feel this is very limiting and I need more control over datafile updates. Request to implemen...
over 1 year ago in Feature Experimentation / Feature Flagging Workflows 1 Future consideration

Option to remove percentage roll out for simpler flag management

We are exploring using Optimizely to manage critically important feature flags. Sometimes, a flag needs to be turned off instantly, out of hours or by Ops personnel eg in the event of an outage of service. In these instances, we want increased con...
over 1 year ago in Feature Experimentation / Feature Flagging Workflows 0 Future consideration