74 results found
-
Add Filter Options for Production/Development Environment + Archived/Non-archived Reports
As a data analyst/product manager, I require a comprehensive overview of our experimentation programs within the reporting system. Currently, the system lacks clarity in the following areas, hindering my ability to effectively analyse experiment performance:
* Production Environment Filtering: I need the ability to specifically filter for experiments running in the production environment. This ensures I'm analysing data that reflects the actual user experience and provides valuable insights into real-world impact.
* Archived Experiment Filtering: A clear distinction between archived and non-archived experiments is crucial. This allows me to:
** Exclude irrelevant or invalid experiments from my analysis.
** Compare…1 vote -
Add Alt Attribute Field for Image Uploads in Optimizely Web Visual Editor
A customer has raised a concern about the inability to add an alt attribute to images uploaded via the Optimizely Web UI. To comply with accessibility standards, they currently use a manual workaround: uploading an image, copying the CDN link, creating an HTML element with the link and alt text, and hiding the original image.
Proposed Solution:
Add a field in the image upload dialog for users to input alt text, which would automatically be included in the image's HTML.
Benefits:
* Simplifies accessibility compliance.
* Saves time by removing the need for manual workarounds.
* Enhances inclusivity and aligns…1 vote -
Ability to save a template as a favourite
When building an optimization variation, Change HTML content is no longer a primary option within the Create Change menu. This is the primary template I use and I now have to do a lot of extra clicking as each time I have to select it from Browse Templates. If the ability to add favourite templates was added it would allow me to be a lot more time efficient with my builds.
1 vote -
Variant-level audience configuration
Hello!
I often have visitors classified into different audiences accessing the same page. It would be nice to be able to experiment with different communications based on the visitor's audience. Today, to have this type of granularity, I need to set up an experiment for each type of audience.
1 vote -
Bot Blocker
We get a lot of bots that try to submit forms. Can Optimizely come up with some feature that can be used to block Bots from getting counted into an experiment?
(Not blocking site access -as our IT department can't even do that all that well)
1 vote -
Dashboard Experiment Overview
I constantly get requests from product manager or other team members asking, "What is running on the site in Optimizely". Not everyone has access to look at the reporting dashboard/program overview.
The idea is for a view that can be shared and configured by an Optimizely Admin - and then can be shared. No login is needed for this view.
The view can contain a number of items (similar to the current program overview) and could be filtered by the admin to only show experiments that are relevant to the business goals or the view's audience.
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 -
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 -
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 -
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 -
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 -
Visual Editor - Dynamic Selector
Customers attempt to use the visual editor to make persistent changes, but the changes do not persist throughout the entire user journey as the selector changes either on reload or if new DOM elements are present on different pages.
1 vote
- Don't see your idea?