Skip to content
← Turn your feedback into functionality

Web Experimentation

Web Experimentation

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Welcome! 👋

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

27 results found

  1. 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
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  2. 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
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  3. 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
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  4. 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
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  5. Visual Editor - Loading Improvements

    Customers try to load their website in the Visual Editor and it never finishes loading

    1 vote
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  6. 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
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  7. 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
    New  ·  0 comments  ·  Admin →
    How important is this to you?
2 Next →
  • Don't see your idea?