26 results found
-
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…
3 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)
3 votes -
Multi-Armed Bandit Screenshots
When running MAB's -- the screenshots of the variations get erased, during the reallocation of the traffic.
New screens shots are not needed every time the MAB resets the traffic distribution.
1 vote -
Integrations blocking deleting concluded experiments
When removing an integration (turning it off), it warns the user for any published, paused experiments, and tell them to archive. It would be helpful if "concluded" experiments would also be considered as a valid option, so we don't have to archive concluded tests to turn off an integration
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.
1 vote -
Google Tag Manager Template (push custom events)
I am a UX Developer. I am trying to create a template within Google Tag Manager to make it easier for team members to push custom events to Optimizely Web Experimentation. Unfortunately due to GTM sandbox restricts, direct execution of methods on global objects like optimizely.push is not possible. There are a few possible ways to resolve this, which could include:
- Expose a queue-style global object
- Provide a GTM-friendly wrapper
- Publish an official GTM Custom Template
1 vote -
Audience Conditions: Ad Campaign
Role: Onboarding Solution Architect
Issue:
For the Audience Condition Ad Campaign "When selecting Visitor does not come from, it is a common interpretation that anyone who comes to a page, except those from an ad campaign would be selected. But this is not true. Instead, the user must come from an ad campaign, just not the one you specify to be targeted. "Request:
Change this audience condition to match the intuitive and common interpretation "common interpretation that anyone who comes to a page", essentially to evaluate anyone and not just those visitor coming from an ad campaign.This would…
1 vote -
adobe analytics integration
Set clear expectations with necessary visuals of screenshot in the Help documents. It is quite confusing now, leaving room for interpretations.
1 vote -
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.
3 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 -
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 -
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 -
URL conditions for saved pages
I create experiments for a major retailer, and current URL substring match capabilities force me to use JS conditions or callbacks for all campaigns on my PDPs and category pages. This is tedious and makes it difficult for non-technical teammates to run experiments.
For example, many retailers use structures like retailer.com/p/ to indicate PDPs and retailer.com/c/ for category pages. However, using those in the substring match fields will include all substrings with a "p" or "c" since the backslashes are not accounted for, opening up the test for many, many more visitors than we would anticipate. For example, the visitor…
1 vote -
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 -
Geo-testing
The ability to split tests based on geographical region so that we can test the effectiveness of region-specific marketing campaigns, two-sided marketplaces, or faciliate other testing use cases when we cannot guarantee a user will be in solely the control or test variant.
1 vote -
Support for Numbers (floats, integers) in Custom Audience Attributes
Currently Web Experimentation Audience Attributes only support values as string types. Adding support for number values (floats, integers) would allow for more complex and granular audience membership.
Customer provided example: An audience for visitors who have less than 100 subscriptions. The Audience Attribute numSubscriptions would be a number value of the total number of subscriptions the visitor has. This attribute could be used to build an audience for all visitors with less than X (ex. 100) subscriptions.
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 -
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 -
Bring the Sample Rate Calculator into Test Build
Its inconvenient navigating back and forth
5 votes -
Visual Editor - Changes overwritten in Preview by the site
The changes work when you are in the tool , but do not actually work in the wild. Something overwrites the code from the customer's website.
1 vote
- Don't see your idea?