This article aims to provide a comprehensive overview of the settings and practical examples utilizing easyPoints and Klaviyo.
For the article that explains what flows are, please refer the following:
Creating loyalty flows in Klaviyo
The following flows will can be used for guest purchases as well and to separate guest customers and customers that are logged in, a tag made with a Flow is required.
For further information, please refer here.
Total points and birthdays
To inform customers about allocated points, us the 'credited points' trigger with a mail notification sent each time customers gain points.
'Credited Points' should be the selected metric for the flow trigger, and the mail notification you would like to send them will be sent every time the customers gain points.
The'Credited Points' metric includes point expiration and refunds when orders are cancelled. These are selectable with the $type and you can limit the trigger to an action of your preference.
For detailed information on each $type, please refer to the link below.
For example, if you were to set the trigger with the $type equals birthday, filter, you can limit the notification to be sent to customers with the birthday rewards.
Customize mail notification for points gained or rewarded, and apply filters for specific triggers.
When using the $type manual, fulfillment, CSV, or any type that includes gaining and subtracting points, you can filter the trigger to have a filter, $point_value is greater than 0 to limit the trigger to only give out notifications for points gained.
Point expiration notification
To remind customers of points close to expiration and encourage product purchases, set the trigger to "-- days before person's $easypoints_points_expiration".
For flows with a starting date, there are corresponding ending dates. In this example, the ending day aligns with the day the points expire.
If you would like the mail to be sent multiple times, you can set the delay "wait until -- days before person's $easypoints_points_expiration" to send a second mail.
To avoid sending emails to customers who have already made a purchase due to the initial notification, ensure that "$easypoints _points_expiration is in the next -- days" is configured accordingly.
Include a conditional split to ensure that customers have points close to expiration and if they do, configure it so the mail will be sent.
Tier status notifications
Inform customers about changes in their status as soon as they occur.
If the flow trigger is set to 'Tier Status Updated', you can notify customers regardless of whether their tier has changed or remained the same.
You have the flexibility to customize emails based on whether a customer's tier has changed or remained the same by utilizing filters.
*However, this trigger or split will only be for tier changes and does not separate customers based on if their tier has gone up or down.
You can choose the trigger split '$tier-changed?' (type = boolean).
Following this, you can personalize your flow according to your preferences.
In the example below, customers who experienced a change of tiers will receive emails, while those who did not will not receive anything.
Tier demotion notification
Before sending the tier update notification, you can also send notifications who are scheduled to be demoted from their current tier.
You can encourage these customers to place orders to maintain their current tier.
To do this, begin by setting the trigger to, "-- days before person's $easypoints_tier_maintenance_deadline".
Following this, add the following flow filter "$easypoints_tier_maintenance_requirement is greater than 0" to narrow down the recipients of the notification to customers who need to spend more than 0 to retain their tiers.
Additionally, you are able to filter certain tiers that will receive the notification using the filter, "$easypoints_tier_current_tier_name equals".
Examples shown below.
Similar to the point expiration, you can add a delay and automatically verify whether the customer has made a purchase, triggering another mail notification.
The flow above starts one week before the update and 2 days before the update, each time checking if the customer has fulfilled the requirements for tier maintenance.
The image below shows an example of using "$easypoints_tier_maintenance_requirement is less than -- " which filters the required amount of money and can change the mail notification.
With this, you can effectively motivate nearing maintenance for an improved chance. The amount of money input in this filter should be calculated with the average purchase prices and average product prices.
Encourage tier advancement
It is essentially the same thing as the tier demotion flow. However, this time, adjust the trigger to, "-- days before person's $easypoints_tier_advancement_deadline" and send mails to encourage customers to achieve a higher tier.
Make sure to use the tier advancement for conditional splits and trigger filters.
Just like the tier demotion flow, this flow also starts with a date property. However, the inside varies with the property being tier advancement deadline.