Skip to content

Web Experimentation

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

116 results found

  1. 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!

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Analytics/Results Page  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Analytics/Results Page  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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
    faster

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Most experiments need different images for desktop, mobile, and tablet. Without a shared library, the customer has to either create a separate experience per device — splitting traffic — or write CSS manually. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. I'd like to have a change approval workflow for launching and updating experiments in Web Experimentation. Today I need to use workarounds like applying a QA audience until the experiment is "approved" by the right individuals.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. AS an experimentation builder
    I WOULD LIKE an easy way to fully qa test and share pre-production experiments
    BECAUSE i want to validate all the aspects of my experiment and be able to share pre-production model with non-technical partners

    FUNCTIONALITY
    look for a cookie or querystring parm or hostname and from that set 'qa' to either true or false.

    false: take no action
    true:
    parms: xCode, info, remove
    xCode sets qa cookie and allows you into the experiment you match the qa mode audience for
    info allows for specifically coded console.logs to run
    remove - removes qa cookie / environment…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Can we add a traffic split visualization to the results dashboard? This would let the team verify that the bandit is working as intended and see exactly how traffic is being rerouted to the top-performing variations in real-time.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Analytics/Results Page  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. When editing HTML - allow the text/code in the HTML box to wrap. This makes it easier to see and edit.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. As an experiment builder

    I would like to be able to force re-evaluation of flag/campaign audiences if I want my experiment to float by user properties and am working in web or have a UPS set in feature

    So that I can have transactional experiments that will match the user up properly to their current properties and not persist them into something they no longer belong in.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. It would be nice to access all the experimentation/personalization modules from the editor. In the old editor, we always had the option to click any module from th left, like metrics, shared code, targeting, etc., but now, the editor opens on top of that dashboard, and the only way to go back is by clicking 'return to setup,' which makes it a longer process to go through. It is also very slow, so I take too long checking all the sections of the experiment/personalization. I get that the editor now takes up the whole screen, but adding a drop-down to…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. I'm glad to see that the Emulator has been improved. But there are some "WTH" issues in the UX. In no particular order...

    1. DON'T blur the content when resizing -- I frequently want to see how objects flow as the browser width changes, this exposes flaws in CSS or coding and I can't see what's happening when It's blurry.

    2. Disabled the editor in the Emulation mode (Add one of the fingers at the top bar to disable it, next to the rotate button) - I need to engage with the site and without it disabled it think I want to…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. AS
    an experiment builder in web

    I WANT TO
    be able to make changes to pages associated with the experiment and not have the visitor activate the experiment when those pages load

    SO THAT
    I can keep changes related to an experiment together while limiting activation of the experiment to a specific page or action

    USE CASE
    I have a change for a specific product display page that I want to evaluate. There are associated changes that I will need to make to the cart and every checkout page. In order to make changes to those pages to support this,…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. I want Optimizely’s new developer experience to support a true IDE-first, GitHub-native workflow. I should be able to do all coding in my own IDE, manage changes through GitHub, and publish through automation and CI/CD workflows without depending on the Optimizely editor for core development tasks. The editor should support preview and collaboration, not replace standard developer tooling and deployment workflows.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Currently, loading the full list of events puts a significant load on the page.
    The Events view becomes very slow, and in many cases it takes several minutes before the events finish loading.
    Pagination (or lazy loading / load more) is needed to reduce the amount of data rendered at once and to improve usability.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Committed  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Opal is very difficult to see -- there's no contrast between it and a page in reporting (or anywhere Opal appears)

    Recommend giving her some color! See screenshots.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Opal AI  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 6
  • Don't see your idea?