Integrating loyalty provider data in Listrak allows data to sync between the provider and Listrak and save the data into profile fields. This data can be used to personalize message content or to determine when a contact should receive an automated message based on loyalty milestones. Listrak Conductor can be used to build these triggered automations and determine what and how many messages a contact should receive.
⚠️ This guide uses Annex Cloud loyalty data in the example. If you are using another loyalty provider, ensure your naming conventions and data reflect your available data.
About Loyalty Automations
Loyalty Automations can be set up for various milestones related to your loyalty program. When a contact meets these milestone they can then be entered into an automation.
Below are some common automations related to loyalty programs:
Welcome to Loyalty Program triggered by sign up
Loyalty Points Earned
Close to Next Loyalty Tier
Loyalty Tier Achieved
Loyalty Points Expiration
Birthday Loyalty Reward
💡 Loyalty Automations are created on the loyalty-specific list.
Entering Contacts into a Loyalty Automation
Contacts are eligible to enter a conversation when an external event tied to the trigger step is fired within the Listrak platform. There are three main ways a contact will enter into a loyalty automation.
An external event can be tied to a subscription point. This is the most common method for a loyalty welcome conversation.
An external event can be specified during a list import. This option is common when launching a loyalty program in Listrak to add existing members to your loyalty list.
An external event can be fired during an API call. This is most common for on-going updates from your loyalty partner. An API call can be made for any contact with a new purchase to update related loyalty data such as points accrued or redeemed.
⚠️ Custom functionality may require additional scoping and work.
Creating the External Events
External Events specify the event that allows a contact to enter a thread within the Conductor Conversation. External Events can be triggered by the methods described above.
Navigate to Automation > Conductor External Events.
Click New Event at the bottom of the page.
Enter a name in the popup that corresponds to the type of activity for the automation. These can be used to represent the specific configuration of your loyalty program such as program or tier name. E.g. LoyaltySignup-Account or BronzeLoyaltyTierEarned
Repeat steps 2 & 3 for any additional tiers, subscription points, or automations you are setting up related to your loyalty program.
If desired, create Groups to help keep your events organized.
Creating the Conversation
The Conductor Conversation controls the logic of your automation once a contact has entered a thread. This logic can send different messages based on different events, determine if a contact should stop receiving messages, and more. You will set up the logic below.
Before beginning, ensure you are on your loyalty list.
Navigate to Automation > Conductor Conversations.
Click New Conversation at the bottom of the page.
In the popup:
Enter the name of your Automated Campaign to reflect the specific goals.
Leave the template drop-down as Default.
Click Create Conversation.
Trigger Step Properties
The Trigger Step connects the external events created to the logic that will be set up into the next conversation.
Click on the Trigger Step (green triangle) in the designer tab.
At the top, give the step an easily identifiable name. This should reflect the type of action or specific configuration of your program. For example, you can have different triggers for each tier of your loyalty program.
Click on the plus sign next to the external event(s) that will be used for the campaign you are creating.
Click on additional plus signs next to external events, if needed. For example, in a Loyalty Welcome campaign you may have multiple external events, one for each way a contact can sign up for the loyalty program.
💡 Click the plus sign under the existing thread to add new trigger steps if needed.
Create Thread Logic
The thread logic is what determines how many messages are part of the automated series, how long a contact waits between messages, and more. Each conversation will have it's own logic based on it's type and based on the specifics of your loyalty program.
Tips for building Conductor Conversations
Use the plus sign to add new step types.
Consider applying a go-to step with a filter to remove contacts if they should no longer receive messages or be directed to a different message. E.g. Remove contacts who have made a purchase when offering a coupon.
Use a saved message option to import a message into Conductor that you have already render and link tested.
Action steps can be used to provide loyalty members with a coupon to incentivize purchase. These coupons can then be inserted in a message via profile fields.
Multiple threads can be used to send different messages based on loyalty tier, point value etc. Click on the green plus sign at the bottom of the conversation to add a new thread.
Learn more about the step types available in Listrak Conductor. Have questions? Reach out to your Account Manager or the Listrak Technical Support team.
Publishing the Conversation
Once you are satisfied with the conversation logic, the conversation can be published. Publishing a conversation enables contacts to enter the thread once an external event has been fired in the Listrak platform.
Click the Publish button in the designer tab.
In the popup, confirm that you wish to publish a conversation.
The conversation should be ready to accept contacts in a few minutes.
Entering Contacts into Conductor via API
Once a Conversation is published contacts are able to enter a thread tied to an external event. The most common way to enter loyalty members into a conversation is via Listrak's REST API.
First, ensure that you have created an Email REST API Integration within the Listrak platform.
Navigate to Help & Support > Help & Support API ID Information to find the IDs for the external events and any profile fields that should be referenced in the conversation.
Use the list import API call or the contact API call to determine the contacts who should enter a conversation. 💡 The fields, IDs, and events will be dependent on the specific goals of your campaign.