Events
Last updated
Last updated
Examples of events:
A call to the call center;
Password recovery request;
Subscription to mailing;
Item X appeared in stock;
Failed advance payment.
There are two types of events:
Customer event is an event that is only relevant to one specific customer, for example, "A customer called the call center”. This particular customer called the call center.
System event is an event that is relevant to ALL customers. It is not tied to any specific customer. For example: "Item X is in stock" – you can notify everyone, who was interested in this item, about this event appearing in stock.
Every event has a name.
Event may or may not contain a context. Context is a set of variables and their values. Event context does not change over time (unlike receipt, where composition or status can change).
Events are displayed in the timeline in the customer's profile:
Transfer of events in the Platform is done via integration.
Events can be used for filtering when building segments in the segment builder ("Show customers who have events with these characteristics X times in period Y").
You can select customers based on the following criteria related to events:
Event name;
Date of event;
Date of last event;
Days since last event;
Event context.
The filter by event context allows you to select customers who have events with the specified values of the specified variable. For example: name = Alphabet. Such a filter will select all customers that have event with a context that has a variable name and it is equal to the value Alphabet.
Campaigns have two triggers activated by events:
Event X has occurred;
System event X.
An example of using the System event trigger:
Event context can be used in Campaigns in the following actions:
Filter customers;
Send message (e-mail / SMS / push).
Field codes must not contain a hyphen '-'.
To filter customers using value from the event context, in the field filtering you should refer to context by specifying the code of that field preceded by a $ sign.
Example:
To use value from the event context when sending message, use the{{client.eventContext.field_code}}. Example:
