Skip to main content
Preview. The Salesforce Marketing connector isn’t generally available yet.

​
Connector Lifecycle

Deleting a source triggers an approval workflow based on your organization’s settings. Once approved, the source and all associated metadata are permanently deleted. The deletion cannot be undone after approval.
Existing metadata, quality scores, and alerts are retained while the connector is inactive. No new data is collected until the connector is re-enabled. If the connector is permanently deleted (after approval), all associated data is removed.

​
Salesforce Marketing-Specific

Enterprise 2.0 (multiple Business Units) and Corporate or Pro editions (a single Business Unit), for Marketing Cloud Engagement.
With OAuth 2.0 server-to-server credentials from an Installed Package. Legacy username and password SOAP authentication isn’t supported. The client secret can be entered directly or retrieved from a vault.
API uses the native REST and SOAP APIs, and listing multiple Business Units works only in API mode. JDBC is table-based. Check with your Prizm team before choosing, because the two modes differ in what they support.
Data Extensions have no last-modified timestamp. Prizm infers freshness from the last run of the Automation, Query Activity, or Journey that writes to the Data Extension, and shows Unknown when it finds none.
Six months, which is the retention of Marketing Cloud’s Data Views.
No. Each is a separate connector with its own setup.