Salesforce Marketing Cloud

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

Features

Feature Name	Supported	Notes
Capture deletes		`ACTIVITY`, `JOURNEY`, and all tables with `EXT`, `SF_EXT`, `SHARED_EXT`, `SHARED_SF_EXT`, or `SYNC_EXT` prefixes.
History mode		`CAMPAIGN`, `EMAIL`, `LIST`, and `LIST_SUBSCRIBER` tables.
Custom data
Data blocking		Column level
Column hashing
Re-sync		Connector level
API configurable		API configuration
Priority-first sync		`CHAT_INBOUND_MESSAGE_LOG`, `CHAT_POTENTIAL_UNSUBS`, `CHAT_TRACKING`, `EMAIL`, `EVENT`, `LIST`, `LIST_SUBSCRIBER`, `MOBILE_PUSH_DETAIL_EXTRACT`, `PUSH_MESSAGE`, `SEND`, `SMS_MESSAGE_TRACKING`, `SUBSCRIBER`, and `TRIGGERED_SEND` tables.
Fivetran data models		Get the transform model; Supports Quickstart data models
Private networking
Authorization via API

Setup guide

Follow our step-by-step Salesforce Marketing Cloud setup guide to connect Salesforce Marketing Cloud with your destination using Fivetran connectors.

Schema information

This schema applies to all Salesforce Marketing Cloud connectors.

To zoom, open the ERD in a new window.

Schema notes

We do not sync the LIST table if the EMAIL table is not selected.

We perform a daily re-sync of the SEND table if the EVENT table is not selected.

Data extensions

You can sync data extensions from your Salesforce Marketing account to your destination. We create a destination table for each data extension using our standard table naming conventions.

We support the following data extension types:

Standard data extension: These tables have the prefix EXT in your destination.
Shared data extension: These tables have the prefix SHARED_EXT in your destination.
Salesforce data extension: These tables have the prefix SF_EXT in your destination.
Shared Salesforce data extension: These tables have the prefix SHARED_SF_EXT in your destination.
Synchronized data extension: These tables have the prefix SYNC_EXT in your destination.

The Salesforce Marketing APIs do not provide a way to perform incremental syncs of data extensions. So, we perform daily full re-imports of each data extension table which may result in longer sync times. We recommend that you create a separate connector for these tables to avoid potential sync delays for other tables. All data extension tables are deselected by default in the Schema tab of the connector details page. You can select your required data extension tables in the Schema tab after your connector setup.

Limitations

We don't support history mode for certain destinations. For these destinations, we don't sync the following tables:

CAMPAIGN_TABLE
EMAIL_TABLE
LIST_TABLE
LIST_SUBSCRIBER_TABLE

Sync Notes

To sync the following tables using SFTP credentials, you must enable the following in Salesforce Marketing Cloud:

MobilePush to sync the MOBILE_PUSH_DETAIL_EXTRACT and PUSH_MESSAGE tables.
Mobile Connect and SMS Channel to sync the SMS_MESSAGE_TRACKING table.
WhatsApp to sync the following tables:
- CHAT_TRACKING
- CHAT_INBOUND_MESSAGE_LOG
- CHAT_POTENTIAL_UNSUBS

UTC conversion

By default, Salesforce Marketing Cloud uses Central Standard Time (CST), but we don't sync the time zone information for timestamps. We store the timestamps in LOCALDATETIME data type without the time zone information in your destination.

Limit historical data sync

In the setup form, you can set a limit on the historical data you want to sync during historical syncs and initial syncs. This limit applies to the following tables:

CHAT_MESSAGING_DETAIL_EXTRACT
EVENT
MOBILE_PUSH_DETAIL_EXTRACT
SMS_MESSAGE_TRACKING_DATA_VIEW

NOTE: The CHAT_MESSAGING_DETAIL_EXTRACT, MOBILE_PUSH_DETAIL_EXTRACT, and SMS_MESSAGE_TRACKING_DATA_VIEW tables are available in your schema only if you have selected the corresponding features in Salesforce Marketing Cloud.