Rules
A rule consists of one or more events and any restrictions applied to those events. Members of a loyalty program earn outcomes by satisfying the conditions specified in a rule.
A single behavior can have one or more rules.
The following image shows a behavior with a single rule and a corresponding outcome. Members earn the outcome by completing the rule.
The following image shows a behavior with two rules and a corresponding outcome. Note that the rules are joined by an AND operator. This means that members must complete all rules in the behavior to earn the outcome. Completing just one of the rules does not earn the outcome. Members must complete both rules.
Alternatively, the rules could be joined by the OR operator. This means that members can earn either of the rules to earn the outcome.
Events
An event is an action that a member of a loyalty program performs that is tracked in the SessionM platform. An example of an event is a completing a purchase.
The SessionM platform supports two classes of events: purchase and custom.
Purchase events
A purchase event is pre-defined in SessionM platform that includes a financial transaction of some type (for example, buying an item or adding more money to a store card).
The SessionM platform supports the following types of purchase events:
Type | Event | Description |
---|---|---|
|
Purchases: Any Item | Purchases any item in the brand’s catalog. |
Purchases a defined minimum number of items. | ||
Purchases an item meeting or exceeding the defined minimum item value. | ||
Purchases a pair of defined items. |
||
Purchases a defined quantity of items. |
||
Purchases designated items. |
||
Use the promo code specified by the purchase rule to buy one (or more items). |
||
Points Per events | Purchase any items from the brand’s catalog and, if the amount spent meets the specified threshold, receive a dynamic points award based on the amount spent. | |
Points Per: Amount Spent: Specific Items | Purchase specific items from the brand’s catalog and, if the amount spent meets the specified threshold, receive a dynamic points award based on the amount spent. | |
Points Per: Item Quantity: Any Item | Purchase any items from the brand’s catalog and, if the number of items purchased meets the specified threshold, receive a dynamic points award based on the amount spent. | |
Points Per: Item Quantity: Specific Items | Purchase specific items from the brand’s catalog and, if the number of items purchased meets the specified threshold, receive a dynamic points award based on the amount spent. | |
Spends events | Spends: Total Amount | Spends a specified amount of money over one or more transactions. |
Spends a specified amount of money in a single transaction. | ||
Reloads Card event | Deposits additional money on a loyalty program’s stored value card. | |
Visits: Any Store event | Visits: Any Store event | Visits a designated store a specified number of times. |
Custom events
A custom event represents one or more occurrences of a specific member action other than a purchase that you want to track in your loyalty program. For example, an event could be enrolling in a loyalty program or completing a survey.
The only requirement is that the custom event is the format required by SessionM. Once submitted to SessionM, custom events are available for use in defining behaviors in campaigns and in building audiences.
Using custom events in behavioral rules in campaigns
You can use custom events to build behavioral rules in campaigns. Define a behavior that has an Engages in Custom Event rule. Then specify the name of a custom event that has been submitted to the SessionM platform in the Custom Event Name restriction.
The following image shows how you use the "profile_complete" custom event in a behavior.
Note that you can assign an outcome for any custom event submitted to the SessionM platform. In the image above, an award of ten points is granted to members who have completed a profile.
Core restrictions
Engages in Custom Event events are constrained by the following core restrictions.
-
Custom Event Name
Identifies the custom event used in a behavior. See Custom Event Name for a detailed description.
-
Total Number of Times
Indicates how many times that members must complete an event before earning an outcome. The default setting is 1. See Total Number of Times for a detailed description.
Ancillary restrictions
The following ancillary restrictions apply to a Engages in Custom Event event:
See the About custom events explainer for detailed information.