The DECISION notification listener is triggered by the Decide methods. It is most commonly used to send decisions to an analytics provider or to an internal data warehouse to join it with other data that you have about your users.
If you only want decisions that resulted in impressions in the Optimizely app, you can filter on the dispatched decision event field of the returned OptimizelyDecision object in your code.
To track flag usage:
- Sign up for an analytics provider of your choice (for example, Segment).
- Set up a DECISION notification listener.
- Follow your analytics provider's documentation and send events from within the decision listener callback.
Steps 1 and 3 are not covered in this documentation. However, the DECISION notification listener is covered below.
The following tables show the information provided to the listener when it is triggered:
|type||string||Decision type varies depending on which method triggers the listener.|
The Decide methods set the type to
|decision info||map||Key-value map that consists of data corresponding to the decision. See decision-info parameter.|
|user ID||string||The user ID.|
|attributes||map||A map of custom key-value string pairs specifying attributes for the user that are used for audience targeting.|
Non-string values are only supported in the 3.0 SDK and above (released after March 2019).
The following table shows the decision info parameter of the DECISION notification listener:
|Decision info parameter||Description|
|flag key||The flag key.|
|enabled||Boolean value for whether the flag is enabled or not.|
|variables||The same object as returned by |
|variation key||The key of the flag variation.|
|rule key||The key of the flag rule.|
|decision event dispatched||A Boolean value indicating if the decision dispatched a decision event to |
In the Optimizely app, an impression on the Results page corresponds to a dispatched decision event.
For code examples, see the notification listener topic in your SDK language:
Updated 10 months ago