65 results found
-
Folder System for Optimizations
As an experimenter I would like the ability to sort my experiments and personalization campaigns into folders based on my own criteria. For my use I would have folders based on the area of the site we are testing (ie. homepage, category page, product detail page or pages based on the person who is working on the experiment (ie. John, Sally, Bob, Pam.
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 -
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.
2 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…
2 votes -
search for
Feedback from client: I want to be able to search for an old test on the results dashabord just once, rather than have to search for it within each status category.
2 votes -
Campaign Export Capability
I am working as analytics engineer in western union , we are having trouble to export the campaigns for our audit activity.
We have 100s of running campaigns in our prod project and its not feasible for all our teams to use the API end points to list more than 200 campaigns and filter Running campaigns manually from the JSON.
And our non tech team cannot do this activity and we don't have bandwidth to build application using the Optimizely api end point to get a UI for this.
We used other AB & Personalization tool and has this basic…
2 votes -
Export code based on conclusion
Once a test is concluded, export the changes as a set of code in HTML+CSS+JS, or React, etc. Has come up several times in the past month. Suggest investigating whether competitors do this.
2 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.
2 votes -
Guided Solutioning for Common WYSIWYG problems
There are common WYSIWYG editor problems, based on site architecture or test type. Create self-service solutioning guides for customers to diagnose and solve problem.
2 votes -
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 -
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
- Don't see your idea?