71 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 -
Experiments average run-time
The customer would like to have the following information available in the Admin Center: average experiment run-time
2 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.
-
Run Time Calculator Accessibility
My customer wants the run time calculator to be usable without having to create an experiment first.
Once an experiment is set up, the calculator can be accessed, but it was flagged as difficult to locate and sometimes the customers wants to use the calculator ahead of set-up. The ask is to move it to a more prominent and easily discoverable location.Personalisation Campaigns
The calculator cannot be used for personalisation campaigns because these are measured differently. However, needing sufficient traffic to detect meaningful change—still applies. Therefore, the customer would like a similar tool or guidance for personalisation tests to…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 -
experiment publish note
AS an experiment builder and program manager,
I WOULD LIKE to be able to add a custom note each time I publish an experiment in both web and feature experimentation and have that note show up in history as part of the list view and details
SO I can more easily find changes in history by seeing the note displayed in the history list and associate changes to ticketing systems when appropriate.
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.
3 votes -
allow navigator.sendBeacon() calls for events in web experimentation
As an experiment builder
I would like to utilize the navigator.sendBeacon API to send events to Optimizely
So I can ensure all events are accounted for and my metrics are more complete and likely to match internal measures of same.
https://developer.mozilla.org/en-US/docs/Web/API/Navigator/sendBeacon
1 vote -
Improved clarity around scheduled experiments
As an experimentation user, I want the UI around scheduled experiments to more clear about the experiment status.
Currently, the experiment status is either "Not Started" or "Paused". It would be great if the experiment status instead was simply "Scheduled", or alternatively "Paused (Scheduled)" / "Not Started (Scheduled)".
Additionally, when changing a paused scheduled experiment, there is a warning "Publish your experiment if you want your draft changes to go live on the scheduled date.". However, when clicking Publish, the preferred option "Publish Only" is not highlighted and instead "Publish and Start" is highlighted. This might cause someone to accidentally…
1 vote -
Ability to track MAU consumption per project when using Custom Snippets
Currently in admin centre the reporting available for MAU's per project does not provide data if the customers projects were set up using custom snippets. As custom snippets are a popular way to set this up, it would be great to be able to able to report on this.
1 vote -
variation editor option to publish directly
As an experiment builder that generally uses the code editors and who uses the cookie and querystring model for qa and works with intricate code that is load dependent and requires more than a few updates to get working properly within the actual site code
I would like to have the ability to publish the variation update on the variation screen (perhaps a 'publish' button)
So I don't have to save the code changes, then go to main experiment screen and publish and then navigate back to the variation and wait for the page (which will fail because it is…
1 vote -
variation screen editor page load option
As a builder of web experiments that always uses the code editors or targets locations inaccessible to the editor
I would like to have a setting that stops/blocks the page load every single time you pull up the variation code. It would be nice to be a persistent setting that could either stick to the variation or to my login.
So I don't have to click through error messages that are not relevant every time I go to edit.
1 vote -
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
- Don't see your idea?