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.
|Custom Data||check||All tables and fields|
|Data Blocking||check||All tables|
Follow our step-by-step Sailthru setup guide to connect Sailthru with your destination using Fivetran connectors.
This schema applies to all Sailthru connectors.
_fivetran_purchase_id is a calculated hash that is added as the primary key in
_fivetran_campaign_query_id is a calculated hash that is added as the primary key in
Sailthru does not provide email addresses in user report.
email_hash column in
user table contains MD5 hash values of email addresses.
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_query and tables based on it (tables whose names start with
campaign_), we fetch the last 18 months 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:
purchaseand tables based on it (tables whose names start with
userand tables based on it (tables whose names start with
For the following tables, we sync all historical data during both the initial sync and subsequent incremental syncs:
ad_planand tables based on it (tables whose names start with
templateand tables based on it (tables whose names start with
We support fetching older data on request.