Conditions of pattern events
For both Qualifying and Suspending events, you can define conditions for an event.
Although, an event is selected for a pattern, but it is only eligible to participate
into the pattern evaluation when all event conditions are met. A condition is a
Name/Value pair which can be passed into postEvent API as parameters in runtime
environment. This provides marketers another flexibility to control event patterns at
runtime. The conditions can be defined for macros as well.
Note: From Unica Interact 12.1.2 onwards, a same event can be selected for a pattern
multiple times. The pattern conditions can be used to differentiate them. For
example, one event can be event "addToCart" with condition of "product = 'iPhone'",
while another event can be event "addToCart" with condition of "product =
'iPad'".
Tracking in-activity using event pattern
An event pattern can not only be evaluated for “condition-met”, but can also be evaluated for “condition-not-met”. Marketers can use this feature to track customers’ in-activities. For example, a pattern has two events, “add_item_to_cart” and “checkout”, all must occur in seven days. Marketers can add check point on third day, if customer has not checked out the item yet, that is, pattern’s state is “condition-not-met”, then an action of “send_reminder_email” would be executed for the customer.