Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Listrak Source


Source Info
  • The Listrak Source is an Event Cloud source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
(warning)

This Source is supported in US data processing regions.

This Source is only supported in workspaces configured to process data in the US region. Workspaces configured with data processing regions outside of the US cannot connect to this source. For more information, see Regional Segment.

Listrak(link takes you to an external page) is the retail industry's leading customer engagement platform. Listrak delivers results for more than 1,000 retailers by providing best-in-class email, text message marketing, identity resolution marketing and push notifications through seamless cross-channel orchestration. Listrak's data-first approach delivers 1:1 personalization at scale so you can send messages at precisely the right time across the right combination of channels and devices to maximize customer engagement, revenue, and lifetime value.

This is an Event Cloud Source which can not only export data into your Segment warehouse, but can also federate the exported data into your other enabled Segment Destinations.

This source is maintained by Listrak. For any issues with the source, contact their Support team.


Getting started

getting-started page anchor
  1. From your workspace's Sources catalog page(link takes you to an external page), click Add Source.
  2. Search for "Listrak" in the Sources Catalog, select Listrak, and click Add Source.
  3. On the next screen, give the source a nickname and configure any other settings. The nickname is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The nickname can be anything, but we recommend using something that reflects the source itself and distinguishes amongst your environments (for example, Listrak_Prod, Listrak_Staging, Listrak_Dev).
  4. Click Add Source to save your settings.
  5. Copy the Write key from the Segment UI.
  6. If using Unify and Engage Audiences:
    1. Go to Unify > Unify settings > Profile sources.
    2. Click Connect source.
    3. Select the new Listrak source.
    4. Click Connect source.
  7. Log in to your Listrak account(link takes you to an external page), and navigate to Integrations > Integrations Management.
  8. Click New Integration.
  9. Click the Segment card.
  10. Click Setup Integration.
  11. Paste the Write key you copied from Segment and click Save.
  12. Add at least one email list that you want to sync with Segment and click Save.

Listrak uses Segment's stream Source component to send Segment event data. It uses the server-side Identify and Track methods to send data to Segment. These events are then available in any destination that accepts server-side events, and available in a schema in your data warehouse, so you can query using SQL.

Listrak sets the anonymousId and the email trait to the email address of the contact.

If you entered a profile field when the email list was added to the integration and the email address has a value for that profile field, the userId is set to that value when you send identify events. Otherwise, Listrak won't send the userId. The userId won't be set for any track events. Listrak maintains a trait for each email list you add to the integration using identify events. The trait is named listrak_list_{listId}, where {listId} is the ID of the list (eg. listrak_list_12345). The trait will be set to true if the email address is subscribed to the list. The trait will be removed if the email address is not subscribed to the list. This trait can be used to create Engage audiences that only contain profiles that are subscribed to a Listrak list.


The following table lists events that Listrak sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations.

Event nameDescription
Email BouncedThe email servers rejected the email.
Email ConvertedThe recipient placed an order after clicking on the email.
Email Link ClickedThe recipient clicked on a link in the email's body.
Email Marked As SpamThe recipient marked an email as spam.
Email OpenedThe recipient opened the email.
Email SentAn email was sent to the recipient.
UnsubscribedThe recipient unsubscribed from the email list.

The following table lists the properties included in the events.

Property nameDescription
email_idAn ID used to identify the email.
email_subjectThe email's subject line.
campaign_nameA name used to identify a Listrak campaign.
link_idAn ID used to identify a link.
link_urlThe URL the link points to.
google_analytics_campaign_nameA name used to identify a Google Analytics campaign.
list_idAn ID used to identify a list.
list_nameA name used to identify a list.
order_totalThe order total associated with the conversion.
unsubscribe_typeThe method by which the contact was removed from the list. See the Unsubscribed Contacts Report Help Article(link takes you to an external page).
context.ipThe opening computer's public IP address.
context.traits.emailThe intended recipient's email address.
context.user_agentThe opening browser's user agent.

Now that your source is set up, you can connect it to destinations.

Log in to your downstream tools and check to see that your events appear as expected and that they contain all of the properties you expect. If your events and properties don't appear, check the Event Delivery tool and refer to the docs for each destination.

If there are any issues with how the events are arriving to Segment, contact the Listrak support team.