> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Salesforce Marketing Overview

> Preview: what the Salesforce Marketing Cloud connector covers and what Prizm collects.

> [!WARNING]
>
> **Preview.** The Salesforce Marketing connector is still in progress and isn't generally available yet. Field names and behavior may change before release.

Prizm connects to Salesforce Marketing Cloud Engagement to catalog your Data Extensions, Lists, Automations, Query Activities, Journeys, and Content Builder emails, monitor data quality, and trace lineage between them. It's a separate connector from Salesforce Sales Cloud and Salesforce Data Cloud.

## Why Connect Salesforce Marketing to Prizm?

**Catalog & Context** Prizm discovers Data Extensions and their fields, Lists, Automations, Query Activities, Journeys and their entry event definitions, Content Builder emails, standard Reports, and dashboards.

**Data Quality** Quality measures run on Data Extension fields. Prizm creates rules automatically from required and primary-key fields and suggests an email-format rule for email fields. You can edit or disable any of them.

**Observability** Prizm tracks row counts and detects added, removed, and type-changed fields between runs. Data Extensions have no last-modified timestamp, so freshness is inferred from the last run of the Automation, Query Activity, or Journey that writes to them.

**Lineage** Marketing Cloud has no native dependency view, so Prizm derives lineage: Data Extension to Journey, Data Extension to Query Activity to Data Extension, Automation activity chains, and Data Extension or List through a send definition to an email.

**Usage** Send, open, click, bounce, complaint, and unsubscribe history, plus Automation run history and Journey entry, exit, and goal counts, feed criticality and popularity.

## Supported Editions

Marketing Cloud Engagement on Enterprise 2.0 (multiple Business Units), and on Corporate or Pro editions (a single Business Unit). The connector uses the Marketing Cloud REST and SOAP APIs with OAuth 2.0 Installed Packages. Legacy username and password SOAP authentication isn't supported.

## Current Scope

* Every run re-extracts all selected objects. Incremental mode isn't supported.
* Assets are existing tables and objects. Custom SQL-defined assets aren't supported.
* Engagement history is limited to Marketing Cloud's rolling 6-month Data Views.
* Freshness is a proxy, and lineage from Query Activities relies on parsing the SQL text, so complex multi-statement queries aren't guaranteed.
* Advertising Studio, Interaction Studio, Einstein scores, Marketing Cloud Connect-synced Sales and Service objects, and cost data aren't covered.

## Next Steps

> **[Setup](/sources/salesforce-marketing/setup.md)**
>
> Create the Installed Package and connect Marketing Cloud.

> **[What We Collect](/sources/salesforce-marketing/what-we-collect.md)**
>
> The assets, signals, and lineage Prizm extracts.

> **[FAQ](/sources/salesforce-marketing/faq.md)**
>
> Common questions about the Salesforce Marketing connector.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.