32 results found
-
Export code based on conclusion
Once a test is concluded, export the changes as a set of code in HTML+CSS+JS, or React, etc. Has come up several times in the past month. Suggest investigating whether competitors do this.
2 votes -
Guided Solutioning for Common WYSIWYG problems
There are common WYSIWYG editor problems, based on site architecture or test type. Create self-service solutioning guides for customers to diagnose and solve problem.
2 votes -
Custom Labels (Owners, Next Steps, Jira Link, Figma Link, etc.)
Give customers the ability to create own labels to attach to experiments, and make these columns you can add in the overview, as well as making it filterable and sortable. This feature would help create ownership of experiments
2 votes -
URL conditions for saved pages
I create experiments for a major retailer, and current URL substring match capabilities force me to use JS conditions or callbacks for all campaigns on my PDPs and category pages. This is tedious and makes it difficult for non-technical teammates to run experiments.
For example, many retailers use structures like retailer.com/p/ to indicate PDPs and retailer.com/c/ for category pages. However, using those in the substring match fields will include all substrings with a "p" or "c" since the backslashes are not accounted for, opening up the test for many, many more visitors than we would anticipate. For example, the visitor…
1 vote -
Naming/Labeling Events & Changes
It seems counter intuitive that I can name a click tracking event but that name does not appear in the sidebar of the variation editing menu. It would make sense to be able to add a label for ALL changes and have them display in the sidebar to allow for easier management. Otherwise, its a bit of a cluster right now
1 vote -
Geo-testing
The ability to split tests based on geographical region so that we can test the effectiveness of region-specific marketing campaigns, two-sided marketplaces, or faciliate other testing use cases when we cannot guarantee a user will be in solely the control or test variant.
1 vote -
Support for Numbers (floats, integers) in Custom Audience Attributes
Currently Web Experimentation Audience Attributes only support values as string types. Adding support for number values (floats, integers) would allow for more complex and granular audience membership.
Customer provided example: An audience for visitors who have less than 100 subscriptions. The Audience Attribute numSubscriptions would be a number value of the total number of subscriptions the visitor has. This attribute could be used to build an audience for all visitors with less than X (ex. 100) subscriptions.
1 vote -
Visual Editor - Changes overwritten in Preview by the site
The changes work when you are in the tool , but do not actually work in the wild. Something overwrites the code from the customer's website.
1 vote -
Visual Editor - Loading Improvements
Customers try to load their website in the Visual Editor and it never finishes loading
1 vote -
Visual Editor - Dynamic Selector
Customers attempt to use the visual editor to make persistent changes, but the changes do not persist throughout the entire user journey as the selector changes either on reload or if new DOM elements are present on different pages.
1 vote -
Improved QA monitoring of test variations
Prospects that have had tests "break" their site want an automated solution for monitoring the quality of their test variations in production, and to be alerted immediately when there are issues that negatively impact UX.
1 vote -
Sample Size Calculator
This should help teams understand the concept of run-time, and avoid tests being run that are destined to become inconclusive.
1 vote
- Don't see your idea?