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

FILTER BY CATEGORY

Web Experimentation

Showing 10

Global holdout group

The ability to set up hold-out groups, which would allow users to separate a percentage of their user base and exclude them from any experiments or feature launches. This feature would enable users to assess the long-term impact of all cumulative ...
19 days ago in Web Experimentation / Project / Account Configuration / Settings  / Targeting 0 Future consideration

Provide a better editor for "custom javascript conditions" for the audience builder.

Hi! As an Optimizely editor, I would like to have a better developer experience when using the "custom javascript condition" when building an audience. Not only is the editor showing plain text while it could be an editor such as is presented when...
about 1 year ago in Web Experimentation / Developer Experience 2 Future consideration

Add an internal description field for extensions

A customer suggested the following feature: It would be helpful to add an internal description field for Extensions. In the Extension's settings, there is a description field. However, that field should contain no more than a single line of text b...
6 months ago in Web Experimentation / Experiment Authoring 0 Future consideration

Multi-variable forced QA

Would like to have a setup so that when there are multiple variables, a QA cookie can be set for each variable so that each can be viewed in the browser independently. Right now a QA cookie set only seems to get you in to an experiment, not view e...
10 months ago in Web Experimentation / QA 1 Future consideration

extensions required values

When creating an extension, a customer suggests to add the possibility to change some of the fields of the extension from optional to required, in the template of the extension itself. Currently, fields are all optional when created. The Json file...
7 months ago in Web Experimentation / Project / Account Configuration / Settings 0 Future consideration

Less clicking around in the Visual Editor, enable scrolling behaviour by default!

Hi! It would be nice to be able to scroll within the Visual Editor without having to enable "Interactive Mode". It's not like scrolling while "Interactive Mode" is disabled is reserved for another functionality, so why not have scrolling available...
about 1 year ago in Web Experimentation / Experiment Authoring 2 Future consideration

Filter active audiences on GET Audiences API & Remove an audience

Hi! As an Optimizely editor, it would be nice to be able to remove an audience. Archiving is not enough, as archived audiences are also returned in the GET Audiences API (see https://library.optimizely.com/docs/api/app/v2/index.html#operation/list...
about 1 year ago in Web Experimentation / APIs 2 Future consideration

While adding audience condition in code mode, add error message if syntax is wrong

In Web and Full Stack, if you add an audience condition via the code mode, and you do not add the "and" at the beginning, the audience cannot be saved, but no error message is generated, so it is not clear what is happening. Please add an error me...
8 months ago in Web Experimentation / Developer Experience / Experiment Authoring 0 Future consideration

Bulk archiving

Provide the ability to bulk archive pages, metrics, experiments, etc that are no longer in active use or that have otherwise been selected to help improve snippet speed.
10 months ago in Web Experimentation / Experiment Authoring / Performance 0 Future consideration

Moving Full blocks of content in the WYSIWYG editor is painful!

When we want to reposition full blocks of content on a web-page, it's hit-and-miss whether the content renders correctly. In particular, the padding and colour schemes don't always transfer correctly
about 1 year ago in Web Experimentation / Experiment Authoring / Other 0 Future consideration