November 2021link
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 2020link
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 2020link
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 |
---|---|
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 wish to continue storing timestamps using TIMESTAMP WITH TIME ZONE
, take no action.
November 2019link
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 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 2019link
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 2019link
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 2019link
- We have added the column
subscriber_key
to theSUBSCRIBER
table.
May 2019link
-
We have introduced a new column
triggered_send_id
to theACTIVITY
table. This field will also have a foreign key relation toTRIGGERED_SEND
table.-
We have moved the
tags
,definitionId
, andstatus
fields from theACTIVITY
table to theJOURNEY
table. -
We have renamed
object_id
in theTRIGGERED_SEND
toid
.
-
February 2019link
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 2019link
Fivetran now supports the s50
instance.
We have added the new column unsubscribed_date
to the SUBSCRIBER
table.
November 2018link
We have added a new field, version
, to the JOURNEY
table.
September 2018link
The Salesforce Marketing Cloud connector now supports the SentEvent endpoint.
August 2018link
Salesforce Marketing Cloud provides digital marketing automation, analytics, and lead management for B2B and B2C companies.