Events represent single occurrences of individual customer actions. Each customer session contains one or more events. For example, a referral being created or a coupon being rejected can be defined as events.
There are different types of events:
Talon_session_created: The session was opened. For example, the customer created a cart.
Talon_session_updated: The session was updated. For example, the customer added a new item to the cart.
Talon_session_closed: The session was closed. For example, the customer checked out.
Talon_session_cancelled: The session was cancelled. For example, the customer left before checking out.
Talon_session_revoked: The session was updated after it was closed. For example, the customer requested a refund.
Learn more about events in our Developer docs.
The Events page in the left-side menu of the Application displays all the events of this Application. It contains the following information:
|Time||Date and time when the event happened in the timezone of the Application.|
|Customer ID||Unique identifier of the customer profile associated to the event. It can be used for integration purposes. It is the same across all Applications.|
|Session ID||Unique identifier of the customer session where the event happened. It can be used for integration purposes. It is unique for each Application.|
|Effects||Number of effects triggered for the event.|
Click the checkbox to the left of each row in the Events page to see further information on an event:
- Attributes: Event attributes and their value. They indicate whether the session is new for the event and provide details on the payload.
- Campaign: The names of the campaigns where the rules containing each effect triggered for the event were built.
- Rule: The names of the rules each effect belongs to.
- Expression: The name of the effect in the response and the values set for the effect.