129 results found
-
Drill-down path events by event property in Paths analysis
Our customer Henry Zhao (henryzhao@canva.com) from Canva Pty Ltd has requested the ability to drill down event names by a property in Paths, noting the comparison to Mixpanel and Amplitude to help illustrate the use case.
In a Paths analysis, when a customer tracks a generic/grouped event (e.g. a single click event that fires across many different UI elements, distinguished only by a property like action, element, or target), there is currently no way to automatically break that single event node into multiple, distinct nodes based on the property's values. The existing Label field only replaces a node's…
1 vote -
Add new JSON field type to templates
Add a new JSON field type to templates.
Currently templates support multiple field types like text and textField but it would be great to add JSON support.
It would increase readability and validate for formatting errors right away3 votes -
Add CMP HPT/TSK as option to show/hide Column in WX
We have the ability to integrate with JIRA and then show that in the show/hide column for Web Experimentation. Why not do the same with CMP. it will be nice to have this show up in the show/hide column so that we can easily see what experiment/personalization links to as a task/HPT. It should also be linkable so that we can easily open that task from the web experimentation platform.
1 vote -
Scope Preview Tool Feed to current experiment
There's currently no setting to scope the Feed tab to a single experiment. The Feed is a project-level event stream — it surfaces every event and Page activation that fires on that URL across your entire project, regardless of which experiment you're QAing. By design, it even shows events that aren't attached to any running experiment, because the Feed references the saved project instance rather than the published CDN snippet. It'd be useful to scope the Preview Tool Feed to current experiment only.
1 vote -
Clear out Multi-armed bandit data
It would be beneficial to be able to reset the traffic allocation type after duplicating an experiment that had previously run.
Depending on the complexity of the experiment set up -- it can be time consuming to reproduce multiple variants.
1 vote -
What was running on yyyy/mm/dd?
AS
a program owner,I WANT TO
look in history in and see what was live on a specific date range,SO THAT
I can quickly produce a list of campaigns that are/were executing within a time window in case of an issue during said date range. This should include things that are concluded (or otherwise) and not showing in the active experiment space that are being executed.It is understood that this same list could be potentially be extracted by looking at history and evaluating the logs, but that is time lost in a production situation.
1 vote -
Search Functionality
It would be great if the search functionality had the ability to include custom fields. Customers have expressed that they would like to to be able to search by JIRA ticket numbers.
1 vote -
Shared Assets (Media Library)
Images are also locked inside each variation and cannot be reused across experiments. A Media Library exists, but it is a paid extra. A basic shared repository should be included as standard.
1 vote -
Opal Code Editing for Reports
Editing reports within Opal constantly reloads the HTML in Opal. Very annoying. If Opal is managing the HTML for the reports - and you're allowing us to edit -- at least let me send the update once I'm ready.
1 vote -
Multiple Linked Hypothesis from CMP HPT tasks to WebExperimentation
When we create a new task in CMP (We use HPT since it was integrated with collaboration) we sometimes use it for two separate tests that have the same objective and hypothesis but for different funnel experiences. It will be ideal to be able to add these two Hypothesis tasks to the Web Experimentation. Right now Im only able to add it once so the other test, can't see it anymore. It will also be greate to show both tests in that same task if possible. I will be creating another feedback as it is part of this as well.
1 vote -
Enable substring (contains) matching for Custom Attributes in Audience Conditions
The "contains" operator is available for built-in attributes like Ad Campaign but not for Custom Attributes. We need substring matching on Custom Attributes to target audiences based on partial URL paths without creating individual exact-match conditions for every URL variation. This would significantly simplify audience setup for multi-page experiments. Ticket #1916403 references this request.
11 votes -
Case insensitive query params and cookies
Create a toggle to allow query params and cookie values to be case insensitivity.
This feature is (or was) in the docs but it was not actually able to be activated.
This feature would allow us to use different cases for key and values on query params, without having to use custom code.
This makes it easier for marketers to create audiences without worrying about exact letter casing.
3 votes -
Metric duplication
Quite often, we need to track both unique and total conversions for metrics that contain multiple filters. Currently, this requires creating a new metric from scratch, which can be a time-consuming process when there are a large number of filters involved. Adding the ability to duplicate an existing metric and simply switch between unique and total conversions would save significant time and reduce manual effort.
1 vote -
New Brand Colors Are Impossible to Read
This blanket brand-color update makes the Web UI unreadable due to contrast and its peppered throughout the UX.
Taste aside, changes like this still have to be usable. So painful!
2 votes -
Visitors to Stat Sig Missing from Unified Results Page
There is no longer a way to see how many more visitors are needed to reach stat sig. In the previous iteration of the results page inconclusive results would say "X visitors remaining" to reach stat sig. A prospect asked me why that was not included in this results page.
1 vote -
Experiment Analytics - Stat Sig Signifier
The statistical significance signifier (green or red number) doesnt carry from the individual metrics into the summary like it used to. Would be great to have at a glance indicator in the summary of the statistical significance status of all metrics in the experiment.
1 vote -
Heatmaps in Optimizely and Opal
As a CRO manager it would be great to have experiment related Heatmaps, Click Maps and Scroll maps as part of the Optimizely experiment reporting dashboard.
Another option would be for Opal to generate experiment/variation UX behavior heatmaps etc.
1 vote -
Experiment variation preview button
As a web developer and CRO manager, I would like to see a "preview" button added to the list of variations. This proves quick access to the variation for review without having to load the visual editor or code editor to access the button.
3 votes -
Device List Clean up - Segment
The device list under segments in Experimentation needs a clean up. I know what segments to use when analyzing experimentation results but the list is so long it looks messy and could use renaming or removal of some of them. For example, I still see Desktop (deprecated) it has been there for many years I think we can remove it if no one is using it? The other one is the Phone. We have iPhone, Other Phones and All Phones. I personally don't know what the difference is between Other Phones and All Phones. we can separate them by name…
1 vote -
Lack of Transparency in Preview Mode
When a variation does not appear in Preview, the tool does not explain why inside the interface.
There is a log, but it requires opening the browser console and reading technical output.
A clear diagnostic message inside the Preview interface would make the QA process much
faster1 vote
- Don't see your idea?