92 results found
-
results page versions
AS An
experiment analystI WANT TO
save the settings of the results page including start/end time, segments, etc... and have it accessible via share link and also as a link displayed on left sideSO THAT
i can share detailed and specific findings with others easily and return to the ones i've created easily.1 vote -
Block Publish When Experiment Uses Archived Event or Metric
We found an experiment can be published even though it referenced an archived event.
Request:
Please add pre-publish guardrails so experiments cannot be published when they reference archived component dependencies.
Expected behavior:
- Block publish if any linked event, metric, or required page dependency is archived
- Show a clear warning with the archived item names
- Provide direct links to fix or replace each archived dependency before publishThis would prevent avoidable debugging and protect experiment data quality.
1 vote -
results display improvements
AS A
experiment creator and reviewerI WANT TO
improve the results page by increasing the context available for visitors that get to the page from a shared results link and may lack context into what the actual experiment is.
1. upload an image of the control and variant to the results section/page per variation or re-use the upload in variations list.
2. include hypothesis - could be input as part of the metrics screen
3. include notes - could be input as part of the metrics input. should allow inclusion of links so that references to other documentation -…1 vote -
stand-alone image upload
AS AN
experiment builder that utilizes the code editor 95% of the timeI WOULD LIKE TO
be able to upload images that are used in the variant without having to create a change in the editor to access the image uploaderSO THAT
my build process makes more sense and I don't create an unecessary change that I then have to delete after I upload the image and get the URI.1 vote -
hiding early results
AS AN
experimentation governance and operations managerI WOULD LIKE TO
be able to 'hide results' for a time by experiment to avoid devs and partners reviewing an experiment and disseminating detailed results before we have anything near conclusive. Having a project wide settable baseline would be good along with the ability to manage it at the experiment layer. Base layer should still be displayed such as visitors, split percentages, SRM, etc... Conversion rates and success metrics should not be shown until the hide time has passed. Admins should always see all metrics.SO THAT
I can avoid negatively impacting…1 vote -
Duplicate Pages
I want to have the ability to duplicate a page. Often times the page configuration is similar, for example when creating pages across environments. However, because Page duplication is not possible this causes a lot of additional work by setting up pages from scratch.
3 votes -
Adjustment of permissions for users without publishing rights
Enable publishing with a test cookie / audience as priority. The Editor role should inherit all Publisher permissions except standard publishing, but should be able to publish when a specific audience/test cookie is applied.
Enable restoring experiments from the archive.
Allow setting experiment end dates.
Provide permissions to edit Pages.
1 vote -
Enhance Search Functionality
Currently, its capabilities are limited in two main areas:
Query Handling: The search processes only the first word of a multi-word query. For instance, a search for “Headers for PDP” will only return results matching “Headers.”
String Matching: The search requires a complete word match and does not return results for partial strings. For example, searching for “experi” will not find items containing the word “experiment.”
These factors reduce the discoverability of specific experiments, particularly in projects with a large volume of tests which is causing friction and frustration.1 vote -
Request to Extend Session Timeout
Kaufland has raised concerns about the current session timeout behaviour in the app. Users are automatically signed out after 30 minutes of inactivity, which results in them having to log in multiple times throughout the day. This is causing frustration and negatively impacting the user experience.
Kaufland would like the option to increase the session timeout window, or make it configurable, so users can remain logged in for longer periods without interruptions.
1 vote -
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.
9 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…
4 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.
2 votes -
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
- Don't see your idea?