74 results found
-
Deployed experiments (winner rollout) should be active in Preview mode for other experiments
Deployed experiments (winner rollout) should be active in Preview mode for other experiments.
Currently, when an experiment is concluded, and the winning variation is deployed, this deployed variation is active for all visitors on the website. However, when Previewing another/new experiment, that deployed experiment is not active.
Since the deployed variation should be considered the "is-state" of the website, and it is publicly visible to regular visitors, it should also be visible in the Preview mode.
1 vote -
program reporting data
As an experimentation program manager in an experimentation COE with no access permissions to build a system to assess API data but with access to data tools that I can use to build out queries and dashboards.
I want to be able to access meta information on experiments (the same data set accessible via the API) in my s3 (bigQuery, etc.) feed.
So I can build queries and dashboards to assess and report on the health of the program, create alerts, etc.
1 vote -
event / metric tagging
As an experimentation program manager in an experimentation COE
I want to be able to 'tag' events/metrics with properties like 'funnel', 'engagement', 'conversion'. This information should be available via export in some manner - s3 type of export preferably.
So I can analyze the metrics use in experiments to better understand what our teams have been / are focusing on and understand the health of the program better.
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: 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 -
Metric Selector
The new metric selector has made the process of selecting metrics take a long time.
1 vote -
List Experiments endpoint - filter by experiment status
Please add the option to filter results by status of the experiment.
1 vote -
Display run dates for archived experiements
For archived experiments, it would be helpful to quickly see the experiment's run dates (start and end without having to dig through event history.
1 vote -
Device sizes out of date
It would be great to see updated device sizes in the visual editor especially for mobile as these are too small for screen sizes people use today. I'm not a developer so I rely on the screen size builder to verify changes but when I look at my iPhone, pages look different most of the time. I've used Optimizely for 7 years and I haven't seen these sizes updated.
1 vote -
Charlie testing feedback
Testing this feedback
1 vote -
Automatic Check Off Box for GTM in Integrations Tab of an Experiment
Had a customer respond that it did not make sense that there were so many checkboxes for the GA4 Integration in the Experiment > Integrations tab. The GTM check should be checked by default or be part of a global/project setting instead of Experiment level.
1 vote
- Don't see your idea?