Skip to Main Content
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 29

MAU Consumption Notification

Hi Team, To manage Experimentation MAU Consumption I would like to request a notification functionality that alerts customers when a certain percentage of their allotment has been consumed so as to we can ensure that Overages are avoided in a time...

Folder System for Optimizations

As an experimenter I would like the ability to sort my experiments and personalization campaigns into folders based on my own criteria. For my use I would have folders based on the area of the site we are testing (ie. homepage, category page, prod...
9 days ago in Web Experimentation / Other 0

Ability to lock down code editor / css changes

As an administrator, I want to lock down the code editor / CSS changes within the platform to prevent security risks from non-technical users or bad actors inserting malicious code.
4 months ago in Web Experimentation / Security 0

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...
2 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...
4 months ago in Web Experimentation / QA 0

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 ...
5 months ago in Web Experimentation / Experiment Authoring 0

Optimizely Web Exp Customer Java script Utility Function Suggestion

Request: Implement an in-code suggestion feature for Optimizely utility functions. Functionality: When a developer starts typing in the code in the optimizely customer java script text area, the system should suggest available utility functions fo...
2 months ago in Web Experimentation / Developer Experience 0

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 ...
over 1 year ago in Web Experimentation / Project / Account Configuration / Settings  / Targeting 0 Future consideration

Delete experiment permanently

Currently, we have an API call called "Delete an Experiment" https://docs.developers.optimizely.com/web-experimentation/reference/delete_experiment to archive experiments (it was suggested in another feedback to modify the name into "archive an ex...
3 months ago in Web Experimentation / APIs 1

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