Add Rule and Variation IDs to Decision Object
Currently, the decision object returned by an SDK's decide method includes the flag, rule, and variation keys that a user was bucketed into but does not return the (experiment rule and variation key that the user was bucketed into.
Grant Matthews
shared this idea
-
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.
-
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.
