Skip to content
← Turn your feedback into functionality

Feature Experimentation

Feature Experimentation

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Welcome! 👋

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

12 results found

  1. Audience integrations

    To enable FX personalization, be able to pull audiences from other tools.

    1 vote
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  2. 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
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  3. Built-in attributes for frontend/client SDKs

    Similar to Optimizely Web, capture basic segmentation (browser, device, ...) out of the box.

    1 vote
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  4. Environment Filter for Webooks

    Filter activity notifications via webhook to only production environment.

    1 vote
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  5. OpenFeature SDK Support

    Make SDKs compatible with OpenFeature standard.

    1 vote
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  6. Event Inspector/Debugger

    Ability for developers to enable an event inspector to ensure instrumentation is working correctly

    1 vote
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  7. Flag Triggers/Kill Switches

    Make change to flag (e.g., toggle on/off) based on event from external system (e.g., APM alert).

    1 vote
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  8. 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
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  9. 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
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  10. Custom Fields/Tags

    It's hard to manage flags/tests at scale without being able to group them and capture more metadata on them.

    1 vote
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  11. Observability/guardrail metrics

    Help customers understand how flags/experiments are affecting site performance.

    1 vote
    New  ·  0 comments  ·  Admin →
    How important is this to you?

  12. 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.

    1 vote
    New  ·  0 comments  ·  Admin →
    How important is this to you?
  • Don't see your idea?