Skip to content
← Turn your feedback into functionality

Settings and activity

1 result found

  1. Add Rule and Variation IDs to Decision Object

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Research & Design  ·  2 comments  ·  Feature Experimentation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    AdminNicolai Antonov (Manager, Technical Support - Tier 2, Optimizely) commented  · 

    While the decision object returned from the SDK currently provides the flag status, variation key, and rule key, there is currently no built-in way to determine whether the rule that returned the decision was an A/B test or targeted delivery. A workaround would be to use specific naming conventions for different rule types, but it would be useful to have this information baked into the decision object by default.

    An error occurred while saving the comment
    AdminNicolai Antonov (Manager, Technical Support - Tier 2, Optimizely) commented  · 

    While the decision object allows you to see which rule delivered a feature, it does not specify whether this rule is an A/B Test, Targeted Delivery, etc.
    Customer naming conventions could theoretically provide this kind of context, but we've received a request from Nike to make this available in the SDK itself.