65 results found
-
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.
8 votes -
CSV Export of Experimentation Configuration Data
I was speaking with a customer who expressed a desire for the ability to generate a CSV export of Experimentation Data straight from the Experimentation UI. I believe this would be tremendously useful, and is something that will significantly benefit the utility of the product.
6 votes -
CSP Errors visibility in visual editor
Currently the visual editor gives no feedback when it doesn't load it. The dev console will show this but the user thinks there's a bug on the Optimizely side.
Displaying a visible error "We weren't able to load in the visual editor, please update your Content Security Policies <error>" would really help a lot of users understand what's happening6 votes -
Display "Link URL" field on custom elements with a href attribute
Today, when selecting an <a>-element in the visual editor, a Link URL fields appears so that editor can change the href.
We are running custom web components for links on our site, they can look something like this: <gds-button href="./link">Title</gds-button>
When selecing gds-button, its possible to edit the Title in the Visual Editor but not the Link URL.
There are workarounds such as modifiyng the whole html or using script. But this is not optimal for editors without coding knowledge. Therefor it would be very useful if the Link URL field could be shown for all element types as long…5 votes -
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…
5 votes -
Bring the Sample Rate Calculator into Test Build
Its inconvenient navigating back and forth
5 votes -
Global holdout group
The ability to set up hold-out groups, which would allow users to separate a percentage of their user base and exclude them from any experiments or feature launches. This feature would enable users to assess the long-term impact of all cumulative launches made by their team.
4 votes -
Better client/UI for viewing and amending HTML
Currently amended or inserted HTML is displayed in a narrow strip to the left of a page which makes it hard to amend and debug. It would be better if the HTML could be viewed in a wider window and if the HTML was formatted nicely so that it was easier to see start and end tags of div's etc.
4 votes -
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)
4 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.
4 votes -
Product Feedback: Experiment Overview
requester joanna.guise@tfs.com
Type of issue: Product feedback
Jo Guise sent a feedback.
Description: It would be useful on the experiment overview tab to have a 'significance %' column, so we can see at a glance how close things are to completion
User email: joanna.guise@tfs.com
User id: IhQP2_vkRualxopsTdqLRQ
Account: The Fragrance Shop Buying Ltd.
Account id: 30340d56-f563-7e35-923a-ea544c6e9b5b
https://u44077338.ct.sendgrid.net/wf/open?upn=u001.UBmjMNjeoRXVAL5fZIj9r2FPj0g8IcH4DdrYL4fPfah4D3R0lViKImdF1fmAOOcaRyeBR6LSEO6zS6tfDSs06Qujo19RxJL6zEvVbzeCVGlMQLHLia9JXsijyREobzYH8087FUi9hyuGsDcM0ICbV4GrZfNkRaHKQGELGRh27vjfHAr0VvlBQ4ES6d2rVLNI4IL-2FvcBEnpqjkNQu49-2FDJFxkhsmBh0yOwHjuluW7e6QI1683bhHmyoTJrSiZoBG43 votes -
warning when changing audience
As an experimenter, I should see a warning/alert when changing an Audience in either Web or FX that is being used in an active experiment to prevent unwanted impacts on live experiments.
3 votes -
Tool should flag when a test is low power (ie not likely to reach stat sig)
State exactly why it was flagged; would likely require customer to input some data
3 votes -
Custom Labels (Owners, Next Steps, Jira Link, Figma Link, etc.)
Give customers the ability to create own labels to attach to experiments, and make these columns you can add in the overview, as well as making it filterable and sortable. This feature would help create ownership of experiments
3 votes -
Product Feedback: Make Conclusions free text searchable
requester frank.herberg@verivox.com
Type of issue: Product feedback
Frank Herberg sent a feedback.
Description: 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.
User email: frank.herberg@verivox.com
User id: 7ae23f47b03511e3850221c527b629ae
Account: Verivox GmbH
Account id: fa3676ce-787e-a4f6-2213-b39f6216060c2 votes -
Product Feedback: Confidence Interval Graph
requester ewoods@cargurus.com
Type of issue: Product feedback
Eric Woods sent a feedback.
Description: Would love to see the confidence interval graphed when showing "Improvement Over Time" on my metrics. Thank you!
User email: ewoods@cargurus.com
User id: tJ04GKlvT8iYKCCIEqhUnA
Account: CarGurus, Inc.
Account id: a73c197e-cc9f-2fc9-0640-82fbb19008322 votes -
Product Feedback: AI Copy Suggestions
requester sroman@petsmart.com
Type of issue: Product feedback
Sarah Roman Sarah Roman sent a feedback.
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!
User email: sroman@petsmart.com
User id: CpWHGlxFRbCDwgTlbx-4nA
Account: PetSmart, Inc.
Account id: 463491db-9b27-9934-8503-af550783befb2 votes -
Persist Show/Hide Column Preferences for Experiment List (WebX, FX & Edge
Summary
Allow users to save their customized "Show/Hide Columns" preferences in the Experiment List view so that these settings persist across sessions and after refreshing or navigating away from the page.
Background
A user has reported that changes made to the "Show/Hide Columns" settings in the Experiment List view do not persist. Currently, when users adjust column visibility to suit their needs, these preferences are reset when they leave the project or refresh the page. This behavior disrupts workflow efficiency and requires users to repeatedly reconfigure their view.
User Impact
* Pain Point: Users must repeatedly adjust column settings, which…2 votes -
MAU Consumption Notification
Hi Team,
To manage Experimentation MAU Consumption I would like to request a notification functionality that alerts customers when a certain percentage of their allotment has been consumed so as to we can ensure that Overages are avoided in a timely manner and contracts can be right sized accordingly.
While Consumption monitoring is a part of governance it can at times be overlooked and having a notification leads to a better customer experience and minimizes the chances of not being able to pick anomalies in a timely manner.2 votes
- Don't see your idea?