68 results found
-
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)
6 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.
-
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…
6 votes -
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 -
Cut off ingestion of decision events for experiments that have already been concluded/archived.
Optimizely still captures data (decision events) for experiments that have already been archived or concluded. This data gets added to the BigQuery tables, which is undesirable. We'd prefer a cut-off, so that decisions for archived/concluded experiments do not get recorded in BigQuery.
2 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.
8 votes -
Allow changing project target URL without deleting changes
In order to support testing of more complicated experiments that require server side code changes, in tandem with experiment JS/CSS changes, please allow the changing of a project target URL without deleting all the experiment changes.
RapidX already has the ability to do this (they have a button that can bypass the change deletion behavior), meaning the use case is valid and the code has already been written. I'm not sure if it's an oversight or if there is a justifiable design reason why customers cannot do the same.
Since we control both the experiment change selectors and the server…
3 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.
4 votesWill be taken into account when reworking pages and how they operate.
-
Metric filtering on revenue or value properties
I'm a big fan of the new filter feature for metrics but would like to see this feature extended to cover standard value and revenue properties, not just custom additional properties.
A simple use case: a business wants to increase high value transactions so they set up a metric that counts transactions over a certain threshold (e.g. revenue > £200).
The workaround at the moment is to copy the values and/or revenue metrics into an additional custom property. This seems like unnecessary duplication though..
1 vote -
Show which audience a visitor matched when an Experiment has multiple audiences.
Show which audience a visitor matched when an Experiment has multiple audiences.
Both the Audience builder and the Experiments builder support OR clauses. However, there is no way to dissect the data to know which specific Audience triggered the experiment for the visitor. Our organization will run experiments where we may use a Javascript based audience and a Real-time segments audience to trigger a single experiment. The Experiment report will show the visitor to variations counts but there is no way to tell which audience the visitor matched.
The suggestion is to have a breakdown of the visitor counts, by…1 vote -
Conditional Activation: undo conditional activation from visual editor
Suggestion: a way to remove the conditional activation trigger from within the visual editor without going into the page activation (auto-generated) callback and adjusting/removing it there?
Currently this option does not exist in the Visual Editor, but would be useful if you want to undo conditional activation (easily).
1 vote -
Conditional Activation: undo conditional activation from visual editor
Suggestion: a way to remove the conditional activation trigger from within the visual editor without going into the page activation (auto-generated) callback and adjusting/removing it there?
Currently this option does not exist in the Visual Editor, but would be useful if you want to undo conditional activation (easily).
1 vote -
Conditional Activation: Select Multiple Conditions
Suggestion:
Ability to add multiple conditions.
At the moment we can only select 1 condition, but selecting multiple (2 or more) conditions would be a great add.
Use Case - Ecommerce example:
if a new user clicks over the jackets category and has an exit intent, we show them a pop up with a promotion
1 vote -
Conditional Activation: Scroll To % option
Topic: Conditional Activation
Use case: run a global experiment with a pop up, but not all pages have the same elements so we need to be able to scroll to % on the page.
Solution: Scroll To option, add the possibility to scroll to % (not just element).
1 vote -
Include ability to target html elements based on their css specificity.
Currentlh when using the Visual editor and an element is selected such as an H1, the css class or ID attributes are not accounted for in the editor.
Sometime is is necessary to be more specific, such as
H1 vs H1.classname
The idea is to include an option to use specificity and have the editor use the ID or classname based on a setting.
Such as...
Use HTML element only (H2)
Use HTML ID (#id-name)
Use HTML element + CSS Class name (H2.classname)1 vote -
Restore to previous version
Since Optimizely keeps a 'log' of changes -- why can't we have a "Restore to this version" in the history log.
It's nice to see what happened in the log, but the ability to restore to a previous version would be invaluable when editing and changes have been saved and going back a few versions is critical to avoid having to redo the entire variation setup.
See attached UX suggestion.
1 vote -
warning when changing audience
As an experimenter, I should see a warning/alert when changing an Audience in either Web or FX that is being used in an active experiment to prevent unwanted impacts on live experiments.
3 votes -
Triggering tests
It is sometimes hard to trigger a test variant when deeper into a flow. Could a bookmark be created to easily trigger a test on any given page?
2 votes -
Add a filter option for New/Returning users
I am the Product owner for our Web Experimentation tool. Our current reporting is very robust but it will also be ideal to add visitor segmentation for new/returning visitors. I have a feeling we had this before but no longer able to segment by that. We are always trying to figure out if new/returning users convert different with our variations. Is this only available via audiences? It will be nice to have them on the filters section of the tool when you are looking at the results report.
1 vote -
Variant-level audience configuration
Hello!
I often have visitors classified into different audiences accessing the same page. It would be nice to be able to experiment with different communications based on the visitor's audience. Today, to have this type of granularity, I need to set up an experiment for each type of audience.
1 vote -
Bot Blocker
We get a lot of bots that try to submit forms. Can Optimizely come up with some feature that can be used to block Bots from getting counted into an experiment?
(Not blocking site access -as our IT department can't even do that all that well)
1 vote
- Don't see your idea?