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

Web Experimentation

Showing 22 of 1571

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...
almost 2 years ago in Web Experimentation / Developer Experience 4 Future consideration

Use "pageview"-events as a source for the audiences builder

Hi! As an Optimizely editor, I want to be able to use the "pageview"-event of a certain page as the source for an audience so that I can target visitors that (have returned and) have viewed a certain page before. We currently solve this by using a...
almost 2 years ago in Web Experimentation / Experiment Authoring / Targeting 4 Already exists

Add support for modern image formats like WebP/AVIF

As an experiment author, I want to be able to upload images to experiments that are high quality, have low file sizes, and support transparency. By supporting modern image file formats such as WebP or AVIF in the visual editor, users would be able...
8 months ago in Web Experimentation / Experiment Authoring 1 Future consideration

Update the "Device" audience condition to either work with iPads or accurately reflect that iPads cannot be targeted using the "Device" audience condition.

Issue As an experiment engineer, I constantly need to explain that even though Optimizely offers an out-of-the-box solution to create audience conditions that would either include or exclude iPads in experiments, creating an audience condition usi...
8 months ago in Web Experimentation / Targeting 1 Future consideration

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 ...
12 months ago in Web Experimentation / Project / Account Configuration / Settings  / Targeting 0 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...
over 1 year 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...
over 1 year ago in Web Experimentation / QA 1 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...
almost 2 years ago in Web Experimentation / APIs 4 Future consideration

Would like to have compilation of most commonly used js functions

As a new Web Experimentation customer, we continue to run into challenges where certain functionality, metrics, events, etc. are not available out of the box. The Solution Architect assigned to us (Ezequiel) has a lot of answers and examples that ...
20 days ago in Web Experimentation / Experiment Authoring 0

Replace "delete" with "archive" for an experiment in REST API doc

I'd like to suggest replacing "delete" with "archive" on that page as this request doesn't delete experiment, just archives it and it's confusing for the customers. https://docs.developers.optimizely.com/experimentation/v3.1.0-full-stack/reference...
over 1 year ago in Web Experimentation / APIs 0 Investigating