63 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

   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  ·  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. Experiment variation preview button

   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.

   •  

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

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

9. Enable substring (contains) matching for Custom Attributes in Audience Conditions

   The "contains" operator is available for built-in attributes like Ad Campaign but not for Custom Attributes. We need substring matching on Custom Attributes to target audiences based on partial URL paths without creating individual exact-match conditions for every URL variation. This would significantly simplify audience setup for multi-page experiments. Ticket #1916403 references this request.

   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

10. Case insensitive query params and cookies

    Create a toggle to allow query params and cookie values to be case insensitivity.

    This feature is (or was) in the docs but it was not actually able to be activated.

    This feature would allow us to use different cases for key and values on query params, without having to use custom code.

    This makes it easier for marketers to create audiences without worrying about exact letter casing.

    •  

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

    Quite often, we need to track both unique and total conversions for metrics that contain multiple filters. Currently, this requires creating a new metric from scratch, which can be a time-consuming process when there are a large number of filters involved. Adding the ability to duplicate an existing metric and simply switch between unique and total conversions would save significant time and reduce manual effort.

    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

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

13. New Brand Colors Are Impossible to Read

    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

    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. Visitors to Stat Sig Missing from Unified Results Page

    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

    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

15. Experiment Analytics - Stat Sig Signifier

    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

    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. Heatmaps in Optimizely and Opal

    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

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

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

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

20. property

    Today in the Optimizely UI there is a limit of 15 properties per event and we cannot delete properties that have already been added.

    At the beginning some of our teams have created events with lots of properties but some were not so relevant in the end, or would be merged with other team's need.

    Instead of creating new event each time a property is not necessary (added by error, archived, event reshaped) so that we can have a clean list and not be blocked from adding more properties, we would like to be able to keep existing events, not passing in values for the incorrect properties and being able to edit the properties list of that event.

    Or not having anymore the 15 properties limit would also be a plus for our event management. Where archived properties would just not been sent anymore but still visible in the UI.

    Thank you

    Today in the Optimizely UI there is a limit of 15 properties per event and we cannot delete properties that have already been added.

    At the beginning some of our teams have created events with lots of properties but some were not so relevant in the end, or would be merged with other team's need.

    Instead of creating new event each time a property is not necessary (added by error, archived, event reshaped) so that we can have a clean list and not be blocked from adding more properties, we would like to be able to keep existing events, not… more

    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