54 results found
-
Enhanced Search Functionality in Optimizely Experimentation
Problem:
Currently, the search function in Optimizely Experimentation only filters by a single word, even if multiple words are entered. For example, if a user searches for “Headers for PDP”, the results only return matches for “Headers”. This limits discoverability and forces users to rely on entering very specific single keywords.Proposed Solution:
Update the search functionality to apply all words entered in the query, rather than restricting results to the first word only. This way, users can perform both broad and specific searches as needed.Reasoning / Business Impact:
For customers running numerous tests, Efficiently searching and reviewing experiments…10 votes -
New Booleans in the Decision Object
It would be easier to have some Boolean values in the decision object, which would simplify recognizing the exact status of a visitor (e.g., whether they are in the "off" variation or the "everyone else" category, or in the concluded/deployed "on" variation). "Enabled" and "variationKey" are not enough to distinguish the above cases.
Currently, they need to check string values and match specific values like "rollout-default" or "deployedtdl" which is not ideal. Booleans would be easier.
2 votes -
Folder/Organization System
I would like the ability to create folders within projects to organize our work. This would allow users to organize work by developer or by area of the site.
5 votes -
Date as an Attribute Type
For our experiments, we have a custom attribute that represents when a user signed up to our platform. Currently, we encode the values we receive for this as 8 digit numbers (YYYYMMDD) because Feature Experimentation audiences do not allow for attributes to be Date values. It would be a nicer experience for our users to be able to use a Date type rather than a Number type for attributes when creating audiences.
1 vote -
default value variables can be changed as editor impacting production
As an editor, I am not allowed to change Production values, including variation variables.
However, I can still update the "Default" value of a variable and that will affect all environments including Production if the default is in use.
1 vote -
navigation
In feature experimentation it would be good to be able to add custom fields to each experiment. For instance location or team - this way teams can easily filter to their experiments to reduce noise
1 vote -
Archive events in archived projects
The list events endpoint currently returns all events, including those from archived projects. This becomes problematic when there are a large number of such events. Could you enhance the archive project functionality so that it also archives the events within the project?
3 votes -
custom content in ui
role: COE lead for experimentation
problem: lack of exposure to internal processes and standards and changes to them
outcome: i would like to be able to insert custom text into the UI at various points, including but not limited to:
* flag list
* create flag overlay
* flag page - ruleset list
* rule definition page
* audience list
* audience creation screen
* attribute list
* attribute creation screen
* event list
* event creation screen
* etc.basically anywhere you create, define, update and/or name things.
the intent is to provide content that descibes the current standards…
1 votethis should be achievable via custom fields for at least flags and rules
-
flag relationships
I manage platform use.
I am trying to make it easier for users to see all related flags that might be used for a single delivery.
I would like a way to list 'related flags' somewhere in the flag definition. there can be multiple flags related to multiple flags. one flag might have a few different relations. the relation list should be links to prod environment page for the defined related flag.1 vote -
Rule Promotion/Copy
As a rule administrator in feature experimentation, I want to be able to move a single rule between environments without have to copy all rules from one environment to another and having those all reset to draft in the target environment.
3 votes -
logic
Current limitation:
When setting up logic for a template, users can only apply the AND condition. This restricts flexibility because it prevents combining AND and OR conditions within the same template.Why this matters:
Most systems allow both AND and OR options so that users can build more complex logic in a single template. Without this capability, users are forced to create multiple templates for different workflow scenarios instead of managing everything under one template using combined AND/OR logic.1 vote -
Visibility into flag usage
Depending on the number of teams operating in FX, tech debt accumulates quickly if not managed. Help customers determine how and when to consider tech debt in their FX endeavors.
Some customers struggle with outdated flags that have not been used in a while, but it is hard for them to determine which ones are outdated.
Help customers understand how their users are reacting to a new feature rollout.
5 votes -
It would be useful to see which active experiments are using a particular audience/attribute
It would be useful to see which active experiments are using a particular audience/attribute
1 vote -
Audience Visibility Control
Role: Technology Specialist - Product Architect
What we you trying to solve:
We manage a multi-OpCo organization using a single Optimizely instance with isolated production environments per market/region. I've submitted a separate feature request for environment visibility control to address UI clutter and prevent users from seeing irrelevant environments.
Following that solution, audiences/segments also need OpCo-scoping. Currently, audiences remain globally shared across all users, creating problems in multi-OpCo setups:
- Cross-OpCo interference - OpCo A can accidentally modify or delete audiences used by OpCo B
- UI pollution - users see irrelevant audiences from all markets when configuring targeting
- Risk of mis-targeting…
1 vote -
Environment-Based Visibility Control for Multi-OpCo Organizations
Role: Technology Specialist - Product Architect
What are we trying to solve:
Currently, all users see all environments in Optimizely regardless of relevance. For our multi-OpCo setup with 40+ isolated production environments (one per market/region), this creates:
- UI clutter - users must navigate through dozens of irrelevant environments
- Training overhead - OpCo representatives need extensive onboarding to identify their specific environments
- Poor UX - cannot create role-specific views for different markets
- Risk of confusion - users might accidentally interact with wrong environment
We cannot use separate Optimizely instances per OpCo because with 100+ flags across 40+ instances, this would require…
1 vote -
Use Custom Event Properties for ratio metrics
Hello!
We very much appreciate the arrival of ratio metrics. However, they do provide limited value to us as long as Custom Event properties are not usable for either numerator or denominator.
It would be awesome to see that added.
Role: I am the Team Lead for our experimentation center-of-excellence and infra team.
3 votes -
How long to get statistical significance
When the platform says another 50k users to reach significance, could a date be added? E.g. it has taken 3 weeks to get to 25k so give the date in 3 weeks as the date when the 50k will be reached
4 votes -
Provide SRM monitoring on the results page
Hey!
As Team Lead Web Analytics I often see teams struggling to solve SRM issues.
It would be immensely helpful if the results interface would provide a graph depicting the user distribution between variants. This seems like a low-hanging fruit for Optimizely and would facilitate debugging SRMs strongly.
Thanks!
1 vote -
Results to Experiment Details Page Navigation Improvement
When you click on the Results button of a specific experiment, you want to be able to navigate from the results screen to the Experiment details page. Instead, currently, you have to go back to the main list of experiments, then find your specific experiment, to click into the details.
1 vote -
Versioning within an Experiment
A versioning capability within an experiment, so that when you are building, if someone makes unintended changes, they can revert back to the old version. There is interest in this feature both in the visual editor and for general changes in the experiment around page, audience, etc. These could be tackled separately.
1 vote
.png){kind=link}
- Don't see your idea?