Segment is a customer data platform (CDP) that enables you to collect, transform, send, and archive your first-party customer data. Segment simplifies the process of collecting data and hooking up new tools, allowing you to spend more time using your data, and less time trying to collect it.
The Sailthru Segment Destination allows organizations using Segment to easily pass crucial marketing data points from your Segment account into Sailthru user profiles with just a few clicks.
Out-of-the-box features include:
- 1:1 profiles for identified Segment users
- Pageviews, Sessions, and Interest Gathering
- Automation entry points from any Segment event
- Specialty automation triggers for Abandoned Cart & Abandoned Browse
- Purchase-driven automation, segmentation, and personalization
To install the Sailthru Segment destination, visit this link which will take you to the integration’s listing in the Segment marketplace.
Once installed, you can set up your API Key, Secret, and whether you’d like to track pageviews automatically to Sailthru from Segment.
Note: Ask Sailthru support to enable your account for EXTID support. This will be used to store Segment userId values on Sailthru profiles.
When you call Segment’s identify() function, Sailthru will automatically create or update a profile for any user with a valid user ID.
Email and User ID will be automatically mapped to Sailthru profile keys, with all other identify properties appearing in user profile custom fields.
Adding to Lists
To add users to lists, you can create a Subscribed Segment event with a list property. This will add the user to the natural list and mark the user as opted in
Alternatively, use Lifecycle Optimizer to create your own signup flow from any Segment event.
Purchases & Carts
For eCommerce data, Sailthru requires a url property for each line item.
If email is not supplied in your Segment Order Completed event, we will make our best effort to correlate preexisting Sailthru profile data. In the unlikely event no email can be found after multiple correlation attempts, the purchase event will be marked with an error in Segment. This will allow you to replay the event once the user’s email has been established.
On the order level, we’ll capture tax, shipping, and discount automatically as adjustments. To make sure all orders enter Sailthru exactly once, the integration will use order_id, checkout_id, or Segment’s message_id as a unique key for the order.
For line items, URL, title, quantity, price, and tags will all map to Sailthru’s content fields, with all other fields appearing as item custom fields. If the item is not already in your Sailthru Content Library, it will automatically be created from the purchase details.
All non-standard Sailthru fields will be available in order-level and item-level custom fields, all accessible in Audience Builder and Lifecycle Optimizer entries.
Sailthru Campaign Attribution
The Sailthru Segment Integration can automatically attribute purchases to your Sailthru campaigns and LO flows by adding a new query parameter st_bid to your clickthroughs. These can be automatically enabled in MY at https://my.sailthru.com/settings/email.
Track Pageviews, Sessions, and Interest Data
The Sailthru Destination for Segment consumes all Segment pageviews. By default, pageview tracking relies on interest tags in your Content Library but those can be overridden by passing a tags array in your Segment page() request properties.
The Sailthru Destination for Segment can also automatically generate connected onsite sessions from your Segment pageview stream, allowing you to use Lifecycle Optimizer’s Browse Abandoned and Cart Abandoned entries.
If for any reason you wish to not track Segment pageviews in Sailthru, you can disable this via a toggle in your Segment Destination settings.
Start Lifecycle Optimizer Flows from Segment Events
All other events recorded with Segment’s track() API are able to kick off Lifecycle Optimizer flows via the Custom Event (API) entry. Any data passed in a Segment event’s properties will be available for entry filters, checks, and accessible in-template.