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 75

Add "name" field to FeatureFlag object in datafile

I would like to ask if it’s possible to add a "name" field to the FeatureFlag object in in datafiles/xxxxx.json which is having all the configured feature flags there. To give some more context on the structure I’m talking about: { ... "featureFla...
9 days ago in Feature Experimentation / Other 0

Serve previous revisions of datafiles from Optimizely CDN

As a web developer I need to ensure that every point in a request lifecycle uses the same version of an Optimizely datafile to ensure a page is rendered correctly. This includes: edge function logic serverside render clientside hydration If there ...
4 months ago in Feature Experimentation / APIs 0

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...
2 months ago in Feature Experimentation / APIs / Experiment Authoring / Feature Flagging Workflows / SDKs & Agent 0 Future consideration

add filter option in the "List Experiments" endpoint

Vistaprint: Add support for filtering "archived" in the List Experiments endpoint. we already have to paginate to get all active experiments even though we only have less than 10 active, I can see this being a problem as time goes on."
over 2 years ago in Feature Experimentation / APIs 3 Future consideration

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...
about 1 year ago in Feature Experimentation / Project / Account Configuration / Settings 1 Planned

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.
about 1 year ago in Feature Experimentation / Other 2

One-click cleanup for obsolete Audiences/Events/Experiments

The GUI tends to get cluttered (at the same time blowing up the datafile). It would be great to have an option to automatically archive elements that are beyond a certain threshhold - such as experiments that are stopped for +6 months, Audiences/a...
11 months ago in Feature Experimentation / Project / Account Configuration / Settings 2 Future consideration

Full Stack with Flutter

Many Customer's mobile team is getting started with experimentation and would like to utilize our SDK with Flutter (a cross-platform mobile framework that is written in the Dart programming language but is compiled to swift (for iOS) and java (for...
over 3 years ago in Feature Experimentation 10 Already exists

Full Stack tests show as an ID number instead of Experiment Name.

Expected Experience Full stack tests should be reported using Flag Names and not flag id numbers on https://app.optimizely.com/v2/accountsettings/account/usage . Makes review difficult. Actual Experience (please describe what you see): For the acc...
over 2 years ago in Feature Experimentation / Project / Account Configuration / Settings 1 Future consideration

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

Currently, I can dynamically update user context but not the datafile. I can only configure time intervals on how often sdk itself will refresh the datafile itself.It's very limiting and I need more control over datafile updates. I suggest to impl...
over 1 year ago in Feature Experimentation / SDKs & Agent 4 Future consideration