107 results found

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

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

3. Experiment change notification

   I would like to have a notification set up for a list of users whenever a new test is set to go live or set to pause.

   I am aware that there is an existing approval feature that sends approval request to a list of users. However this is not fit for purpose due to the extra steps created in the publish workflow.

   We would like to have a standalone notification feature to allow key stakeholders to be notified of key experiment changes without creating too many extra steps to the current flow of the release.

   11 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  ·  2 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. Missing preview url in new visual editor

   The "share preview" is missing in the new editor. Once the old VE is retired, how do we share the changes with other team members for review?

   7 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

5. Prioritization of Experiments and Personalization Campaigns

   Problem Statement (The "Why"):

   I need an easy way to manage the hierarchy of experience delivery across overlapping audiences. Currently, Optimizely allows for experience prioritization within a specific Personalization Campaign, but it lacks a "Global Air Traffic Control" for the entire Web project.

   When I have multiple experiments or personalizations live on the same page (e.g., the Homepage), there is no native way to ensure that a high-value visitor (like Enterprise or Mid-Market) is prioritized into a specific experiment before being eligible for a general "All Traffic" A/B test.

   Current Workaround (The Pain Point):

   To achieve this today, I have to:

   1. Manually create Exclusion Groups, which are randomized and don't allow for "if this, then that" priority.

   2. Or, manually edit the audience of the "All Traffic" test to explicitly exclude Enterprise and Mid-Market segments.

   This adds significant operational overhead, increases the risk of setup errors, and makes it difficult to scale a complex experimentation roadmap.

   Proposed Solution (The "What"):

   I am looking for a Prioritization Layer (similar to Mutiny’s "Prioritization" feature) where I can drag and drop all active experiments and personalizations into a master list.

   • Logic: When a visitor hits a page, Optimizely should check the priority list from top to bottom. The visitor is bucketed into the first experience they qualify for.

   • Outcome: If I have a homepage test for Enterprise, Mid-Market, and All Traffic, I want to ensure the Enterprise visitor sees the high-intent Enterprise experiment 100% of the time, rather than being "cannibalized" by a general A/B test just because it was launched first or has a broader audience.

   Business Value / Outcome

   • Accuracy: Ensures the most relevant message reaches the most valuable audience without manual "audience-math."

   • Velocity: Reduces the time spent QA’ing overlapping audiences and managing exclusion groups.

   • Revenue Impact: Maximizes the conversion of high-intent segments by ensuring they always see their tailored experience first.

   Problem Statement (The "Why"):

   I need an easy way to manage the hierarchy of experience delivery across overlapping audiences. Currently, Optimizely allows for experience prioritization within a specific Personalization Campaign, but it lacks a "Global Air Traffic Control" for the entire Web project.

   When I have multiple experiments or personalizations live on the same page (e.g., the Homepage), there is no native way to ensure that a high-value visitor (like Enterprise or Mid-Market) is prioritized into a specific experiment before being eligible for a general "All Traffic" A/B test.

   Current Workaround (The Pain Point):

   To achieve this today, I have… more

   6 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  ·  2 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

6. Duplicate Pages

   I want to have the ability to duplicate a page. Often times the page configuration is similar, for example when creating pages across environments. However, because Page duplication is not possible this causes a lot of additional work by setting up pages from scratch.

   6 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

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

8. Adjustment of permissions for users without publishing rights

   Enable publishing with a test cookie / audience as priority. The Editor role should inherit all Publisher permissions except standard publishing, but should be able to publish when a specific audience/test cookie is applied.

   Enable restoring experiments from the archive.

   Allow setting experiment end dates.

   Provide permissions to edit Pages.

   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  ·  2 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

9. New Editor -- Have option to position at top of page and control the background of the editir for visibility

   Be able to have the editor at the top of the page. And add controls to alter the visual editor's color so that it can be seen easier on white pages. (Mockup uses red for example).

   •  

   3 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

10. Enhancing A/B Testing with ES11 Modern JavaScript Features

    I am proposing that we upgrade to ES11 to stay aligned with the latest JavaScript standards and leverage modern language features such as optional chaining, nullish coalescing, and Promise.allSettled. These enhancements significantly simplify handling complex asynchronous logic, reduce verbose and repetitive code, and improve overall readability and maintainability of our experiment scripts.

    While we understand that upgrading is not strictly required to run experiments, adopting ES11 is vital for our growth and development as devs. It enables us to build more robust and reliable A/B tests, accelerate development and iteration cycles, and minimize technical debt. Keeping pace with evolving web technologies ensures our experimentation framework remains scalable and efficient as our testing needs expand.

    I would greatly appreciate your consideration of this upgrade.

    I am proposing that we upgrade to ES11 to stay aligned with the latest JavaScript standards and leverage modern language features such as optional chaining, nullish coalescing, and Promise.allSettled. These enhancements significantly simplify handling complex asynchronous logic, reduce verbose and repetitive code, and improve overall readability and maintainability of our experiment scripts.

    While we understand that upgrading is not strictly required to run experiments, adopting ES11 is vital for our growth and development as devs. It enables us to build more robust and reliable A/B tests, accelerate development and iteration cycles, and minimize technical debt. Keeping pace with evolving web… more

    11 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

    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
    Research & Design  ·  AdminDejan Dragusin (Senior Product Manager, Optimizely) responded

    This will become a project setting option.

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

12. Automatic Screenshot Generation

    Create an automatic screenshot generation feature. It would work like this:

    When enabled (via a setting that enables a "generate screenshot" button) Optimizely will load each variation - behind the scenes - including the control and create a screenshot based on the target audience. (i.e.: laptop, desktop, tablet, mobile - using average sizes or customer's defined UX design).

    The images can be updated manually if needed.

    This will save tons of time doing this manually.

    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  ·  1 comment  ·  Reporting  ·  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. Do not remove code when changing activation targets.

    Frequently I need to switch my coding / set up from a staging to a production environment. Optimizely warns me and then REMOVES all my code.

    This is fine if you are a basic non-technical user.

    It would be better if this was an optional change.

    Possibly provide a check box and a message in the button (see screenshot) - which would allow me to change the targeting.

    •  

    •  

    13 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

    Future Consideration  ·  3 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

14. UX Change: Run Time Calculator

    Masorange has requested the run time calculator to be usable without having to create an experiment first. Once an experiment is set up, the calculator can be accessed, but it was flagged as difficult to locate and sometimes they want to use the calculator ahead of set-up. The ask is to move it to a more prominent and easily discoverable location.

    4 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

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

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

17. Experiment Organization Folders

    It would be great to be able to create folders in the experiments list to group items together. (Not the sort feature). Often, I have multiple experiments (separate mobile and desktop project that are the same content) - it would be useful to be able to organize these into groups - like in a file folder system. (See mockup)

    •  

    7 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

    3 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
    Gathering Feedback  ·  AdminDejan Dragusin (Senior Product Manager, Optimizely) responded

    We are planning to redo some parts of the dashboard and the setup of certain things. As a lot of creation things will be moving into the new VE, we will be taking this into account and I will be reaching out when we get to the dashboard part.

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

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

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