74 results found
-
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.
-
Product Feedback: Make Conclusions free text searchable
As a researcher, I want to find old experiments with relevant outcomes for specific domains.
Proposal: enable the search box in the experiments list to find content in the conclusion free text.2 votes -
Product Feedback: Confidence Interval Graph
Description: Would love to see the confidence interval graphed when showing "Improvement Over Time" on my metrics. Thank you!
2 votes -
Product Feedback: AI Copy Suggestions
Description: We'd love to be able to use the AI copy suggestions with an extension. The problem is that the copy we want to enter in the extension isn't being read by the AI platform in order to make a suggestion, because it's not part of the site yet. This would be a wonderful improvement to both features!
2 votes -
Custom code Repository
I would like to request the addition of a feature in Optimizely that allows users to store custom-written code in a dedicated code repository and to export/import experiments, including custom code. This functionality would greatly enhance the ability to manage and reuse complex experiments across different projects or teams. By storing custom code in a repository, users can maintain a centralized, version-controlled collection of scripts that can be easily accessed and applied to various experiments. Additionally, the ability to export and import entire experiments, complete with custom code, settings, variations, audiences, goals, and metrics, would facilitate the replication of successful…
2 votes -
Page Properties for Enhanced Targeting and Metrics
Dear Team,
We would like to request the extension of the recently released properties functionality for custom events to include page-level implementation. This enhancement would significantly improve both targeting capabilities and metric definition for page-based analytics.
Currently, when managing numerous product detail pages (PDPs) with varying attributes such as product categories, we face limitations in creating meaningful metrics. Whilst page attributes exist, they cannot be utilised within metric definitions.
The ability to define page properties would enable us to create metrics such as "product category PDP visits" without requiring dedicated category pages or specific experimental targeting for each variant.
This…
2 votes -
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 -
Campaign Export Capability
I am working as analytics engineer in western union , we are having trouble to export the campaigns for our audit activity.
We have 100s of running campaigns in our prod project and its not feasible for all our teams to use the API end points to list more than 200 campaigns and filter Running campaigns manually from the JSON.
And our non tech team cannot do this activity and we don't have bandwidth to build application using the Optimizely api end point to get a UI for this.
We used other AB & Personalization tool and has this basic…
2 votes -
Visual Editor - Loading Improvements
Customers try to load their website in the Visual Editor and it never finishes loading
2 votes -
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 -
Guided Solutioning for Common WYSIWYG problems
There are common WYSIWYG editor problems, based on site architecture or test type. Create self-service solutioning guides for customers to diagnose and solve problem.
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…
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 -
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.
- Don't see your idea?