Skip to content

Web Experimentation

Categories

JUMP TO ANOTHER FORUM

27 results found

  1. 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?
  2. 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?
  3. 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
    New  ·  0 comments  ·  Admin →
    How important is this to you?
  4. 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?
  5. 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
    New  ·  0 comments  ·  Admin →
    How important is this to you?
  6. Customers use the Chrome Plug-in often for debugging, QA and forcing themselves into variations. It does not always work, and is pretty limited.

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