New feature
Beta
Salesforce Marketing Cloud connector
Salesforce Marketing Cloud connector is a Databricks data engineering capability, introduced June 2026.
The managed Lakeflow Connect connector that ingests Salesforce Marketing Cloud campaigns, journeys, email engagement events and data extensions into Databricks over Server-to-Server OAuth.
- A data extension must be named by its External Key (Customer Key) - use its friendly display name and the pipeline fails.
- When a data extension has no primary key, the connector invents one: __databricks_id, a hash of every column - which also rules out SCD type 2 for that table.
- For Salesforce data extensions the docs point you at the sibling Salesforce connector instead, because this one cannot ingest them incrementally.
Limitations: No SFTP export workflow and no direct data views (write them to a data extension first). Deletes to emails and campaigns need a full refresh. Each connection covers one business unit (and its children), so several business units need separate connections and API integration packages. Tables keyed by __databricks_id cannot use SCD type 2.
Open in REbricked →- Category
- Data engineering
- Also known as
- SFMC connector, Salesforce Marketing Cloud, Marketing Cloud connector
- Verified
- 2026-10-20
Sources
- Official Official Databricks / Microsoft docs
- Official Databricks release notes: Salesforce Marketing Cloud managed ingestion connector (Beta) (June 18, 2026)
- Official Databricks docs: Salesforce Marketing Cloud connector limitations
- Official Databricks docs: Salesforce Marketing Cloud connector concepts