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 10 votes in total. Thank you for your feedback.

ADD FEEDBACK

FILTER BY CATEGORY

Web Experimentation

Showing 16 of 874

Fetch API's list used in project

Is there any better option by which we can get the list of API’s used in our project, so that we can fetch all the API's used.
1 day ago in Web Experimentation / Other 0

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

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...
3 months ago in Web Experimentation / APIs 0 Investigating

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...
3 months ago in Web Experimentation / Project / Account Configuration / Settings 0 Future consideration

Add description to archived experiment

Vodafone Ziggo - We visit our archived experiments often, and it is difficult to understand why certain experiments were built. in order to find out, you have to go into results and edit the experiment, and do some research. It would be helpful if...
4 months ago in Web Experimentation / Other 1 Planned

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...
4 months ago in Web Experimentation / Developer Experience / Experiment Authoring 0 Future consideration

REST API to pull the page usage data

Stepstone wishes to create a batch process to pull the Page usage info and create a dashboard in Power BI.
6 months ago in Web Experimentation / APIs 0 Already exists

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.
6 months ago in Web Experimentation / Experiment Authoring / Performance 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...
6 months ago in Web Experimentation / QA 1 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...
9 months ago in Web Experimentation / Developer Experience 2 Future consideration