23 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…
7 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.
7 votesWill be taken into account when reworking pages and how they operate.
-
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 -
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.
9 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 votesConcluding experiments should prevent decision events, investigating.
-
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.
3 votes -
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 -
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 -
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 -
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 -
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 -
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 -
Tool should flag when a test is low power (ie not likely to reach stat sig)
State exactly why it was flagged; would likely require customer to input some data
3 votesThis may be something we consider giving Opal the power to do next year. Currently gathering input from customers.
-
Custom Labels (Owners, Next Steps, Jira Link, Figma Link, etc.)
Give customers the ability to create own labels to attach to experiments, and make these columns you can add in the overview, as well as making it filterable and sortable. This feature would help create ownership of experiments
3 votes -
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 -
Audience Conditions: Ad Campaign
Role: Onboarding Solution Architect
Issue:
For the Audience Condition Ad Campaign "When selecting Visitor does not come from, it is a common interpretation that anyone who comes to a page, except those from an ad campaign would be selected. But this is not true. Instead, the user must come from an ad campaign, just not the one you specify to be targeted. "Request:
Change this audience condition to match the intuitive and common interpretation "common interpretation that anyone who comes to a page", essentially to evaluate anyone and not just those visitor coming from an ad campaign.This would…
1 vote -
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
- Don't see your idea?