54 results found
-
Remove unused experiments from user profile service
Currently, user profile service (UPS) maintains a map of user IDs to the experiment IDs they've previously been exposed to and the variation ID they received. The SDKs continuously append to the UPS without any cleanup, even if an experiment has been concluded and is no longer relevant.
Customers have in the past implemented diff logic to compare the live experiment IDs in the datafile vs UPS and remove experiment IDs from the UPS that are no longer in the datafile.
2 votes -
Flag Triggers/Kill Switches
Make change to flag (e.g., toggle on/off) based on event from external system (e.g., APM alert).
2 votes -
Dependent flags
Be able to trigger flags if certain actions happen, or make flags dependent on other flags. Both stateless and stateful approaches.
2 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 -
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 -
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 -
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 -
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 -
more prominent/named link to flag/rule definition from results
As a member of a center of excellence,
I would like to see a prominent link to the rule configuration in the results page
So I don't have to explain to users all the time the most efficient manner to get back to the rule. This will decrease user frustration when trying to understand what metrics definitions are.
Most users have not figured out that the environment link takes you back to the rule itself.
1 vote -
List Flags With Rules, API Endpoint
This is a request to create a REST API endpoint that satisfies the following requirements.
A List Flags endpoint (to return all flags that returns both flags with rules (including variation names, and those with targeted delivery specifying which variation is enabled in the delivery.1 vote -
Feature to create flags template that can be used in creating custom flag
Summary:
This feature request proposes the ability to create flag templates that can be used as a foundation for generating custom flags. Templates would streamline the flag creation process, ensuring consistency and saving time when generating multiple similar flags.
Use Case:
Currently, creating flags often requires starting from scratch . This is both time-consuming and prone to errors. By introducing customizable templates, users could:
* Define reusable structures for flags, including predefined attributes and settings.
* Quickly apply these templates to generate custom flags with minimal effort.
* Maintain consistency in flag configuration across projects or teams.
Benefits:
* Efficiency:…1 vote -
Enhance efficiency of UserProfileService with decideAll(
When calling decideAll( with a User Profile Service (UPS, the method looks up the UPS for each flag.
The request is that the SDKs be updated to default to just one lookup for all flags.
This will prevent unnecessary resource consumption for customers who utilize decideAll( method and also implement/rely upon a USP.1 vote -
Archive Notification for task Watchers
When a task is archived, a notification is sent to all watchers assigned to the task.
1 vote -
Apply Audience Automatically At The Project Level
As an experimenter I would like to be able to have an audience auto populate for an entire project. The bot filtering provided within Optimizely does not exclude additional bots that we need to remove from testing as an organization, and therefore we need to apply an additional audience to our tests to remove these bots from all test. Currently we have to do this manually for every test which allows for human error. But we would like to be able to auto populate this for all feature experiments within a project to avoid this step being forgotten.
1 vote
- Don't see your idea?