Customize Email Body Content for Specific Rewards

This article helps you with some customization in your notifications.

📘

Note

This section may require HTML development expertise.

If you do not like the card view for rewards in the default Zinrelo email notifications, you can design your own HTML using the custom HTML tags listed below -

  • allrewards- Tag to iterate over all the rewards and replicate the HTML inside the tag for each reward

E.g

<allrewards>

<! -- Your HTML code goes here -->

</allrewards>

The HTML code written inside this tag will be replicated for each reward

  • tierrewards- Tag to iterate over all the tiers rewards and populate the HTML inside

E.g

<tierrewards>

<! -- Your HTML code goes here -->

</tierrewards>

The HTML code written inside the tag will be replicated for each reward available on the tier the user is on.

Here is a sample HTML that uses the < allrewards > tag:

Customize Email Body

ifcondition- Tag to check a condition and populate the HTML inside only if the condition is satisfied.

Note: In ifcondition, the preview email will not work. To test the actual flow of the email, you can go to the website and redeem the reward.

E.g

<ifcondition check-**param-condition**=value>

<! -- Your HTML code goes here -->

</ifcondition>

Where param can take one of the following values - reward_id, reward_name, reward_description, reward_points, user_tier, user_available_points

And condition can take one of the following values - equals, notequals, greaterthan, greaterthanequal, lessthan, lessthanequal

For e.g

<ifcondition check-**reward_points**-lessthan=500>

<! -- Your HTML code goes here -->

</ifcondition>

The HTML code inside the above mentioned tags can contain the following dynamic variables-

  • reward_id- Populates the reward id (works with equals and notequals)
  • reward_name- Populates the reward name (works with equals and notequals)
  • reward_description- Populates the reward description (works with equals and notequals)
  • reward_points- Populates the reward points required (works with all the conditions)
  • user_tier- Populates the user’s tier (works with equals and notequals and should be compared with tier_id)
  • user_available_points- Populates the user’s available points (works with all the conditions)