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

My feedback: Experimentation Analytics

Showing 35 of 1838

Allow Calculated Metrics

Customers would like to be able to build their own metrics by mixing Optimizely events already present in the platform. A key example is funnel metrics: Conversions of step 2 / Conversions of step 1 as opposed to conversions of step 1 / number of ...
about 2 years ago in Experimentation Analytics / Metrics Setup 2 Planned

Getting a (public) results sharing link via API

Suggested by a customer: "We are automatically exporting all our Optimizely running experiments to Slack and would like to add a link to the results of each experiment to that. As this should be accessible to all users and not only those with an O...
almost 3 years ago in Experimentation Analytics 4 Planned

Allow multiple currency support

It would be a nice add to be able to use 1 revenue event for all currencies. Currently, we need to create 1 event per currency if we want to track revenue accurately. Instead, it would be nice to use 1 revenue event, and specify the currency insid...
almost 2 years ago in Experimentation Analytics / Metrics Setup 0 Future consideration

Results pulled via API are frequently multiple days stale.

This leads to us having to make multiple request per experiment in order to get up-to-date data. Various ideas to resolve: Allow users to prime a test's results Call a webhook when results are ready Optimize performance of the results query
over 1 year ago in Experimentation Analytics / APIs 0 Investigating

Exclude outliers for selected metrics

Currently Optimizely allows excluding outliers only for ravenue. We would like to enable it for other metrics e.g Add to Bag.
almost 3 years ago in Experimentation Analytics 1

Filter results by event tags

We often run into this: When evaluating experiments we need to segment users / events that occured under certain conditions. User attributes don't suffice as often the tags we are looking for change during a session. So we would like to be able to...
over 3 years ago in Experimentation Analytics 0 Planned

Change denominators to track funnel-conversions better

We want to measure conversion of different steps in our funnel, including offline events based on prior conversion steps and not always based on visitors. in our case: We do create leads on our landingpages which we then call on the phone. for som...
over 2 years ago in Experimentation Analytics 1 Planned

Segmenting more than one attribute at a time

For releasing features / targeting users to be part of an experiment it is very straight forward to target specific attributes As optimizely gives you the ability to apply various different filtering mechanisms.. e.g. below, above, contains, does ...
about 3 years ago in Experimentation Analytics 0 Investigating

Add option to modify the Timezone in the Results Page

Results Page allows to view results for a specific date range, by entering start date and end date. It also shows the current timezone (for example GMT +01 00). It would be good if we could change the timezone from there, so teams in different tim...
about 2 years ago in Experimentation Analytics 1 Investigating

Add experiment metadata (human readible experiment name, variation name, event name, etc) in E3

Add experiment metadata (start/finish date, etc) to E3. These can be accessed via our REST API but this would reduce the friction points of building dashboards using the E3 data.
about 3 years ago in Experimentation Analytics 0 Future consideration