> ## 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 — What We Collect

> Preview: the assets, signals, and lineage Prizm extracts from Salesforce Marketing Cloud.

> [!WARNING]
>
> **Preview.** This page describes the planned connector and may change before release.

## Catalog Metadata

| Marketing Cloud object | What Prizm stores |
| :- | :- |
| Data Extension | Table asset, with its description and whether it's sendable |
| Data Extension field | Column with type, primary key, required flag, and description |
| Query Activity | Derived asset with its SQL text, target Data Extension, and update type. It's the main source of lineage |
| Automation | Pipeline asset with name, key, status, steps, schedule, and last run |
| Journey and entry Event Definition | Pipeline asset and lineage source |
| List and folders | List asset, with its folder placement kept |
| Content Builder email | Content asset |
| Standard Reports | Report asset with its category and schedule |
| Journey Analytics Dashboard and Intelligence Reports | Dashboard asset |

Marketing Cloud has no generic free-form tagging, so folder placement is the nearest equivalent.

## Observability and Quality

| Signal | How Prizm measures it |
| :- | :- |
| Freshness | Inferred from the last run of the Automation, Query Activity, or Journey that writes to the Data Extension. **Unknown** if none is found |
| Volume | Row counts |
| Schema | Added, removed, or type-changed fields between runs |

**Automatic rules.** Prizm creates a not-null rule for required fields and a uniqueness rule for primary-key fields, suggests an email-format rule for email-type fields, and checks that Journey entry subscriber keys exist in All Subscribers. You can edit or disable any of them. Failing records are written to an Iceberg table, linked to the rule execution.

**Criticality.** Each Data Extension is scored from freshness, dependencies, volume, metadata and sensitivity, usage, key attributes, and structure. Data with no linked sends, automations, or journeys gets a neutral usage score.

## Lineage

* Data Extension to Journey (entry source)
* Data Extension to Query Activity to Data Extension, from SQL text parsing of standard single-statement queries
* Automation activity chains (for example import, query, extract, send)
* Data Extension or List through a send definition to an email asset

Impact (downstream) lineage is supported.

## Usage

Send, open, click, bounce, complaint, and unsubscribe history from Marketing Cloud Data Views (rolling 6-month retention), plus Automation run history and Journey entry, exit, and goal counts. Prizm captures it daily and uses it for criticality and popularity ranking. Automation Studio notifications are ingested and labeled by source.

## What Prizm Does Not Collect

Cost data, Advertising Studio, Interaction Studio and Personalization, Einstein scores and predictions, and Marketing Cloud Connect-synced Sales and Service objects.

## Next Steps

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

> **[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.