Skip to content

Feature Experimentation

Categories

JUMP TO ANOTHER FORUM

11 results found

  1. In order to support testing of more complicated experiments that require server side code changes, in tandem with experiment JS/CSS changes, please allow the changing of a project target URL without deleting all the experiment changes.

    RapidX already has the ability to do this (they have a button that can bypass the change deletion behavior), meaning the use case is valid and the code has already been written. I'm not sure if it's an oversight or if there is a justifiable design reason why customers cannot do the same.

    Since we control both the experiment change selectors and the server…

    3 votes
    New  ·  0 comments  ·  UX  ·  Admin →
    How important is this to you?
  2. When the platform says another 50k users to reach significance, could a date be added? E.g. it has taken 3 weeks to get to 25k so give the date in 3 weeks as the date when the 50k will be reached

    3 votes
    New  ·  0 comments  ·  UX  ·  Admin →
    How important is this to you?
  3. Add a "status changed" date to the FX Flags overview page. Because currently, there is a "created" and "modified" column. However, "Modified" refers to any changes, and there is no easy way to see when a status was changed, so when a rule was changed to its current state (started/paused/concluded)... it would be valuable information for the customer just within the FX UI.

    Additional context: https://jira.sso.episerver.net/browse/DHK-2914?focusedId=2087943&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2087943

    4 votes
    New  ·  0 comments  ·  UX  ·  Admin →
    How important is this to you?
  4. It is sometimes hard to trigger a test variant when deeper into a flow. Could a bookmark be created to easily trigger a test on any given page?

    2 votes
    New  ·  0 comments  ·  UX  ·  Admin →
    How important is this to you?
  5. In the Opti ID > Usage & Billing > MAU Breakdown Dashboard, the “Experiment Name” column currently displays plain text for each experiment. While this provides identification, users must manually search for the experiment within the relevant Optimizely project to view or edit its details. This extra step slows down workflows, especially for customers or internal teams who need to investigate experiment configuration, performance, or attribution quickly.

    Solution: Enhance the “Experiment Name” field in the Opti ID MAU dashboard to display each experiment name as a clickable hyperlink. The link should point directly to the experiment’s details page. The link…

    1 vote
    New  ·  0 comments  ·  UX  ·  Admin →
    How important is this to you?
  6. I know that Optimizely tries to keep bucketing consistent when traffic allocation and or distribution changes.
    It would be great to be able to see the bucketing allocation (eg. 1-5000 for A, 5001-10000 for B) in the interface.
    In this example it is simple, but when ramping up (and possibly at the same time changing the distribution of traffic) it would be great to be able to verify via the interface which buckets are being set.
    I am aware of Customer Profile Service but I see this as independent from that.

    1 vote
    New  ·  0 comments  ·  UX  ·  Admin →
    How important is this to you?
  7. I know that Optimizely tries to keep bucketing consistent when traffic allocation and or distribution changes.
    It would be great to be able to see the bucketing allocation (eg. 1-5000 for A, 5001-10000 for B) in the interface.
    In this example it is simple, but when ramping up (and possibly at the same time changing the distribution of traffic) it would be great to be able to verify via the interface which buckets are being set.
    I am aware of Customer Profile Service but I see this as independent from that.

    1 vote
    New  ·  0 comments  ·  UX  ·  Admin →
    How important is this to you?
  8. As of now, in Feature Experimentation, if a variant performs (very) bad, there is no way to deactivate it or set its behavior back to baseline without needing to create a new rule.
    This of course slows down experimentation speed.
    I do understand that the results of that variant are not usable after setting a variant's behavior back to baseline behavior. However, that is not the issue. The goal is to simply be able to continue letting the test run while disabling a bad-performing variant.

    1 vote
    New  ·  0 comments  ·  UX  ·  Admin →
    How important is this to you?
  9. I would like the ability to create folders within projects to organize our work. This would allow users to organize work by developer or by area of the site.

    1 vote
    New  ·  0 comments  ·  UX  ·  Admin →
    How important is this to you?
  10. It would be great to have some kind of filters that allow a deeper dive into data. So if we wanted to see how many people bought a licence AFTER triggering a specified conversion

    1 vote
    New  ·  0 comments  ·  UX  ·  Admin →
    How important is this to you?
  11. Hello!

    We very much appreciate the arrival of ratio metrics. However, they do provide limited value to us as long as Custom Event properties are not usable for either numerator or denominator.

    It would be awesome to see that added.

    Role: I am the Team Lead for our experimentation center-of-excellence and infra team.

    1 vote
    New  ·  0 comments  ·  UX  ·  Admin →
    How important is this to you?
  • Don't see your idea?