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

JavaScript SDK handles large datafiles in a performant manner. It is possible to process large datafile initialisation on a web worker.

The javascript SDK client initialises the client form the datafile. When the datafile is large, processing the JSON takes a long time. P50 20ms and P75 already gives 70ms. This is significantly long when considering page load time. It would be ben...
almost 2 years ago in Feature Experimentation / SDKs & Agent 1 Future consideration

Grant Editors to have access to configure roll out rules in Production, while restricting them from configuring experiments

The goal is for us to make sure only members from the Experimentation Operations function can configure launch experiments in production, but the Product team can control roll outs in production.
about 2 years ago in Feature Experimentation / Experiment Authoring 0 Future consideration

Error message about number of characters in the rule

When creating a new flag, and adding a rule (for example Targeted delivery), the name of the rule key can be maximum 64 characters. Entering more characters will end up in an error message saying: "Updating test ruleset for flag [flag name] failed...
about 2 years ago in Feature Experimentation / Project / Account Configuration / Settings 0 Future consideration

New Results Page Layout

Sharing on behalf of a customer (Simon Born of Real Digital Services GmbH) "This is a short feedback on the new layout of the Results page. While I understand the approach to make visible the prioritization of the primary metric versus the others ...
about 2 years ago in Feature Experimentation / Other 0 Future consideration

Support Infrastructure-as-Code automation tools

As a developer I want to be able to authenticate to the Optimizely APIs using OAuth 2.0 Client Credentials Flow so that I can use automation tools (such as Terraform) to manage the configuration of my Optimizely account
about 2 years ago in Feature Experimentation / APIs 1 Future consideration

Clone or copy experiment

It would be helpful to have a clone or copy functionality. This way it is much easier to setup an experiment that is similar to another one.
about 2 years ago in Feature Experimentation / Experiment Authoring 1 Already exists

Option to change the variants order in Flags

In Flags, it is not possible to change the order of variants and have a different “Baseline” variation by default in the Results Page. Regardless the possible workaround (change the baseline variation from the results page), the proper behaviour w...
about 2 years ago in Feature Experimentation / Project / Account Configuration / Settings 0 Future consideration

Link back to the experiment on the results page on new FS UI

Hi team, there is no easy way to move between an experiment and the result at the moment. Customers need to keep both experiment and the result open in different tabs if they want to refer between both so they are asking for a link back in the res...
about 2 years ago in Feature Experimentation / Other 1 Already exists

Ability to customize the logger

Sixt has thousands of users and optimizely currently logs in unstructured manner. We would like to include some custom fields for each request that comes into our servers in order to facilitate easier logging, review and optimizely logs search. As...
over 2 years ago in Feature Experimentation / SDKs & Agent 1 Future consideration

Clinets request a way to differentiate experiment state (active, paused, archived, invalid)

This has been requested via FS swift-sdk github issues (https://github.com/optimizely/swift-sdk/issues/291) Currently SDK provides an error experimentKeyInvalid which says "Experiment key ((key)) is not in datafile. It is either invalid, paused, o...
over 2 years ago in Feature Experimentation / SDKs & Agent 0 Future consideration