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 19 of 962

Add Collaborators API

I'd like to suggest opening up a collaborators API to allow for the management of internal user/collaborator accounts via API calls
3 days ago in Web Experimentation / APIs 0

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...
11 months ago in Web Experimentation / Developer Experience 2 Future consideration

Combining two click event into one conversion metric.

Sharing on behalf of a customer (William Bauer of Bell Media) The customer asked to add a Feature that will combine two or more click events to trigger one metric conversion. For example, on a webpage, there might be Right/Left arrows that would c...
about 1 month ago in Web Experimentation / Other 0

Performance Edge - Custom Attributes

Interested in the addition of Custom Attributes to allow us to segment results. Currently in order to get the data we need, we have to create a large amount of events to account for all testing scenarios we want to capture.
about 2 months ago in Web Experimentation / Other 0

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.
about 2 months 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...
4 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...
5 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...
5 months ago in Web Experimentation / Project / Account Configuration / Settings 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...
8 months ago in Web Experimentation / QA 1 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...
11 months ago in Web Experimentation / Experiment Authoring / Targeting 4 Already exists