Configuring Program Activities

Here is quick overview of the built-in activities that can be configured through the Zinrelo console:

Navigating to the Activity Configuration section

The link to the activities configuration section is in the ‘Program Settings’ tab. You can edit the in-built activities, create custom activities and activate / pause any of the activities in this section.

Configuring Activities

The configuration for any activity, whether in-built or a custom activity, consists of two parts. These are done in the respective sub-tabs in the activity configuration.

• Basic Settings
• Activity Rules

Basic Settings

The screenshot below shows the default fields in the Settings tab of any activity configuration. Some of the activities built into the Zinrelo platform have additional fields in this section. The in-built activities along with their additional configuration fields are explained in the ‘In-built Activities’ section in this document. The default fields are explained below.

• Points: Number of points that will be earned for doing the activity.
• Approval Type: Points for the activity can be awarded either immediately, automatically after X days or after manual verification. In the latter two options, the earned points transaction for the activity show up in an approval tab where you have the options to either approve or reject the transactions.
• Activity ID: This field cannot be edited for the in-built activities. For custom activities, this field acts as a reference in the API call. (See custom activity setup in this article for details).
• Show activity in User Dashboard: You can opt if you want to display this activity on the End-user dashboard or hide it.

Configuring the Business Rules

Zinrelo provides a sophisticated Rule Engine which allows you to define rules and exceptions for awarding points for each activity. The rules can be set up in the ‘Manage Rules’ sub-tab of each activity.

You can add multiple rules for each activity. When defining a rule you have to set the ‘Rule Type’ and then the conditions that make up rule.

Note: When any rules are not applied, the default points are awarded to the members. But, if you want to remove this default setting and do not want to award points to members if no rules are not applied, reach out to your account manager or write to us at [email protected].

Rule Type

The options available for the ‘Rule Type’ are -

1. Bonus Multiplier: The points earned are multiplied by the bonus multiplier if the conditions of the rule are satisfied.
2. Fixed Points: A fixed number of bonus points are awarded when the conditions are met.
3. Exclusion: No points are awarded when the conditions are met.
4. Frequency: This adds a frequency cap on the number of times a user can earn points for the activity. After the threshold is reached, further transactions are automatically rejected and no points will be awarded.

Rule Conditions

The conditions are based on rule attributes like ‘Transaction Date’ or ‘Order Value’. Only attributes that are relevant to an activity will show up in the rules section for that activity. You can add multiple conditions using the AND / OR operators.

In-built activities

These are activities which are built into the Zinrelo platform and don’t need any additional setup on your side. The in-built activities along with their unique configuration fields (if any) are described in this section.

Account Creation

Enable this activity to award points to customers for enrolling in the loyalty program. Unless you have configured your program for explicit opt-in, enrolling into the program is the same as creating an account on your site.

Purchase on Website

This is the primary activity for any loyalty program through which customers can earn points for their purchases. This activity does not have any additional configuration fields.

Birthday Bonus

With this activity, we can reward customers with bonus points on their birthday. The birthday information is collected in the Zinrelo loyalty dashboard. This activity does not have any additional configuration fields.

Refer-a-Friend

This activity awards points to referrers when their friends create an account with you and complete a purchase. Here is a video explaining how the activity works:

Unique Configuration Fields:

• Award Type: The referrer could be awarded a fixed number of points for the referral or the points awarded could be a percentage of the friend's purchase value.
• Friend Incentive Type: The referral campaign can award a generic coupon code for friends who click through the referral link. The other option is to not award any incentive.
• Facebook Settings: Set up the text of the default description of the Facebook post that will be seen by the customers’ friends.
• Twitter settings: Set up the text of the default tweet. Customers have the option to edit the default text before they Tweet.
• Email Settings: Customize the invitation email that goes out to the customers friends on behalf of the customer. The other email you can customize is the acknowledgement email sent to the customer after the customer has referrer friends.
• Landing Page pop-up: If the referral campaign is setup to award a generic coupon to friends, the coupon will be presented in a pop-up when the friends land on your website. This pop-up can be customized via HTML.
• The default referral link will have the Zinrelo domain in it. If you are on the enterprise plan, this link can be customized to your domain. You will need IT support to set it up.
  1. Create a sub-domain like refer.zinrelo.com.
  2. Create a CNAME setting in your DNS for your newly configured domain to app.zinrelo.com.
  3. Enter the complete URL with the sub domain in the 'Link Settings' of the activity configuration.

Contact Zinrelo support ([email protected]) to record this mapping in the Zinrelo system. Once done, the new referral link will start working.

Winback Bonus

This activity is targeted towards your inactive customers. The idea is to give the inactive customers an incentive to make a purchase soon. Here is a quick video explaining the Winback Bonus Activity:

Unique Configuration Fields:

• Inactivity Period: This is the number of months in which, if a customer has not made a purchase, the customer will be considered inactive.
• Winback offer validity: The winback activity awards points to the inactive customers if they purchase within the offer validity period. After this, they lose the opportunity to earn the points.

Share on Facebook This activity is created to encourage Facebook sharing. Points for this activity are not awarded when the customer shares on Facebook but when someone clicks on the shared FB post. This is done for two reasons – to confirm to FB sharing policy and to prevent abuse through shares visible only to the customer.

This activity does not have any additional configuration fields.

Share on Twitter

This activity is created to encourage Twitter sharing. Points for this activity are not awarded when the customer shares on Twitter but when someone clicks on the tweet.

This activity does not have any additional configuration fields.

Share on Pinterest

This activity is created to encourage Pinterest sharing. Points for this activity are not awarded when the customer shares on Facebook but when someone clicks on the shared FB post. This is done for two reasons – to confirm to Pinterest sharing policy and to prevent abuse through shares visible only to the customer.

This activity does not have any additional configuration fields.

Configuring a Custom Activity

A custom activity is one which doesn’t happen through the Zinrelo platform but you still wish to award points to customers for that activity. As long as you can track such activities at your end, Zinrelo can award points for it.

To set up a custom activity, select the 'Custom Activity' option from the Activities section. The configuration is similar to the other activities - set up the basic fields and then add the business rules.

To award points, you can either make a real time call using the Zinrelo API or upload an aggregated file to a FTP at the end of the day for batch processing.

To know about language customization, refer to this document.