Source connector

Salesforce Marketing Cloud connector

Salesforce Marketing Cloud integration for databases, warehouses and BI tools

Enterprise email, journeys, and cross-channel messaging. Datrise captures Salesforce Marketing Cloud entities such as subscribers, data extensions, journeys, sends, email events and lists, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Salesforce Marketing Cloud Engagement REST API + SOAP API, Data Extensions authenticates with OAuth 2.0, incremental runs key on _CustomObjectKey system field's modified date column, or an authored DateModified/LastUpdated column on the data extension queried via $filter.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `salesforce_marketing_cloud_subscribers`) with a schema derived from the Salesforce Marketing Cloud API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Salesforce Marketing Cloud pipeline page, and join the waitlist to get the Salesforce Marketing Cloud connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Salesforce Marketing Cloud data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
subscribers	salesforce_marketing_cloud_subscribers	Upsert by primary key, incremental on updated-at
data extensions	salesforce_marketing_cloud_data_extensions	Upsert by primary key, incremental on updated-at
journeys	salesforce_marketing_cloud_journeys	Upsert by primary key, incremental on updated-at
sends	salesforce_marketing_cloud_sends	Upsert by primary key, incremental on updated-at
email events	salesforce_marketing_cloud_email_events	Append-only, incremental by timestamp
lists	salesforce_marketing_cloud_lists	Upsert by primary key, incremental on updated-at

Salesforce Marketing Cloud API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Salesforce Marketing Cloud Engagement REST API + SOAP API, Data Extensions
Authentication	OAuth 2.0 — Server-to-server OAuth2 client credentials grant from an Installed Package, scoped with REST/SOAP permission IDs per business unit.
Pagination	page — Data Extension row endpoints use $page and $pageSize query parameters; filtering, sorting, and paging are only supported on sendable data extensions.
Rate limit	Not published
Incremental cursor	_CustomObjectKey system field's modified date column, or an authored DateModified/LastUpdated column on the data extension queried via $filter — Data Extensions have no vendor-mandated modified-date column; incremental sync depends on whatever date field the business unit's data extension schema actually includes.
Webhooks	Yes — Event Notification Service (registered HTTPS callback subscriptions)
Bulk export	Yes — Data Extension Rows (Asynchronous) API
Deletes detectable	No

Official API reference

What bites when replicating Salesforce Marketing Cloud

Marketing Cloud publishes no fixed numeric rate limit for the REST or SOAP APIs; instead it reactively throttles an account with HTTP 500 'Rate Limited' faults once calls are judged to be impacting system performance, per the rate-limiting guide.
$page/$pageSize filtering, sorting, and paging on Data Extension rows only work on sendable data extensions — non-sendable data extensions fall back to unfiltered, unsorted result sets.
The Event Notification Service requires your callback endpoint to respond with HTTP 200 within 30 seconds of the verification POST, or the subscription registration fails outright.
Data Extensions carry no built-in soft-delete or IsDeleted flag; a row removed from the extension simply disappears from subsequent reads with no audit trail unless the business unit's own schema logs it.

Compare this against every other documented API

Popular destinations for Salesforce Marketing Cloud

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Salesforce Marketing Cloud connector FAQ

What Salesforce Marketing Cloud data does the connector extract?: 6 objects: subscribers, data extensions, journeys, sends, email events and lists. Each lands in its own table with types preserved; history-style objects (1: email events) load as append-only streams.
Is the Salesforce Marketing Cloud integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Salesforce Marketing Cloud data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Salesforce Marketing Cloud → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Salesforce Marketing Cloud pipeline with guided onboarding

Join the waitlist to get priority access for Salesforce Marketing Cloud integrations with guided setup, schema-aware mapping, and production-grade incremental sync.