70 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.
11 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 -
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 -
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 -
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 -
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 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 -
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 -
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 -
Scope Preview Tool Feed to current experiment
There's currently no setting to scope the Feed tab to a single experiment. The Feed is a project-level event stream — it surfaces every event and Page activation that fires on that URL across your entire project, regardless of which experiment you're QAing. By design, it even shows events that aren't attached to any running experiment, because the Feed references the saved project instance rather than the published CDN snippet. It'd be useful to scope the Preview Tool Feed to current experiment only.
1 vote -
Clear out Multi-armed bandit data
It would be beneficial to be able to reset the traffic allocation type after duplicating an experiment that had previously run.
Depending on the complexity of the experiment set up -- it can be time consuming to reproduce multiple variants.
1 vote -
What was running on yyyy/mm/dd?
AS
a program owner,I WANT TO
look in history in and see what was live on a specific date range,SO THAT
I can quickly produce a list of campaigns that are/were executing within a time window in case of an issue during said date range. This should include things that are concluded (or otherwise) and not showing in the active experiment space that are being executed.It is understood that this same list could be potentially be extracted by looking at history and evaluating the logs, but that is time lost in a production situation.
1 vote -
Search Functionality
It would be great if the search functionality had the ability to include custom fields. Customers have expressed that they would like to to be able to search by JIRA ticket numbers.
1 vote -
Shared Assets (Media Library)
Images are also locked inside each variation and cannot be reused across experiments. A Media Library exists, but it is a paid extra. A basic shared repository should be included as standard.
1 vote -
Opal Code Editing for Reports
Editing reports within Opal constantly reloads the HTML in Opal. Very annoying. If Opal is managing the HTML for the reports - and you're allowing us to edit -- at least let me send the update once I'm ready.
1 vote -
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 partnersFUNCTIONALITY
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…1 vote -
Multiple Linked Hypothesis from CMP HPT tasks to WebExperimentation
When we create a new task in CMP (We use HPT since it was integrated with collaboration) we sometimes use it for two separate tests that have the same objective and hypothesis but for different funnel experiences. It will be ideal to be able to add these two Hypothesis tasks to the Web Experimentation. Right now Im only able to add it once so the other test, can't see it anymore. It will also be greate to show both tests in that same task if possible. I will be creating another feedback as it is part of this as well.
1 vote -
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 -
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 -
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
- Don't see your idea?