83 results found
-
Missing preview url in new visual editor
The "share preview" is missing in the new editor. Once the old VE is retired, how do we share the changes with other team members for review?
1 vote -
Delete Change feature in new Visual Editor
Delete change feature is buried in the new UX. Add a "delete change" feature in the main view (suggested at top). See screenshot for visual example
1 vote -
metrics
As an experiment builder and analyst
I would like to create advanced ratio metrics by combining events in the numerator and denominator.
Importantly, if the metric in a ration metric is custom, I need to be able to set custom properties in their definition.
So that I can more easily and accurately define my target metrics without extra work.
Use case: i use a custom property called 'environment' that sets 'dev','qa','prod' so I can distinguish between events in different environments. Without that property, ratio metrics cannot utilize the event.
1 vote -
New Editor -- Have option to position at top of page and control the background of the editir for visibility
Be able to have the editor at the top of the page. And add controls to alter the visual editor's color so that it can be seen easier on white pages. (Mockup uses red for example).
2 votes -
Mutually Exclusive Manager
It would be nice to be able to preset up the Mutually Exclusive experiments without saving them and possibly have it start/stop at a specific time.
1 vote -
Experiment change notification
I would like to have a notification set up for a list of users whenever a new test is set to go live or set to pause.
I am aware that there is an existing approval feature that sends approval request to a list of users. However this is not fit for purpose due to the extra steps created in the publish workflow.
We would like to have a standalone notification feature to allow key stakeholders to be notified of key experiment changes without creating too many extra steps to the current flow of the release.
7 votes -
Prioritization of Experiments and Personalization Campaigns
Problem Statement (The "Why"):
I need an easy way to manage the hierarchy of experience delivery across overlapping audiences. Currently, Optimizely allows for experience prioritization within a specific Personalization Campaign, but it lacks a "Global Air Traffic Control" for the entire Web project.
When I have multiple experiments or personalizations live on the same page (e.g., the Homepage), there is no native way to ensure that a high-value visitor (like Enterprise or Mid-Market) is prioritized into a specific experiment before being eligible for a general "All Traffic" A/B test.
Current Workaround (The Pain Point):
To achieve this today, I have…
2 votes -
property
Today in the Optimizely UI there is a limit of 15 properties per event and we cannot delete properties that have already been added.
At the beginning some of our teams have created events with lots of properties but some were not so relevant in the end, or would be merged with other team's need.
Instead of creating new event each time a property is not necessary (added by error, archived, event reshaped) so that we can have a clean list and not be blocked from adding more properties, we would like to be able to keep existing events, not…
1 vote -
Automatic Screenshot Generation
Create an automatic screenshot generation feature. It would work like this:
When enabled (via a setting that enables a "generate screenshot" button) Optimizely will load each variation - behind the scenes - including the control and create a screenshot based on the target audience. (i.e.: laptop, desktop, tablet, mobile - using average sizes or customer's defined UX design).
The images can be updated manually if needed.
This will save tons of time doing this manually.
1 vote -
CSS code validation
As a frequent user of the code editor and a builder that surrounds each of the variants I build with their own unique DOM ID so that I can prefix each CSS rule with same ID and eliminate any possibility of style bleed into other areas of the page
I would like to see some of the current CSS validation remarks related to ID use removed. the list includes the following but their may be more:
1. 'don't use ids as selectors' (as it is 100% valid CSS and actually faster in the rendering engine)
2. 'really, 2 ids?' -…1 voteThis is something that hasn't been reviewed in some time.
We plan to rework how developers work with WEB later this year. We will take this into account.
-
reusable/transportable variants in web experimentation
As a user building variants in web experimentation,
I would like to be able to save and reuse variants across campaigns, pages and projects while deciding at the campaign/page level whether to allow the selected version to stand apart or be kept in sync (copy local versus linked). Localized from linked save could require a new name but retain the link to the original and allow for a button to copy the parent for resync/update needs.
So that I can more easily have a dev, qa, prod environment setup in web experimentation.
This would likely require that variants live outside…
2 votes -
Title: Improving Revenue Experiment Accuracy for High-Variance Transactions
Optimizely currently defines revenue outliers using a fixed threshold of mean + 3 standard deviations. This approach works well for classic e-commerce use cases with stable pricing, but it becomes less reliable in scenarios where transaction values are inherently unpredictable.
In donation-based fundraising—and in other models with variable or open-ended transaction values (e.g. donations, contributions, pay-what-you-want, grants, or memberships) - there is no fixed price catalogue. As a result, a small number of very high transactions can disproportionately influence revenue and average gift metrics.
After reviewing this with our analysts and experimentation team, we found that applying a mean +…
1 vote -
UX Change: Run Time Calculator
Masorange has requested 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 they want to use the calculator ahead of set-up. The ask is to move it to a more prominent and easily discoverable location.
3 votes -
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 -
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 voteThis is planned, Q3 at latest.
-
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
- Don't see your idea?