Consider the following example:
A loyalty program has two tiers, normal and loyalty. Customers need to spend at least 100 lifetime purchases to upgrade from a normal tier to the loyalty tier.
- Tier Upgrade : Eager Mode and tier needs to be upgraded when the lifetime purchases amount exceeds 100.
- Points Allocation:
- For transactions made in Mumbai stores, issue 2% of transaction amount as points to the loyalty customers during 10 AM to 4 PM from Monday to Friday (non-peak hours) and 1% for rest of the time (peak hours).
- For transactions in the stores other than Mumbai, issue 2% of the transaction amount as points
- Points Expiry: One year from the points issued date
To configure the above loyalty program, do the following:
- On the Tier Upgrade tab, set upgrade based to Lifetime Purchases and upgrade type to Eager. Then create the two tiers and set the lifetime purchases amount required for upgrading from Normal to Loyalty as shown in the screenshot below
- Open the Points Allocation tab and create two different allocation strategies - one with 1% of the transaction amount and the other with 2% of the transaction amount
- Then, on the Points Expiry tab, create points expiry strategy and set the expiry to 12 months from the event date (points issued date) as shown below
- Click EventView and configure events and rules. You need to create a separate set for each condition you need to validate. Set a Forward to set for satisfying each condition and define the action to be performed in the last set. For example, in the screenshot below, the action to be performed for Set1 it is defined Set4 and for Set7 it is defined in Set7
- Select the Event as New Transaction
- In the following example, Set1 (a master set) is created which will check the conditions defined in Set2 (to check whether a transaction is made in Mumbai and visited during non-peak hours) and Set7 (to check whether the customer is not from Mumbai)
- Apply Store Level Scope to the set and select store(s) belonging to Mumbai. Tip: Set the button to Include and select the store(s) that are in Mumbai. You can also upload store codes through csv file using StoreCode csv option
Note: If you use both the options - select stores and also upload store codes - then the priority is given to the StoreCode csv option
- Now, set the condition to check whether the transaction is made during the non-peak hours, i.e., Monday - Thursday between 6 am - 4 pm. If yes, set the points allocation strategy that corresponds to 2% of the transaction amount; if false, set the points allocation strategy that corresponds to 1% of the transaction amount
- Now same as above configurations, for Set 7, set a store level scope and select the stores that are not in Mumbai and click Save Scopes. Tip: Set the button to Exclude and select the store(s) that are in Mumbai
- As no other condition needs to be verified, set Expression and Expression Equals as true as shown below and set the allocation strategy that issues points of 2% of the transaction amount
- Set the allocation strategy that issues points of 2% of the transaction amount.
- Click Save to save the recent changes made in the loyalty program.
- Then click Reconfigure to affect the changes made in the loyalty program.