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

Being able to see experiment data before the last reset

This would give more transparency about the development of an experiment. Now the data is simply gone :(
over 2 years ago in Feature Experimentation 0 Future consideration

Filtering for conversions by whitelisted users

Conversions from whitelisted users are useful for debugging and QA. They can however be distorting results from live data - especially on low total conversion metrics. Optimizely could mark the events in the moment of processing and offer an easy ...
over 2 years ago in Feature Experimentation 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 ...
over 2 years ago in Feature Experimentation 1 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.
over 2 years ago in Feature Experimentation / Feature Flagging Workflows 1 Future consideration

Set Seed of Experiment Allocation

It would be helpful to set the seed of traffic allocation so that you know the same user (same user ID) would be in the same variation on both experiments. Essentially the distribution of V1 vs V2 would be the same numbers (between 0-10000) in bot...
over 2 years ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Streaming Datafiles

Offer an option to consume datafiles immediately when updated via websocket or other streaming architecture. This would enable faster updates to flags and bring us into parity with competitors.
almost 3 years ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Roku SDK

No description provided
almost 3 years ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Intelligent Rollback and Deploy (Experiments + Features)

No description provided
almost 3 years ago in Feature Experimentation 0 Future consideration

Folders for Full Stack Features

Currently using an in-house tool for feature flags and have over 2200 live at any give time. Projects help organize these, but would like to have another layer of organization (such as folders).
almost 3 years ago in Feature Experimentation 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 ...
almost 3 years ago in Feature Experimentation 0 Future consideration