Sequence events

A sequence event detects when two or more events occur in a specified order in the session. The sequence event is used to detect that they fired and that they fired in a specific order. This event fires on the first detection of the sequence in the completed session.

  • Sequence events may be evaluated in any trigger of the session. Sequence events that are evaluated in the End of Session trigger are always evaluated after dependent events in the trigger were evaluated.

Suppose there are three events: Add to Basket (A), Error (B), and Purchase (C). In a session, the sequence of events occurs in the following order: A, A, B, A, C, A, B. For a specified event sequence of A,B, the events fires in the session even though Event A occurs again after Event B was fired for the first time. The event fires even though the visitor added an item to basket after the error, but they did not receive another error before the purchase.

All sequences are evaluated independently of each other. In this manner, you can create nested sequences.

Note: Events that occur on the same hit are always considered to be in the proper sequence.
Note: If you are mixing hit-based events and step-based events in your sequence, you should set the trigger to evaluate the event on After Every Hit or End of Session. If the trigger is Every Hit, the event is evaluated before the steps that are part of the event, and the sequence may not be properly evaluated.
  • Step-based triggers can be created based on data that is submitted from the Discover client frameworks. See "Step-Based Eventing" in the Unica Discover Event Manager Manual.

Before you define an event of this type, you need the following information:

  • Each event and the sequence to test