Configure destination for Listrak¶
Note
This topic contains information about configuring a destination that sends query results to Listrak using orchestrations. To configure a destination that sends audiences to Listrak using campaigns see this topic .
Listrak is an automation platform for email marketing. Use the Listrak Email API to manage audiences in Listrak.
Amperity can manage email lists in Listrak.
Amperity automatically adds a field attribute to all email lists that are sent to Listrak. This field is located inside a field group named “Amperity Message Attributes” within Listrak.
Note
Use SFTP to manage Customer lists , Product lists , Order lists , and Order item lists .
Work with your Listrak representatives to determine which of these sets will be useful for your workflows within Listrak, and then verify that attributes sent from Amperity are mapped correctly to the appropriate data schema within Listrak.
Get details¶
Review the following details before configuring credentials for Listrak and before configuring Amperity to send email lists to Listrak.
![]() |
Credential settings You must configure this destination for email or SMS: Email client ID and client secret
About Listrak allowlists
|
![]() |
Required configuration settings
|
![]() |
Audience configuration Use a query or a segment to build an audience to send to Listrak. The email or phone field must be part of the audience. You may append additional profile attributes to the query or segment. |
Customers, products, and orders¶
Configure Amperity to additional data sets—customers, products, orders, and order items—to Listrak using SFTP.
Note
This option uses the SFTP destination that is built into Amperity and should follow the steps and requirements that are outlined in the Listrak file import guide .
You can send the following sets of data to Listrak.
Work with your Listrak representatives to determine which of these sets will be useful for your workflows within Listrak, and then verify that attributes sent from Amperity are mapped correctly to the appropriate data schema within Listrak.
Configure credentials¶
Configure credentials for Listrak before adding a destination.
An individual with access to Listrak should use SnapPass to securely share “email client ID and secret” details with the individual who configures Amperity.
To configure credentials for Listrak
![]() |
From the Settings page, select the Credentials tab, and then click the Add credential button. |
![]() |
In the Credentials settings dialog box, do the following: From the Plugin dropdown, select Listrak. Assign the credential a name and description that ensures other users of Amperity can recognize when to use this destination. |
![]() |
The settings that are available for a credential vary by credential type. For the “listrak” credential type, configure settings, and then click Save. You must configure this destination for email or SMS: Email client ID and client secret
|
Add destination¶
Use a sandbox to configure a destination for Listrak. Before promoting your changes, send a test audience, and then verify the results in Listrak. After verifying the end-to-end workflow, push the destination from the sandbox to production.
To add a destination for Listrak
![]() |
Open the Destinations page, and then click the Add destination button. ![]() To configure a destination for Listrak, do one of the following:
|
![]() |
Select the credential for Listrak from the Credential dropdown, and then click Continue. Tip Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to Listrak. |
![]() |
In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination. Configure business user access By default a destination is available to all users who have permission to view personally identifiable information (PII). Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies. Enable the PII setting checkbox to allow limited access to PII for this destination. Use the Restrict PII access policy option to prevent users from viewing data marked as PII anywhere in Amperity and from sending data to downstream workflows. |
![]() |
Configure the following settings, and then click “Save”.
Audience primary key
Field group
Segment name (Required at orchestration)
|
![]() |
After configuring this destination users may use:
|