Release Notes

September 2025

We no longer support historicSyncTimeFrame when creating connections using REST API configuration.

August 2025

We have changed the primary key of the following tables from message_id to event_id:

• ES_CAMPAIGN_SENDS
• ES_CAMPAIGN_OPENS
• ES_CAMPAIGN_CLICKS
• ES_CAMPAIGN_BOUNCES
• ES_CAMPAIGN_UNSUBSCRIBES
• ES_TRIGGERED_SENDS
• ES_TRIGGERED_OPENS
• ES_TRIGGERED_CLICKS
• ES_TRIGGERED_BOUNCES
• ES_TRIGGERED_UNSUBSCRIBES

The new primary key field, the event_id field, is present for records from March 20th, 2025, onwards. The existing records in these tables will be moved to backup tables whose names contain the suffix _backup.

March 2025

We have added a new field, Sync data from selected date, under the Historical Sync Time Frame dropdown in the setup form. This allows you to select the exact date up to which the backward sync will occur. The default value is Sync all historical data. You can edit the connection details and update the time frame for an existing connector.

This limit applies to the following tables:

• CAMPAIGN_QUERY
• PURCHASE
• PURCHASE_ITEM

We are gradually rolling out this feature to all connections.

October 2024

We have added two new columns, is_real_open, to the ES_CAMPAIGN_OPENS and ES_TRIGGERED_OPENS tables.

We have added a new column, is_real_click, to the ES_CAMPAIGN_CLICKS and ES_TRIGGERED_CLICKS tables.

We have added a new column, client_id, to the ES_FLOW table.

For more information, see the Sailthru Email Event Stream Data Sets documentation.

We have added a new field, Historical Sync Time Frame, to the connector setup form. This allows you to select how many months' worth of historical data you want to sync. The default value selected is ALL_TIME. For an existing connector, you can edit the connection details and set the time frame value. We have also added support for the historic_sync_time_frame field for connections created using the Create a connection endpoint. For more information, see our Sailthru documentation and REST API config.

The historical sync limit only applies to the following tables:

• CAMPAIGN_QUERY
• PURCHASE
• PURCHASE_ITEM

August 2024

We have added a new field, event_id, for the event stream tables. We have also updated the event_time field to enable millisecond precision for the event stream tables. For more information, see Event Stream Changes.

We will re-sync data from March 19, 2024, for all the event stream tables.

July 2024

You can now use your own S3 bucket to sync Sailthru Connect data. Previously, you had to use Fivetran's S3 bucket. To support this enhancement, we have added two new fields, S3 Bucket and Role ARN, to the setup form. We are gradually rolling out this improvement to all existing connections.

June 2024

We can now pack all the custom fields of the LIST_STAT and USER tables into a single JSON file and upsert it into a single column. We have added a new field, Pack Mode, to the connector setup form. The field provides you the option to choose how Fivetran should handle your custom fields. This feature is useful when the number of columns in a table exceeded 9,900 columns. If Unpacked Mode is selected and the number of columns of your table exceeds 9,900 then we will truncate the columns to 9,900. For more information, see our Sailthru connector documentation.

January 2023

We have added the following new columns to the CAMPAIGN table:

• email_hour_range
• end_date
• is_public

We have added the following new columns to the LIST_STAT table:

• active_count
• disengaged_count
• email_count
• emailable_count
• engaged_count
• lists_count
• lists_signup_count
• optout_count
• passive_count
• valid_count

We now sync custom fields to the LIST_STAT table.

We have added three new columns, ip, ip_type, and user_agent, to the following tables:

• ES_CAMPAIGN_CLICKS
• ES_CAMPAIGN_OPENS
• ES_TRIGGERED_CLICKS
• ES_TRIGGERED_OPENS

January 2022

Our Sailthru connector is now generally available.

Read our Sailthru connector documentation.

September 2021

The Sailthru connector now supports Sailthru Connect. You can now sync Event Stream data from your Sailthru account. For more information, see our setup instructions.

March 2021

The Sailthru connector now supports table blocking for all Sailthru tables. You can now choose which tables to sync and which to block from syncing to your destination. On your Connector Details page, go to the Schema tab and select or deselect the tables.

If you want to sync a child table, you must include the parent table in the sync.

September 2018

Fivetran now sets the _fivetran_deleted column value to true for deleted records in the USER and USER_LIST tables.