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 69 of 1586

Support for mobile devices/adaptive ui for feature experimentation

Currently only the latest version of the Desktop Chrome browser is supported for building experiments and campaigns within the Optimizely Experimentation app. But this is a limitation, as sometimes you need to configure feature flags on the go thr...
about 1 year ago in Feature Experimentation / Experiment Authoring 1 Future consideration

support SPM binaryTarget

See https://github.com/optimizely/swift-sdk/issues/478. Do you have any plan to support SPM binaryTarget? Like what https://github.com/airbnb/lottie-spm Lottie do or Facebook sdk https://github.com/facebook/facebook-ios-sdk/blob/main/Package.swift...
about 1 year ago in Feature Experimentation / APIs 1 Will not implement

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

Method to return if user is bucketed into an experiment

Create a method that returns a boolean to check if a user is in an experiment or not. Something similar to isFeatureEnabled, but for the whole experiment (for server side SDKs). I know that it could be built with some code, but having a simple isI...
about 1 year ago in Feature Experimentation / SDKs & Agent 1 Future consideration

Limit number of visitors for an experiment

Add the option to set up an absolute number of customers for an experiment or a variation. For example, an experiment supposed to be run only for the first 10000 visitors (instead of using the percentage).
about 1 year ago in Feature Experimentation / APIs 1 Will not implement

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...
about 1 year ago in Feature Experimentation / SDKs & Agent 4 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...
about 1 year ago in Feature Experimentation / Feature Flagging Workflows 0 Future consideration

Introduce distinct lexicon to distinguish between flag status and rule status (don't use on/off for both)

It is currently confusing to use the same terminology for both flags and the rules that control flags. For example, I can have a rule that is 'flag:off' but the rule in the list shows as 'on'. Suggestion would be to have different lexicon for rule...
about 1 year ago in Feature Experimentation / Feature Flagging Workflows 0 Future consideration

Type check for userId in Javascript (Browser/Node) SDKs

The customer (Yuliyan Yordanov from Tesco Stores) suggested a failsafe solution to reject empty string userId upon activating/enabling an experiment/feature: "A simple check for (typeof user_id ===’string’ && user_id.length ) would fix the...
about 1 year ago in Feature Experimentation / SDKs & Agent 1 Future consideration

Normalizing metrics

Groupon experimenters are looking for ways to normalize certain metrics. We need to have an ability to change the denominator for each metric. e.g Deal View CTR (deal view/total unique impressions) Session CVR (units/session) Deal Purchase CVR (Un...
about 1 year ago in Feature Experimentation / Other 0 Future consideration