Skip to main content

Displaying events

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.

Event types

There are different types of events:

  • When the Update customer session endpoint receives a request:

    Event name
    (Rule Builder event type)
    Trigger criteria for the event
    talon_session_created
    (Customer Session Creation)
    • The state property is either open or closed.
    • The request includes a new integration ID.
    Example: The customer creates a cart.
    talon_session_updated
    (Customer Session Update)
    The state property is open.

    Example: The customer adds an item to the cart.
    talon_session_closed
    (Customer Session Closing)
    The state property is closed.

    Example: The customer checks out.
    talon_session_cancelled
    • The state property is cancelled.
    • In the preceding request, the state property was open.

    Example: The customer leaves before checkout.
    talon_session_revoked
    • The state property is cancelled.
    • In the preceding request, the state property was closed.

    Example: The customer requests a refund.
  • When the Return cart items endpoint receives a request:

    Event nameTrigger criteria for the event
    talon_session_partially_returnedThe state property is closed.

    Example: The customer returns some of the items and expects the corresponding refund.
  • The Update customer profile endpoint receives a request with runRuleEngine=true:

    Event name
    (Rule Builder event type)
    Trigger criteria for the event
    talon_profile_created
    (Customer Profile Registration)
    The request includes a new integration ID.
    talon_profile_updated
    (Customer Profile Update)
    The integration ID was sent to Talon.One in a previous request.

Listing events

The Events page in the left-side menu of the Application displays all the events of this Application. It contains the following information:

ColumnDescription
TimeDate and time when the event happened in the time zone of the Application.
EventEvent type.
Customer IDUnique identifier of the customer profile associated to the event. It can be used for integration purposes. It is the same across all Applications.
Session IDUnique identifier of the customer session where the event happened. It can be used for integration purposes. It is unique for each Application.
EffectsNumber of effects triggered for the event.

Event overview

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.
  • Effects:
    • 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.