57 results found
-
Display bucketing ranges in the GUI (when changing traffic allocation)
I know that Optimizely tries to keep bucketing consistent when traffic allocation and or distribution changes.
It would be great to be able to see the bucketing allocation (eg. 1-5000 for A, 5001-10000 for B) in the interface.
In this example it is simple, but when ramping up (and possibly at the same time changing the distribution of traffic) it would be great to be able to verify via the interface which buckets are being set.
I am aware of Customer Profile Service but I see this as independent from that.1 vote -
Disable losing variant(s) during experiment
As of now, in Feature Experimentation, if a variant performs (very) bad, there is no way to deactivate it or set its behavior back to baseline without needing to create a new rule.
This of course slows down experimentation speed.
I do understand that the results of that variant are not usable after setting a variant's behavior back to baseline behavior. However, that is not the issue. The goal is to simply be able to continue letting the test run while disabling a bad-performing variant.1 vote -
Audience integrations
To enable FX personalization, be able to pull audiences from other tools.
3 votes -
Built-in attributes for frontend/client SDKs
Similar to Optimizely Web, capture basic segmentation (browser, device, ...) out of the box.
3 votes -
Custom Fields/Tags
It's hard to manage flags/tests at scale without being able to group them and capture more metadata on them.
3 votes -
Datafile Relay Proxy
If Optimizely's CDN goes down or is inaccessible, the SDKs don't have a default fallback mechanism to evaluate feature flags without access to the datafile hosted on the CDN.
It's possible to initialize the SDK with a cached datafile, but that requires custom logic. Ideally, Optimizely could provide a default mechanism to provide a fallback datafile (e.g., a "relay proxy" service that caches the datafile, or a default mechanism within the SDKs).
1 vote -
Introduction of filters
It would be great to have some kind of filters that allow a deeper dive into data. So if we wanted to see how many people bought a licence AFTER triggering a specified conversion
1 vote -
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 -
Observability/guardrail metrics
Help customers understand how flags/experiments are affecting site performance.
1 vote -
Events integrations
Customers want to have metrics they track in their analytics in Optimizely. Today they have to manually add new event instrumentation. Would be great to integrate with other analytics and import their event tracking in Optimizely (ie. similar to Segment integration)
1 vote -
Environment Filter for Webooks
Filter activity notifications via webhook to only production environment.
1 vote -
OpenFeature SDK Support
Make SDKs compatible with OpenFeature standard.
1 vote -
Event Inspector/Debugger
Ability for developers to enable an event inspector to ensure instrumentation is working correctly
1 vote -
Dependent flags
Be able to trigger flags if certain actions happen, or make flags dependent on other flags. Both stateless and stateful approaches.
1 vote -
Introduce concept of Feature Flag Types
Almost none of my customers implement long-term flags. Every time they run a new experiment, they create a new flag, and remove it after. Even if they could have reused the flag for a new experiment a month later. This creates a lot of additional work.
1 vote -
Ability to Redesignate the Primary Environment in Feature Experimentation
A customer has requested the ability to change the primary environment in Feature Experimentation after the initial project setup. Currently, the primary environment is automatically assigned and cannot be modified, which has led to ongoing frustration for their team.
They would like the ability to:
* Reassign the primary environment to another existing environment within the project.
* Make this change via the UI or API with appropriate safeguards (e.g., confirmation prompts, permissions.1 vote -
Serve previous revisions of datafiles from Optimizely CDN
As a web developer I need to ensure that every point in a request lifecycle uses the same version of an Optimizely datafile to ensure a page is rendered correctly. This includes:
* edge function logic
* serverside render
* clientside hydration
If there is a mismatch in Optimizely datafile versions between edge function logic and serverside render, then the incorrect decision could be used to generate a page that is saved into the CDN cache. If there is a mismatch in Optimizely datafile versions between the serverside render and the clientside hydration, then hydration mismatch bugs will occur.
Optimizely's…4 votes -
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 -
Add "name" field to FeatureFlag object in datafile
I would like to ask if it's possible to add a "name" field to the FeatureFlag object in in datafiles/xxxxx.json which is having all the configured feature flags there.
To give some more context on the structure I'm talking about:
{
...
"featureFlags": [
{
"id": "123456",
"key": "experiment_key",
-> "name": "Experiment name", <- NEW FIELD HERE
"rolloutId": "rollout-1233456",
"experimentIds": [],
"variables": []
}
...
],
...
}
New "name" field would be having a value of the name of the related flag.
I'm guessing it could be not available there by default because of privacy/security reasons, but if that's…1 vote -
Product Feedback: New UI post-mortem ;-D
requester chase@weedmaps.com
Type of issue: Product feedback
Chase Dutton sent a feedback.
Description: When you guys launched the new UI, it confused the heck outta every developer at Weedmaps and we had many product incidents where a flag was misidentified as being off when it should have been on, or vice versa.
This confusion wasn't due to any bugs in Optimizely or Weedmaps, just the new UI was visually confusing all who encountered it.
Anyways we're doing much better now, but yea just wanted to share that feedback. If it confused 100% of our 60+ devs I'm sure it confused…2 votes
- Don't see your idea?