Release Date: Apr 17, 2019.
New Features
1. User Group Loyalty
- A user group includes one primary member and multiple secondary members.
- All members will be in the same tier as the primary member. The tier will be changed (either upgrade or downgrade) for a secondary member when he/she makes a purchase or when joining the group.
- Upgrade primary member based on the cumulative purchases of group members (if the upgrade is based on lifetime purchases)
- On purchases made by a secondary member, points could be issued to the secondary member and the primary member of the group.
- When a secondary member leaves a group, his/her tier will be downgraded to the lowest tier
- New events introduced: Group Member Join, Group Member Leave, Group Transaction Add, Group Transaction Update, and Group Return Transaction.
2. Rules on Extended Fields
With this release, Loyalty Manager supports rules on customer-level and transaction-level, and transaction-line item level extended fields.
- Rule expressions on customer-level extended fields are available in all rule sets across events using the profile currentCustomer.
Example: currentCustomer.extField_dob and currentCustomer.extField_gender.
- Rule expressions on transaction-level and transaction line item-level extended fields are available for TransactionAdd and transactionUpdate events under the profile currentTxn.
Example: currentTxn.extField_NPS and currentTxn.extField_tax_amount. - Rules expressions on transaction line item level extended fields are available under the profile currentLineItem.
Example: currentLineItem.extField_additional_discount and currentLineItem.extField_serial_number. - Operators vary based on the data type of an extended field. For example,
- for a date data type, say currentCustomer.extField_dob, you could use .dayOfMonth, .year, .day, or .month.
- for a string data type, say currentCustomer.extField_gender, you could use .contains or .exists.
- for a double data type, say currentTxn.extField_tax_amount, you could use >, =, or <.
Example: currentCustomer.extField_dob.isValid( )&¤tCustomer.extField_dob.month()==12 |
- Limitation: Tags corresponding to extended fields are not supported in communication message templates
3. Support for Customer Lables
- Ability to write ruleson customer lables using currentCustomer.includesLabelR
egex - Example: currentCustomer.includesLabelR
egex("HNI") - Use Case: Allocate 2% points to the high-spending customers (grouped using the label 'HIGHSPENDORS') and 1% points to the remaining customers.
- Rule Expression - currentCustomer.includesLabelR
egex("HIGHSPENDORS") - When 'TRUE' - Allocate Points action - 2% Points Allocation strategy
- When 'FALSE' - Allocate Points action - 1% Points Allocation strategy
- Rule Expression - currentCustomer.includesLabelR
- Example: currentCustomer.includesLabelR
- Ability to tag labels to the customers on an event using the action Tag Customer in the rule-set
- Use Case: If a customer purchases an iPhone, tag the label IPHONE_BUYERS
- Label Name - IPHONE_BUYERS
- On the TransactionAdd event use transaction item unroller. Write a condition to check if the transaction consists of iPhone, set the action as Tag Customer and select the label IPHONE_BUYERS
- Use Case: If a customer purchases an iPhone, tag the label IPHONE_BUYERS
Enhancements
Disabled Tier Downgrade Reminders for Tiers with Always Downgrade Strategy
- If the downgrade strategy for a particular tier is set as 'Always' downgrade after tier duration, no downgrade reminder will be sent to the customers before the downgrade.
- This does not impact tiers that has When condition. The downgrade reminders for tier downgrade with When condition will continue to work as per the schedule