101 results found
-
Bug Fix
Bug Fixes on text editor (mainly shared code)
Native find on page doesn't work reliably (sometimes shows more occurrences than there actually are, doesn't jump to the place in the code when you hit enter)
- Would be great to implement that properly
Starting typing at all makes the current line jump to the bottom of the screen, which is really frustrating and quite confusing.
- Ideally just keep the scroll position what it is when you start typing.
(I'm using Chrome on Mac OS)
1 vote -
Version control
A slightly better interface of what changes have been made before committing. I know you can view history, but it's not that easy to understand. Being able to see lines of code that have changed in each of the shared js, shared css and variations would be very helpful, rather than just the number of lines changed.
1 vote -
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 -
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 -
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 -
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).
2 votes -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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.
4 votes -
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 -
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
- Don't see your idea?