Go to the Destinations overview page and click the Add destination button. Select Sailthru and click Continue. You can then authenticate Hightouch to Sailthru.Enter the following fields into Hightouch:
Once you’ve set up your Sailthru destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Sailthru destination you want to sync to.
To match rows from your model to users in Sailthru, you need to select a model column and corresponding Sailthru field. The available matching fields depend on your sync mode:
Hightouch supports syncing users to a single list. You can input the name of your list on the sync configuration page. If the list doesn’t exist yet, Hightouch will create the list automatically in Sailthru.
Hightouch lets you sync user fields via field mapping.
You can map data from any of your model columns to default and custom user fields.
If you send data for a custom field that doesn’t exist, Hightouch adds the field.
Ensure your model’s columns have the same data types as the fields you want to sync to.
Upsert syncs send users to Sailthru in one of two ways. Choose the method in the sync’s Advanced settings under How should Hightouch send users to Sailthru?
Bulk (default) uploads users in bulk jobs. Use it for large audiences when list additions don’t need to start Lifecycle Optimizer flows.
Real-time sends each user with Sailthru’s User API. Use it when adding users to a list should start a Lifecycle Optimizer flow with a List Joined entry. Sailthru lists User API calls, not bulk jobs, among the ways a user joins a list for that entry.
Real-time syncs count against Sailthru’s rate limit for the User API, which defaults to 18,000 requests per minute per account. Other integrations that call the User API on the same account share that limit. Large audiences can take longer to sync in real time because each user is a separate request. Sailthru can raise the limit for your account on request.Update syncs always send each user with the User API, so this setting only appears for upsert syncs.
For upsert syncs set to Bulk, Hightouch sends users to Sailthru in batches. The default is 100,000 rows per batch. You can change this in the sync’s Advanced settings under Rows per batch.Lower the value if a sync runs out of memory on wide user records. Sailthru builds each batch in memory, so a smaller batch reduces peak memory use roughly in proportion.
You can match rows from your model to custom events in Sailthru on any column in your model and any field in Sailthru. Ensure the data types of the model column and Sailthru field you select match.
Refer to the record matching docs for more information.
You can match rows from your model to purchases in Sailthru on any column in your model and any field in Sailthru. Ensure the data types of the model column and Sailthru field you select match.
Refer to the record matching docs for more information.
You can match rows from your model to returns in Sailthru on any column in your model and any field in Sailthru. Ensure the data types of the model column and Sailthru field you select match.
Refer to the record matching docs for more information.
To see the exact API requests and responses from each sync run, use the live debugger. To get notified by Slack, PagerDuty, SMS, or email when a sync fails, set up sync alerts. If you run into an issue this page doesn’t cover, .
