Zinrelo provides multiple personalization components in its platform to enable businesses to tailor the program to individual customer needs. One of the key personalization components is the ‘Personalization Rules’. The Rule Engine allows you to set up personalization rules based on member or transaction attributes. You can award bonus points or set up exclusion rules based on the member attributes or the transaction attributes. Click here to know about personalization rules.

One of the features that makes the rule engine so powerful is the ability to define custom attributes for members and transactions. We understand that each business will have different processes and may want to store different information against its members and transactions. This information may be used for personalization or even reporting. Zinrelo allows you to define member attributes and transaction attributes that are unique to your business.

The following section explains the types of custom attributes you can set up. If you are looking for ideas to use custom attributes, you can jump to the Use Cases.

📘

To create custom attributes for your store, write to your account manager at support.zinrelo.com.

Custom Member Attributes

Member attributes help to explain or describe the characteristics of a member. You can set up the following types of attributes for members:

• String: You can define attributes like Age, Gender, Nationality, etc.
  You can define allowed values for the string attributes. So for the gender attribute, the allowed values may be Male, Female and Non binary.
• Date: You can define attributes like Anniversary Date, Birthday Date, etc.
• Number: You can define attributes like number of reviews submitted, member age, average order value, etc.
• List: You can pass in a list of values against an attribute. For example, the magazine subscriptions that a member has could be stored in a list attribute such as Forbes, Capital, Fortune, etc.

Custom Transaction Attributes

Similar to member attributes, transaction attributes capture the characteristics of the transaction.

You can set up the following types of attributes for transactions:

• String: You can define attributes like Activity Name, Activity ID, Redemption Category, Points, etc.
  You can define allowed values for the string attributes. So for the Activity attribute, the allowed values may be created_an_account, made_a_purchase, anniversary_bonus, etc.
• Date: You can define attributes like review date, comment date, etc.
• Number: You can define attributes like stars/ likes for any comment, number of miles traveled, number of friends referred, etc.
• List: You can pass in a list of values against an attribute. For example, the channels from where activities were performed, activities tags, etc.

Different types of transactions can have different attributes. The additional information that you may want to capture when members earn points for purchases will be different from the information that you may want to capture on a discount reward redemption. So you have the ability to define a separate set of attributes for each activity and each reward.

Use Cases

Use cases for using custom attributes:

Use Case 1

Fab Apparel, an apparel company, wants to promote their new store in NY by running a campaign for Women’s day.

They can create two member attributes- ‘Gender’ and ‘Location' and populate the appropriate values in these attributes for each of their members. Then they can run a campaign targeting all Females in NY using the campaigns module or the personalization rules.

Use Case 2

Fab Apparel wants to see how customers are redeeming the points across all their stores. They can define a custom attribute called ‘store_location’ in each of their rewards and pass the location of the store in this attribute whenever a redemption transaction is recorded.
This will enable them to create a report of redemptions by the store location.

Use Case 3

Wonder Blossoms, an online florist, wants to award bonus points to members using a WB Platinum credit card for their online purchases. They can create a custom attribute called 'credit_cart_type' against the purchase activity in their program. Whenever they record purchase transactions in the loyalty program, they should update the type of card used in this attribute. Using the personalization rules, they can award bonus points for any purchase transactions that use the WB Platinum credit card.