80 results found
-
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.
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.
11 votes -
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…
9 votes -
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 -
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 -
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 -
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 -
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…
6 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.
4 votes -
Add new JSON field type to templates
Add a new JSON field type to templates.
Currently templates support multiple field types like text and textField but it would be great to add JSON support.
It would increase readability and validate for formatting errors right away3 votes -
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.
3 votes -
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.
3 votes -
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 -
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…
3 votes -
Page Properties for Enhanced Targeting and Metrics
Dear Team,
We would like to request the extension of the recently released properties functionality for custom events to include page-level implementation. This enhancement would significantly improve both targeting capabilities and metric definition for page-based analytics.
Currently, when managing numerous product detail pages (PDPs) with varying attributes such as product categories, we face limitations in creating meaningful metrics. Whilst page attributes exist, they cannot be utilised within metric definitions.
The ability to define page properties would enable us to create metrics such as "product category PDP visits" without requiring dedicated category pages or specific experimental targeting for each variant.
This…
3 votes -
Visual Editor - Loading Improvements
Customers try to load their website in the Visual Editor and it never finishes loading
3 votes -
Improved QA monitoring of test variations
Prospects that have had tests "break" their site want an automated solution for monitoring the quality of their test variations in production, and to be alerted immediately when there are issues that negatively impact UX.
3 votes -
Support CIDR and Regex IP Filtering to Prevent MAU Consumption
Allow customers to exclude entire IP ranges using CIDR notation (e.g., 43.172.0.0/16) or regular expressions to prevent unwanted traffic from contributing to billable MAUs.
Business Impact:
Manually maintaining hundreds of IP exclusions is not scalable, especially with evolving automated traffic. More flexible filtering would reduce administrative overhead and help customers manage MAU consumption more effectively.
2 votes -
The new result page variation should allow variation reordering
The variations on the new results page appear confusing, as they do not reflect the configured setup. Being able to reorder the variations on the new results page would be helpful.
2 votes -
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!
2 votes
- Don't see your idea?