111 results found

1. Device List Clean up - Segment

   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 like Android, Iphone and All Phones. it just looks confusing. Maybe it needs a better name. Not a priority but definitely a nice clean up would be nice.

   I also don't know why the segment by new vs returning visitors was removed. I know we can do this by doing an audience segmentation, but sometimes I have experiments that are for everyone, and then in the report, I'd like to segment by that type of visitor.

   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… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Lack of Transparency in Preview Mode

   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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Multi-device Experiments

   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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Change approval workflow in Web Experimentation

   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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. qa mode versus preview

   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 to rest user to normal
   all lower environments automatically set to qa which turns on variation logging
   what this mode enables
   sets all custom events to "environment=qa"
   allows user to enter an experiment that has a qa mode audience.
   
   if you set your cookie to a specific experiment - provided that the experiment was set up properly with qa mode audience and is published.
   provides special gui console.logs for the experiment code.
   when entering from querystring, sets qa cookie so visitor stays in qa mode until they reset with 'remove'

   this basically puts a system around cookie based qa and allows you to send out links to partners with "optiQa=x###" in the querystring to review.

   IMPLEMENTATION:
   besides having publish and preview in the top left of the nav, could have a toggle/radio that said 'qa -- live' that sets the base for this and automates all of what I am doing above. when turning it on, you'd get an id of sorts that would work for the parm/cookie. No audience addition or wrangling. could add the logging as a util - util.log('comment'); or something like that. this could also serve as the 'start date' for metrics - when it is turned to 'live'. The codes should be as short as possible - just incrementing integers starting at 1 to be easy to use.

   WHY
   i want to qa experiments that essentially run in the same manner as they do for an actual visitor - instead of previewing or variation forcing because they skip audiences, the timing is different AND events don't fire.

   i want to see the page activate and potential impact to js racing conditions, fouc, and timing on redirects. i want to validate the audiences i've set up. i want to ensure events are firing. basically, i want to see what my visitors see, not just what would happen in an ideal world.

   lastly, is easier to qa in mobile without the preview overlay, which causes qa team issues.

   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… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Multi-Armed Bandit Results

   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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Word Wrap Option in Visual Editor

   When editing HTML - allow the text/code in the HTML box to wrap. This makes it easier to see and edit.

   •  

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. experimentation forced re-evaluation each decision - override UPS / sticky assignment

   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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. View experimentation sections from editor

   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 go to the sections instead of 'return setup' would be a lot better. Also, the bottom toolbar could be consolidated to fewer buttons that do the same. Like the edit, variation code editor and changes seem to take you to the same thing. I don't want to choose for most users, but right now the options in the toolbar are overwhelming because they mostly do the same thing. I wish the emulation of other devices didn't open as a pop-up either, because when I'm sharing my window, it won't appear. I have a very big screen. Anyway, I think it could be better.

   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… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. NEW Responsive Mode

    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 edit.

    3. Keep responsive bar visible (and give it more contrast and a bar drag icon) - don't make me click 3 more time to scale the editor.

    4. Enable the "escape" button (and or clicking outside of the emulator) to exit Emulate mode.

    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… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Experiment Activation and associated changes

    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, I will either need to add code to project.js or add pages to the experiment and define changes there.

    If I add code to project.js, it adds complexity to project.js. It makes it less clear what code and which pages are part of the experiment and adds unecessary processing for all pages.

    If I add the pages to the experiment, I can keep all the code related to the experiment in one place but then I have activation points on all those pages which is not ideal.

    POSSIBLE SOLUTION
    Define pages as part of the experiment but do not have this definition list trigger activation. Have a completely separate activation mechanism that allows me to add pages and define specific conditions for activation. This would allow me to keep all the code related to the experiment in one place and limit activation to specific pages or actions.

    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,… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Developer experience

    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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. 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 ow

    Software Engineer

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. o Adding pagination to events to limit the number of events loaded at once.

    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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Opal UI - is Awful!!

    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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Bug Fix

    Bug Fixes on text editor (mainly shared code)

    Native find on page doesn't work reliably (sometimes shows more occurrences than there actually are, doesn't jump to the place in the code when you hit enter)

    • Would be great to implement that properly

    Starting typing at all makes the current line jump to the bottom of the screen, which is really frustrating and quite confusing.

    • Ideally just keep the scroll position what it is when you start typing.

    (I'm using Chrome on Mac OS)

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Version control

    A slightly better interface of what changes have been made before committing. I know you can view history, but it's not that easy to understand. Being able to see lines of code that have changed in each of the shared js, shared css and variations would be very helpful, rather than just the number of lines changed.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Create a dev only toggle that won't show the website preview

    I am a developer who uses Optimizely for a lot of experimentation and have to spend a lot of the time inside of the code editor. The new editor creates way too much friction. I don't need my entire website to load and then inject optimizely's scripts. This cant take multiple seconds just to change one line of code.

    I would much prefer it if we could have something like a toggle on our profile where we could choose to never show the preview and just show us the variation code in a code editor. I can always copy a link if I want to go look at the preview.

    The one thing I do like about the new code editor is that it feels more like vs code where it gives you intellisense and smart code / method completion. If we could have this functionality in a web based code editor without having to load any preview (I legitimately never look at the integrated preview, I just copy the link into a private window).

    I am a developer who uses Optimizely for a lot of experimentation and have to spend a lot of the time inside of the code editor. The new editor creates way too much friction. I don't need my entire website to load and then inject optimizely's scripts. This cant take multiple seconds just to change one line of code.

    I would much prefer it if we could have something like a toggle on our profile where we could choose to never show the preview and just show us the variation code in a code editor. I can always copy a… more

    8 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. New Visual Editor - Carry over click tracking from Lagacy Editor

    Please make sure to carry over click tracking fucntionality from Lagacy Editor. This is a fundamental function in the current legacy editor and the old legacy editor should not be phased out until this function is added to new editor

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  5 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. New Editor

    Hello I have been using Optimizely for over 5 years and greatly enjoyed the product. The new editor that is slated to be fully launched greatly complicates my workflow. Most of the coding and edits I do in this editor I have to use an external editor to write and then copy them into the new Optimizely editor because of the layout and bugs in this new experience.

    Here are some of the bugs I have noticed while using the new layout:
    -the preview screen the editor is overlayed on distorts the elements and hides the element being edited behind the projected boiler play Homepage.
    - the boxes for the fields in the template editor popup cannot be dragged and resized. This creates an impossible environment to edit code and I have to copy my work to an outside editor to make any change.
    -the Emulate feature does not create a mobile environment. It just shrinks the desktop environment
    -the popups overlaying the screen block sight of the feature being edited

    Hello I have been using Optimizely for over 5 years and greatly enjoyed the product. The new editor that is slated to be fully launched greatly complicates my workflow. Most of the coding and edits I do in this editor I have to use an external editor to write and then copy them into the new Optimizely editor because of the layout and bugs in this new experience.

    Here are some of the bugs I have noticed while using the new layout:
    -the preview screen the editor is overlayed on distorts the elements and hides the element being edited behind… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating