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 52

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

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

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

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

When adding multiple audiences to a rule, don't default to matching ANY

When you add multiple audiences to a new rule, the default is to match ANY of the selected audiences. We always want to match ALL of the selected audiences, but our users often forget to change ANY to ALL. They put their experiment live and don't ...
over 2 years ago in Feature Experimentation 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 ...
over 1 year ago in Feature Experimentation / SDKs & Agent 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
over 1 year 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...
over 2 years ago in Feature Experimentation / Other 1 Future consideration