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.

We are pleased to announce that beginning on Tuesday, March 25th, we are launching a new feedback experience for our customers!

The new experience should transition over seamlessly, but please be aware that short interruptions to our feedback portal may occur on March 25th between 2:30-4:30pm EDT.


All the best, your Optimizely Product Team

ADD FEEDBACK

Web Experimentation

Showing 36 of 1913

Prioritising personalisation experiments

I'm looking at setting up 2 personalisation experiences on the same page (different audiences). I am aware that multiple experiences can be placed within the same campaign and prioritised, however the 2 experiences I am setting up have different m...
12 months ago in Web Experimentation / Experiment Authoring 0

Debugger for events not triggering

Make it easier to understand if an event would not trigger in an experiment, for example by Implementing a debugger tool when editing a variation, showing if specific elements/events that are supposed to be tracked for the experiment, would not tr...
about 1 year ago in Web Experimentation / QA 0

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...
almost 2 years ago in Web Experimentation / Experiment Authoring 1 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 ...
about 1 year ago in Web Experimentation / Experiment Authoring 0

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...
almost 2 years ago in Web Experimentation / Targeting 1 Future consideration

Support for rearrange tests on Dynamic websites

Optimizely Web Experimentation does not currently support rearrange tests (tests that swap the positions of nodes in a document) on dynamic websites but may extend support in the future. Adding support will mean elements in Dynamic pages can be re...
8 months ago in Web Experimentation / Experiment Authoring 0

Device sizes out of date

It would be great to see updated device sizes in the visual editor especially for mobile as these are too small for screen sizes people use today. I'm not a developer so I rely on the screen size builder to verify changes but when I look at my iPh...
8 months ago in Web Experimentation / Experiment Authoring 0

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...
about 3 years ago in Web Experimentation / Experiment Authoring / Targeting 4 Already exists

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 2 years 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...
almost 3 years ago in Web Experimentation / QA 1 Future consideration