14 results found
-
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 -
Edge Delivery with Fastly CDN
I am the Product Manager at Hearst Magazines.
Our current Web Experimentation implementation is set up with the snippet in the <body> tag, which causes significant flicker for experiments involving changes above the fold.
Your new Edge on CDN feature could be a game changer for us. However, the blocker is that we currently use Fastly CDN, which is not supported by your Edge product.12 votes -
Multiple audience preview
I would like to be able to test multiple audiences on the same page, to see how the activities associated with those audiences would appear to a user in multiple audiences.
The Optimizely preview helper would be a great way to do this. In the override, it currently only shows the audiences associated with the campaign being previewed. If this allowed for the override to allow for any audiences to be selected, and hence allow to test for how it might look for a user who is in multiple audiences, it would be extremely helpful.
2 votes -
Tool should flag when a test is low power (ie not likely to reach stat sig)
State exactly why it was flagged; would likely require customer to input some data
1 vote -
Bring the Sample Rate Calculator into Test Build
Its inconvenient navigating back and forth
2 votes -
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 -
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.
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 -
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 -
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 -
Improved QA plug-in
Customers use the Chrome Plug-in often for debugging, QA and forcing themselves into variations. It does not always work, and is pretty limited.
1 vote
- Don't see your idea?