Sailthru link
Sailthru provides services for email management. Sailthru services include scheduling and sending campaigns and transactional emails to each user's interest. Campaigns are email messages scheduled for group of users based on a specific template. It can contain news update or promotional messages. Transactional emails are sent to a particular user in response to a specific action.
Featureslink
Feature Name | Supported | Notes |
---|---|---|
Capture deletes | ||
Custom data | check | All tables and fields |
Data blocking | check | Column level and all tables |
Column hashing | check | |
Re-sync | check | Connector level |
History | ||
API configurable | check | API configuration |
Priority-first sync | ||
Fivetran data models | ||
Private networking |
Setup guidelink
Follow our step-by-step Sailthru setup guide to connect Sailthru with your destination using Fivetran connectors.
Schema informationlink
This schema applies to all Sailthru connectors.
To zoom, open the ERD in a new window.Schema noteslink
_fivetran_purchase_id
is a calculated hash that is added as the primary key in purchase
and purchase_item
table.
_fivetran_campaign_query_id
is a calculated hash that is added as the primary key in campaign_query
and campaign_click
table.
Sailthru does not provide email addresses in user report. email_hash
column in user
table contains MD5 hash values of email addresses.
Sync strategylink
We fetch data from the Sailthru API. If you opt to sync Sailthru Connect, we fetch Event Stream data.
We cannot query most of the Sailthru API endpoints using date ranges. Consequently, we need to fetch all historical data during incremental syncs. We can then discard the older data that we already have synced to the destination.
As an exception, the campaign
endpoint allows us to use time ranges in our API calls. We can therefore incrementally sync the campaign
table that uses this endpoint. For campaign
, we fetch all historical data during the initial sync and sync incrementally during the subsequent syncs. We do not need to discard the older records in campaign
.
For campaign_query
and tables based on it (tables whose names start with campaign_
), we fetch the last 18 months' worth of data during the initial sync. During the subsequent incremental syncs, we still fetch the last 18 months' worth of data and discard records older than 60 days.
For the following tables, we sync 30 days' worth of data during both the initial sync and subsequent incremental syncs:
purchase
and tables based on it (tables whose names start withpurchase_
)user
and tables based on it (tables whose names start withuser_
). We sync these tables based on thesend_time
parameter value returned by the corresponding list endpoint. We retrieve the data for a list only if it has a validsend_time
value and if this value is within the last 30 days.
For the following tables, we sync all historical data during both the initial sync and subsequent incremental syncs:
ad_plan
and tables based on it (tables whose names start withad_plan_
)template
and tables based on it (tables whose names start withtemplate_
)list
We support fetching older data on request.