Zinrelo provides a sophisticated personalization rule engine that allows you to define rules and exceptions for awarding points for each activity. This gives you the option of defining your own business rules for each transaction and reward.

Activity Rules

To set up the activity rules, you have to go to Program Settings >> Activities >> Activity for which the rules have to be set.

The rule engine works on the conditions, its categories, and actions.

This is how the rule engine works:

• If any activity matches all or any of the set conditions, then the set action will be taken.
• These conditions are set on Member and Activity Attributes.
• There are different categories under each attribute on which we can set conditions on. Like transaction tags, user tier, available points, birthday, etc.

And each category has their operators which are selected on the basis of the requirements. For example:

• If the category is ‘Date’ like Enrollment Date, Birthday, Last Points Earned Date, etc., then its operators could be Relative (more than, less than, etc.) and Absolute (after, before, on, etc.)
• If the category is ‘Number’ like Number of Reviews, Number of Purchases, etc., then its operators will be less than, greater than, equals and between.
• If the category is ‘String’ like member tags, city, nationality, etc., then its operators will be equals, not equals, in and not in, contain all of, contain any of, etc.

Note: The date added to the end date will be excluded from the business rules when using the 'between' operator. Only the start date and a date before the end date will be considered.

For example, if a business rule of 'Award bonus points in multiples of base points' is applied to all receipts uploaded between 26/08/2022 and 30/08/2022. Then, all receipts uploaded on or after 26/08/2022 and before 30/08/2022 will be applicable for the rewards. But the receipt submitted on 30/08/2022 will be excluded from the rewards. Only base points will be rewarded for it.

Please Note: You can add only 1 exclusion rule to an activity. If you want to have multiple parameters for exclusion, user 'IF - Match any' condition.

Use Cases

Use Case 1-Wonder Blossoms, an online florist company, wants to run a promotion campaign on Women’s Day for their product ‘Blue Rainbow’ especially for US citizens. Wherein the citizens will be rewarded with 10x bonus points if they buy ‘Blue Rainbow’ from the website on 8th of March.

To set this rule, Wonder Blossoms will select the following conditions:

Activity- Purchase on Website

1. Product Category- Blue Rainbow
2. Transaction Date-8th March
3. Nationality- American

Note: To reward the bonus points to US citizens, Wonder Blossoms will create a custom attribute- ‘Nationality.’

They will select ‘Match All’ for these conditions, as all of the set conditions have to be met.

Finally, they will select the action ‘Award bonus points in multiples of base points’ and enter the bonus points that are to be awarded.

Use Case 2- Wonder Blossoms wants to award 3X fixed points to everyone on their birthday in the month of January 2022.

To set this rule, Wonder Blossoms will select the following conditions:

Activity: Purchase on website

Transaction date: January 2022

Birthday: in the transaction month

Members who make transactions in the month of January 2022 and whose birthday falls on that month will get 3X fixed points.

Rewards Personalization Rules

You can set business rules on rewards on the basis of Redemption Frequency, Transaction and Member Attributes.

To set rules of rewards go to Program Settings>> Rewards>> Select the rewards you want to configure>> Manage Rules.

Note: To know how to configure the program rewards, click here.

Use Cases

Use Case 1- If available points<10, frequency>10 in a day and frequency>100 in a month. In this case, you can use the "match any" condition and set multiple frequencies for a day and a month.

Use Case 2- A one-time ‘Gold Tier Welcome’ reward has been configured. Members are able to redeem this reward when they upgrade to the Gold tier. However, this reward is available for redemption only once. So after a member has redeemed this reward, the reward should be hidden from that member.

For this use case, two rules have to be set. First, hide the reward from Platinum and Silver tiers, as this reward is only for Gold tier members. Second, you have to set redemption frequency.

Use Case 3- The loyalty program caters to both B2B and B2C members. The type of member is identified at the time of enrollment and the attribute ‘membership type’ is updated with the appropriate value. B2B members should not see the discount rewards offered to B2C members.

Use Case 4- To run a successful promotion, members in the loyalty program have been assigned different tags. Members with the tag "Redemption Made" should not see the discount rewards.

📘

Please Note:

Please ensure that you enter the category names without using apostrophes or special characters. The category name should be entered exactly as it is, without any special characters.