67 results found
-
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 -
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 votesConcluding experiments should prevent decision events, investigating.
-
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 -
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 -
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 -
Dashboard Experiment Overview
I constantly get requests from product manager or other team members asking, "What is running on the site in Optimizely". Not everyone has access to look at the reporting dashboard/program overview.
The idea is for a view that can be shared and configured by an Optimizely Admin - and then can be shared. No login is needed for this view.
The view can contain a number of items (similar to the current program overview) and could be filtered by the admin to only show experiments that are relevant to the business goals or the view's audience.
1 vote -
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.
-
Multi-Armed Bandit Screenshots
When running MAB's -- the screenshots of the variations get erased, during the reallocation of the traffic.
New screens shots are not needed every time the MAB resets the traffic distribution.
1 vote -
Integrations blocking deleting concluded experiments
When removing an integration (turning it off), it warns the user for any published, paused experiments, and tell them to archive. It would be helpful if "concluded" experiments would also be considered as a valid option, so we don't have to archive concluded tests to turn off an integration
1 vote -
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.
1 vote -
Google Tag Manager Template (push custom events)
I am a UX Developer. I am trying to create a template within Google Tag Manager to make it easier for team members to push custom events to Optimizely Web Experimentation. Unfortunately due to GTM sandbox restricts, direct execution of methods on global objects like optimizely.push is not possible. There are a few possible ways to resolve this, which could include:
- Expose a queue-style global object
- Provide a GTM-friendly wrapper
- Publish an official GTM Custom Template
1 vote -
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
- Don't see your idea?