Update profiles in Listrak SMS¶
Listrak SMS is an automation platform for audience activation through mobile messaging campaigns and personalized SMS marketing.
Important
This destination only updates existing profiles in Listrak SMS. This connector does not create, delete, subscribe, or unsubscribe contacts. Use the Listrak SMS–List management destination to create, delete, subscribe or unsubscribe contacts.
Caution
Audience members sent to Listrak SMS from Amperity are automatically subscribed to a list and can receive SMS messages as the default behavior in Listrak SMS. Audience members who did not already exist in Listrak SMS are created and subscribed by default.
To avoid sending unsubscribed customers, apply filters to remove any customers who have unsubscribed from receiving SMS messages before sending audiences to Listrak SMS using campaigns, journeys, or orchestrations.
Amperity updates the contact attributes of SMS audiences in Listrak, including phone (required), email, first name, last name, birthdate, and postal code. Additional attributes may be sent when a matching custom segmentation field exists in Listrak SMS.
Talk with your Amperity representative about the Listrak SMS connector before configuring it in your tenant.
Use the Listrak SMS REST API to update SMS profile attributes for contacts that already exist in Listrak SMS.
Amperity uses the Start a Contact Update Import endpoint to update an audience member’s information by {phoneNumber}.
The steps that are required to send SMS profile updates to Listrak SMS from Amperity.
Caution
This destination is available for sending query results to Listrak SMS after it is configured by a Datagrid Operator or your Amperity representative.
If this destination cannot be selected for orchestrations ask your Datagrid Operator or Amperity representative to configure a destination for sending query results to Listrak SMS.
Build query¶
Listrak SMS uses phone numbers as the primary identifier for each SMS profile.
Listrak SMS has the following SMS pre-defined attributes to collect additional information about SMS profiles.
System fields
Birthday Use for date-based segmentation.
Email Address A contact attribute.
First Name and Last Name Use for personalization.
Postal Code Use for location targeting.
Use system attributes to personalize messages, such as adding a first name to an SMS message, and to filter messages to only those who match certain criteria.
Custom attributes
Custom attributes sent from Amperity must match custom attributes that already exist in Listrak SMS.
An SMS profile in Listrak SMS requires only a phone number, but may include all system profile attributes, including email address, first name, last name, postal code, and birthdate. Custom attributes may be included in the query results.
Important
Only phone numbers that already exist in Listrak SMS will be updated. Phone numbers that do not exist are silently dropped. Use the SMS Opt Status table to filter the results to include only customers who have opted in to receiving SMS messaging.
Replace spaces in custom SMS profile field names with underscores in the Amperity SQL query. For example, a custom SMS profile field is named “Loyalty Tier” in Listrak SMS. Alias the field name in the query using underscores:
current_tier AS Loyalty_Tier
Important
To avoid sending SMS messages to people who did not consent to receiving them, ensure only consented phone numbers are included in the data provided to Amperity, or maintain consent status as a separate attribute.
For example, bring Listrak subscriber status to Amperity as a data source, and then use that data source with the SMS Opt Status table to help ensure customers are filterable by subscriber status in queries and segments.
SMS opt-in requirements are different from email opt-in requirements and require separate consent tracking.
Example query
1WITH sms_opt_status AS (
2 SELECT
3 so.amperity_id
4 ,so.is_sms_opted_in
5 FROM SMS_Opt_Status so
6)
7
8SELECT
9 co.phone
10 ,co.email AS "Email Address"
11 ,co.given_name AS "First Name"
12 ,co.surname AS "Last Name"
13 ,co.postal AS "Postal Code"
14 ,co.birthdate AS "Birthday"
15 ,co.current_tier AS Loyalty_Tier
16FROM Customer_360 co
17JOIN sms_opt_status so ON co.amperity_id = so.amperity_id
18WHERE so.is_sms_opted_in = true
Listrak SMS has the following requirements for attributes.
Amperity attribute |
Listrak profile field |
|---|---|
phone |
Phone Required. The primary identifier for each SMS profile. |
Email Address A contact attribute. |
|
given_name |
First Name Use for personalization. |
surname |
Last Name Use for personalization. |
postal |
Postal Code Use for location targeting. |
birthdate |
Birthday Use for date-based segmentation. |
Custom attributes |
Custom profile fields Important Custom attributes must be configured as custom profile fields in Listrak before Amperity can send custom attributes with Listrak SMS profiles. The attribute name in Amperity must match the profile field name in Listrak SMS. Attribute names are not case-sensitive. All custom attributes sent by Amperity must match a custom profile field that exists in Listrak SMS. |
Important
Validate the audience with Listrak SMS by using a sample audience with a very small membership. For example: 10 or 100 members or the minimum audience size recommended by Listrak SMS. Send the sample audience to Listrak SMS and verify the sample audience is correct in Listrak SMS. Make adjustments if necessary. Only send full audiences after validation is complete.
Add orchestration¶
An orchestration defines the relationship between query results and a destination, including the destination and the frequency at which an orchestration runs.
To add an orchestration
Open the Activations page, select the Orchestrations tab, and then click the Add orchestration button. This opens the Add orchestration dialog box.
From the Object type dropdown, select Query.
From the Object dropdown, select the query for which results is sent to Listrak SMS.
From the Destination dropdown, select a destination that is configured for sending data to Listrak SMS.
Verify all settings.
Set the workflow to Manual. You can change this to automatic later, after verifying the end-to-end workflow.
Click Save.
Run orchestration¶
Run the orchestration manually to validate that it works.
To run the orchestration
Open the Activations page, select the Orchestrations tab, and then open the menu for the Listrak SMS orchestration. Select Run.
The Status column for the orchestration updates to say “Waiting to start”, after which the notifications pane updates to include a notification that shows the current status.
When the orchestration has run successfully, the status is updated to “Completed”.