Release Notes

September 2024

We now sync the triggered_send_key field to the ACTIVITY table.

July 2024

We have added a new table, SMS_MESSAGE_TRACKING to sync data from the SMSMessageTracking data view.

We have added the following new tables to support MobilePush:

MOBILE_PUSH_DETAIL_EXTRACT
PUSH_MESSAGE
PUSH_APPLICATION

We have added the following new tables to support Chat Messaging Data Extract:

CHAT_TRACKING
CHAT_INBOUND_MESSAGE_LOG
CHAT_POTENTIAL_UNSUBS
OTT_REGISTRATION

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 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 connectors created using the Create a Connector endpoint. For more information, see our REST API config.

The historical sync limit only applies to the following tables:

CHAT_MESSAGING_DETAIL_EXTRACT
EVENT
MOBILE_PUSH_DETAIL_EXTRACT
SMS_MESSAGE_TRACKING_DATA_VIEW

April 2024

We have added support for syncing Data Extensions from your Salesforce Marketing Account. We create a destination table for each data extension table. We are gradually rolling out this change to all our existing connectors.

February 2024

We have added new Quickstart packages for the following connectors:

We have added the following columns to the JOURNEY table and assigned version column as the primary key for the table:

category_id
channel
created_date
definition_type
entry_mode
execution_mode
exits
last_published_date
meta_data
modified_date
notifiers
scheduled_status
stats
version

We have added the following columns to the ACTIVITY table and assigned journey_version column as the primary key for the table:

description
journey_version
meta_data
schema

January 2024

We have released a pre-built, dbt Core-compatible data model for Salesforce Marketing Cloud. Find the model in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation*.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

We have added the option to select the event types that you want to sync. In the connector setup form, you can now select the event types in the Select Event Type(s) drop-down menu.

November 2023

We have converted the following tables to history tables and migrated the existing data in these tables to history mode:

EMAIL
LIST
LIST_SUBSCRIBER

We have added two new tables, CAMPAIGN and CAMPAIGN_ASSET.

We are gradually rolling out these changes to all existing connectors.

October 2023

We have made the following schema changes to address the data redistribution and data integrity issues caused due to the incorrect selection of the primary key:

Moved the alias, total_clicks, and unique_clicks columns from the LINK to the LINK_SEND table.
Changed the primary key from a combination of send_id and link_id columns to the id column, in the LINK_SEND table.

April 2023

We have changed the primary key of the LIST_SUBSCRIBER table and performed a table re-sync to ensure data integrity. The new composite key is a combination of the id and list_id columns.

August 2022

We have decreased the priority fetch period from 14 to 5 days for all the priority-first sync tables to improve sync speeds and reduce the duration of the first forward sync. For more information, see our priority-first sync documentation.

We have decreased the priority fetch period from 5 days to 1 day for all the priority-first sync tables to improve sync speeds and reduce the duration of the first forward sync. For more information, see our priority-first sync documentation.

June 2022

We now support syncing HTML-based emails.

November 2021

We have added the event_type field as a primary key in the EVENT table. We don't recommend a re-sync because this change resolves a rare discrepancy that may not have affected you and because the EVENT table can take a long time to sync. If you do notice data discrepancies in the EVENT table and must re-sync it, contact Fivetran Support.

March 2020

We have implemented a new sync schedule to fetch data from the SUBSCRIBERS table. Every Saturday, the connector performs a historical sync. The additional Saturday sync improves the connector's overall sync speed.

January 2020

We now store timestamp data using the TIMESTAMP WITHOUT TIME ZONE type. Previously we used TIMESTAMP WITH TIME ZONE and when Fivetran received timestamp data that did not have timezone information from Salesforce Marketing Cloud, we incorrectly stored the timestamp data as UTC. Using TIMESTAMP WITHOUT TIME ZONE fixes this issue.

The following table lists the columns whose type we have converted from TIMESTAMP WITH TIME ZONE to TIMESTAMP WITHOUT TIME ZONE:

Table Name	Modified Columns
EMAIL	created_date, modified_date
EVENT	created_date, event_date, modified_date
JOURNEY	created_date, modified_date
LINK	last_clicked
LIST	created_date, modified_date
LIST_SUBSCRIBER	created_date, modified_date
SEND	created_date, modified_date, send_date
SUBSCRIBER	created_date, unsubscribed_date
TRIGGERED_SEND	created_date, modified_date

Newly created connectors will use TIMESTAMP WITHOUT TIME ZONE in these columns by default. To update existing connectors to use TIMESTAMP WITHOUT TIME ZONE, drop your existing tables and trigger a re-sync. If you want to continue storing timestamps using TIMESTAMP WITH TIME ZONE, take no action.

November 2019

The Salesforce Marketing Cloud connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Salesforce Marketing Cloud's priority-first syncs fetch the most recent 14 days' worth of data from the following tables:

EVENT
SUBSCRIBER
TRIGGERED_SEND
SEND
EMAIL
LIST_SUBSCRIBER
LIST

To learn more, see our priority-first sync documentation.

October 2019

We have started syncing email data from the Content Builder API into the EMAIL table. This lets us fetch data that is not available through the SOAP API. This change adds the new column asset_type_id to the EMAIL table.

September 2019

We have added support to authenticate Salesforce Marketing Cloud connectors using OAuth 2.0. Salesforce Marketing Cloud creates new packages with OAuth 2.0 as the only authentication option. Thus, all connectors that use these new packages must use OAuth 2.0 to authenticate with Fivetran.

When you create a new connector, you must now enter your subdomain in the setup form. You must also select New Enhanced Package to indicate that your package uses OAuth 2.0.

August 2019

We have added a new column, subscriber_key, to the SUBSCRIBER table.

May 2019

We have added a new column, triggered_send_id, to the ACTIVITY table. This column will also have a foreign key relation to TRIGGERED_SEND table.

We have moved the tags, definitionId, and status columns from the ACTIVITY table to the JOURNEY table.

We have renamed object_id column in the TRIGGERED_SEND table to id.

February 2019

We dropped the following fields from the TRIGGERED_SEND table:

cc_email
interaction_id
is_always_on
is_send_logging
pre_header
replyto_address
replyto_display_name
send_window_delete

January 2019

Fivetran now supports the s50 instance.

We have added a new column, unsubscribed_date, to the SUBSCRIBER table.

November 2018

We have added a new column, version, to the JOURNEY table.

September 2018

The Salesforce Marketing Cloud connector now supports the SentEvent endpoint.

August 2018

Salesforce Marketing Cloud provides digital marketing automation, analytics, and lead management for B2B and B2C companies.

Read our Salesforce Marketing Cloud connector documentation.