Skip to content

Feature Experimentation

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

5 results found

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Analytics/Results Page  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?