The loyalty_tier_upgraded event is triggered at the moment a user has a tier upgrade. You can use it to create a triggered email that will be sent the moment the user has an upgrade. The event has the following parameters you can use inside the email, by using the following ESL code:

• Current Tier ID > {{event.current_tier.id}};
• Current Tier name > {{event.current_tier.name}};
• Current Tier icon > {{event.current_tier.icon}};
• Previous Tier ID > {{event.previous_tier.id}};
• Previous Tier name > {{event.previous_tier.name}};
• Previous Tier icon > {{event.previous_tier.icon}};

Check the Upgraded to higher tier tactic, to see this event in action.

The loyalty_tier_downgraded  event is triggered at the moment a user has a tier downgrade (From regular tiers, not from Invitation only to regular tier). You can use it to create a triggered email that will be sent the moment the user downgraded to a lower tier. The event has the following parameters you can use inside the email, by using the following ESL code:

• Current Tier ID > {{event.current_tier.id}};
• Current Tier name > {{event.current_tier.name}};
• Current Tier icon > {{event.current_tier.icon}};
• Previous Tier ID > {{event.previous_tier.id}};
• Previous Tier name > {{event.previous_tier.name}};
• Previous Tier icon > {{event.previous_tier.icon}};

The loyalty_tier_invitation_exit  event is triggered at the moment a user moved from an Invitation only tier to a regular tier. You can use it to create a triggered email that will be sent the moment the user leaves the Invitation only tier, to say you are sorry they left the tier and would like to see them again. The event has following parameters you can use inside the email:

• Current Tier ID > {{event.current_tier.id}};
• Current Tier name > {{event.current_tier.name}};
• Current Tier icon > {{event.current_tier.icon}};
• Previous Tier ID > {{event.previous_tier.id}};
• Previous Tier name > {{event.previous_tier.name}};
• Previous Tier icon > {{event.previous_tier.icon}};

The loyalty_points_redeemed event is triggered at the moment users redeem their points, for example, for a voucher. The event has only one parameter which you can use inside the email:

• Points > {{event.points}}
• Tier name > {{event.tier_name}}

The loyalty_voucher_redeemed event is triggered at the moment that the user redeems (uncovers) the voucher code in the Wallet or via API. You can use the event to send an email which will include the voucher code.
The event has the following parameters you can use inside an email, by using the following ESL codes:

• Voucher code > {{event.code}};
• Voucher name > {{event.name}};
• Tier name > {{event.tier_name}}

The loyalty_points_from_purchase_confirmed  event is triggered at the moment that the purchase points of Loyalty members are confirmed. You can use the event to create a triggered email that will update your members when their points are confirmed so they can check their balance, or you can send the details within the email. The event has following parameters you can use inside the email:

• # of points earned from this purchase > {{event.points}};
• Purchase OrderID > {{event.order_id}};
• Tier name > {{event.tier_name}}

The loyalty_purchase_referee_confirmed event is triggered the moment the referred friend made a purchase and the allocation period has passed. You can use the event to create a triggered email that will update your referrer that they have a reward waiting for them, because of the friend’s purchase. No parameters are available for this event.

This event is triggered the moment a user is signing for your loyalty program, either via Loyalty API or the Wallet. You could use it to trigger a “Welcome Tactic”. This trigger has no additional data that can be used via ESL in an email.

The external event loyalty_member_deleted_by_contact is triggered when the contact cancels his membership via the Wallet, the external event loyalty_member_deleted_by_customer is triggered when his membership is cancelled via the Member Profile. When the contact is deleted using the Loyalty API, it depends on the parameter sent in the API call which event is triggered: customer or contact. These events event have no payload.

The external event loyalty_cashback_redeemed is triggered when a member redeems a cashback voucher.

The loyalty_tier_calculation event is triggered at the moment a user has a tier calculation and stays in the same tier.  The event has the following parameters you can use inside the email, by using the following ESL code:

• Current Tier ID > {{event.current_tier.id}};
• Current Tier name > {{event.current_tier.name}};
• Current Tier icon > {{event.current_tier.icon}};
• Previous Tier ID > {{event.previous_tier.id}};
• Previous Tier name > {{event.previous_tier.name}};
• Previous Tier icon > {{event.previous_tier.icon}}

Use this trigger to notify members, that they achieved the necessary amount of points to stay in their current tier.

Loyalty Tactics use the External event transactional entry point in the Automation Center.

Here contacts can enter a program if they are returned by an API call containing the same external event (you must first create the API call before you can use this node).

• If you include external data in the external event API call, this external data will remain available for that contact throughout their journey through the program and can be used to personalize further emails.
• Programs that start with this entry point follow the ignore opt-in rules for transactional programs. If you create a program that starts with one of these entry points, the first email in the program will be sent to all participating contacts regardless of their opt-in status (i.e. opt-in can be empty or FALSE).
• External events may be used in as many active programs as you like.

You can create Automation Center programs that trigger Loyalty actions or assign rewards with this node.

Using the Loyalty Trigger node, you can build sophisticated automations with Emarsys in Interactions. You can quickly react to event related to your contacts engaging with your brand and involve them with Loyalty. For more information, see Channel nodes.