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 1568

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

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...
almost 3 years ago in Feature Experimentation 10 Already exists

Support setting userAttribute through Optimizely agent environment variable.

We have an enhancement request for https://github.com/optimizely/agent?tab=readme-ov-file#configuration-options. We want to be able to add a property or an environment variable so that we can add a key-value pair for the userAttribute mentioned in...
4 months ago in Feature Experimentation 0

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

Feature: visionOS Support

No description provided
3 months ago in Feature Experimentation / SDKs & Agent 0

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...
3 months ago in Feature Experimentation / Feature Flagging Workflows 0

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

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...
over 2 years ago in Feature Experimentation / Feature Flagging Workflows 4 Already exists

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

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 ...
about 2 years ago in Feature Experimentation 0 Future consideration