92 results found
-
Edge Delivery with Fastly CDN
I am the Product Manager at Hearst Magazines.
Our current Web Experimentation implementation is set up with the snippet in the <body> tag, which causes significant flicker for experiments involving changes above the fold.
Your new Edge on CDN feature could be a game changer for us. However, the blocker is that we currently use Fastly CDN, which is not supported by your Edge product.12 votes -
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.
9 votes -
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.
9 votes -
Improved QA plug-in
Customers use the Chrome Plug-in often for debugging, QA and forcing themselves into variations. It does not always work, and is pretty limited.
9 votes -
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…
8 votesThis will become a project setting option.
-
CSV Export of Experimentation Configuration Data
I was speaking with a customer who expressed a desire for the ability to generate a CSV export of Experimentation Data straight from the Experimentation UI. I believe this would be tremendously useful, and is something that will significantly benefit the utility of the product.
7 votes -
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 votesWe 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.
-
CSP Errors visibility in visual editor
Currently the visual editor gives no feedback when it doesn't load it. The dev console will show this but the user thinks there's a bug on the Optimizely side.
Displaying a visible error "We weren't able to load in the visual editor, please update your Content Security Policies <error>" would really help a lot of users understand what's happening6 votes -
Display "Link URL" field on custom elements with a href attribute
Today, when selecting an <a>-element in the visual editor, a Link URL fields appears so that editor can change the href.
We are running custom web components for links on our site, they can look something like this: <gds-button href="./link">Title</gds-button>
When selecing gds-button, its possible to edit the Title in the Visual Editor but not the Link URL.
There are workarounds such as modifiyng the whole html or using script. But this is not optimal for editors without coding knowledge. Therefor it would be very useful if the Link URL field could be shown for all element types as long…5 votes -
Clone Experiments across Projects
I propose adding a feature to Optimizely that allows users to clone experiments across different projects. This would streamline workflows by enabling users to replicate successful experiments without manually recreating them. The cloned experiments should include all settings, variations, audiences, goals, and metrics, with options to adjust project-specific parameters. This feature would enhance efficiency, promote consistency, and improve the overall user experience.
5 votes -
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…
4 votes -
Product Feedback: Experiment Overview
Description: It would be useful on the experiment overview tab to have a 'significance %' column, so we can see at a glance how close things are to completion
4 votes -
Persist Show/Hide Column Preferences for Experiment List (WebX, FX & Edge
Summary
Allow users to save their customized "Show/Hide Columns" preferences in the Experiment List view so that these settings persist across sessions and after refreshing or navigating away from the page.
Background
A user has reported that changes made to the "Show/Hide Columns" settings in the Experiment List view do not persist. Currently, when users adjust column visibility to suit their needs, these preferences are reset when they leave the project or refresh the page. This behavior disrupts workflow efficiency and requires users to repeatedly reconfigure their view.
User Impact
* Pain Point: Users must repeatedly adjust column settings, which…4 votes -
Global holdout group for WX
The ability to set up hold-out groups, which would allow users to separate a percentage of their user base and exclude them from any experiments or feature launches. This feature would enable users to assess the long-term impact of all cumulative launches made by their team.
4 votes -
Better client/UI for viewing and amending HTML
Currently amended or inserted HTML is displayed in a narrow strip to the left of a page which makes it hard to amend and debug. It would be better if the HTML could be viewed in a wider window and if the HTML was formatted nicely so that it was easier to see start and end tags of div's etc.
4 votes -
See Deployed Variations with Active Tests
I would like to easily see deployed variations from winning tests alongside Active/Running tests. Since deployed variations are only visible in the Concluded section, it's easy for them to get lost.
4 votes -
Custom Labels (Owners, Next Steps, Jira Link, Figma Link, etc.)
Give customers the ability to create own labels to attach to experiments, and make these columns you can add in the overview, as well as making it filterable and sortable. This feature would help create ownership of experiments
4 votes -
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.
3 votes -
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.
3 votes -
Product Feedback: Confidence Interval Graph
Description: Would love to see the confidence interval graphed when showing "Improvement Over Time" on my metrics. Thank you!
3 votes
- Don't see your idea?