23 results found
-
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.
-
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 -
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 -
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.
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…3 votes -
Product Feedback: Make Conclusions free text searchable
As a researcher, I want to find old experiments with relevant outcomes for specific domains.
Proposal: enable the search box in the experiments list to find content in the conclusion free text.2 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!
2 votes -
Product Feedback: AI Copy Suggestions
Description: We'd love to be able to use the AI copy suggestions with an extension. The problem is that the copy we want to enter in the extension isn't being read by the AI platform in order to make a suggestion, because it's not part of the site yet. This would be a wonderful improvement to both features!
2 votes -
Custom code Repository
I would like to request the addition of a feature in Optimizely that allows users to store custom-written code in a dedicated code repository and to export/import experiments, including custom code. This functionality would greatly enhance the ability to manage and reuse complex experiments across different projects or teams. By storing custom code in a repository, users can maintain a centralized, version-controlled collection of scripts that can be easily accessed and applied to various experiments. Additionally, the ability to export and import entire experiments, complete with custom code, settings, variations, audiences, goals, and metrics, would facilitate the replication of successful…
2 votes -
variation editor option to publish directly
As an experiment builder that generally uses the code editors and who uses the cookie and querystring model for qa and works with intricate code that is load dependent and requires more than a few updates to get working properly within the actual site code
I would like to have the ability to publish the variation update on the variation screen (perhaps a 'publish' button)
So I don't have to save the code changes, then go to main experiment screen and publish and then navigate back to the variation and wait for the page (which will fail because it is…
1 vote -
Support for rearrange tests on Dynamic websites
Optimizely Web Experimentation does not currently support rearrange tests (tests that swap the positions of nodes in a document on dynamic websites but may extend support in the future.
Adding support will mean elements in Dynamic pages can be rearranged and the objects will be re-applied like the other support for changes.1 vote -
Shortcut to turn off interactive mode
I often have customers that struggle to change fly-out menu's. They have to select the interactive mode to open the flyout, but then they can't select an element as they have to turn off the interactive mode. By moving out of the flyout to turn off interactive mode this closes the flyout again however, meaning they can never select an element in these flyouts.
If there was/is a shortcut to quickly turn off interactive mode that would solve this I believe.1 vote -
Shared code - double scroll bar
On the Shared Code section, when the code is too long, you get a double scroll bar on the right. It is not particularly problematic, but it bothers the UX a bit.
1 vote -
Result reset warning should include the name of the test
To avoid accidentally resetting the wrong test, it would be helpful to include the name of the test whose results are being reset in the warning message.
1 vote -
More matching rules for custom/external attributes
Currently you can only match "has" or "does not have". The attribute is always just a string, can we have REGEX and "contains" rules on this?
This would make audience creation a lot easier with less work to manually add all possible options you want to include.
e.g. language /en-gb/ or /en-us/. I want to just make sure it includes "/en-" but currently I have to add every possible value in there1 vote -
Metric Selector
The new metric selector has made the process of selecting metrics take a long time.
1 vote -
List Experiments endpoint - filter by experiment status
Please add the option to filter results by status of the experiment.
1 vote -
Display run dates for archived experiements
For archived experiments, it would be helpful to quickly see the experiment's run dates (start and end without having to dig through event history.
1 vote -
Automatic Check Off Box for GTM in Integrations Tab of an Experiment
Had a customer respond that it did not make sense that there were so many checkboxes for the GA4 Integration in the Experiment > Integrations tab. The GTM check should be checked by default or be part of a global/project setting instead of Experiment level.
1 vote
- Don't see your idea?