Skip to main content
Salesforce Marketing Cloud is a comprehensive digital marketing platform that enables businesses to create, manage, and optimize personalized customer experiences across email, mobile, social media, and web channels. It provides tools for email marketing, automation, analytics, and customer journey management.

​
Configuring Salesforce Marketing Cloud as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Salesforce Marketing Cloud option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need your Salesforce Marketing Cloud credentials for this connection. You can find these in your Salesforce Marketing Cloud account settings. The following configurations are available:
  • Subdomain: Your Salesforce Marketing Cloud subdomain (e.g., if your URL is https://mc123456789.auth.marketingcloudapis.com, your subdomain is mc123456789). You can find this value in the Installed Packages section of Marketing Cloud Engagement Setup.
  • Client ID: The client ID from your Salesforce Marketing Cloud app integration. You can find the client ID in Marketing Cloud Setup > Apps > Installed Packages > .
  • Client Secret: The client secret from your Salesforce Marketing Cloud app integration.
  • Account ID: Your Salesforce Marketing Cloud account ID.
  • Search: A search parameter to filter data extensions. This helps you focus on specific data extensions that you want to extract data from (e.g., “Newsletter”, “Customer”, etc.).
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

Below you’ll find all available data streams from Salesforce Marketing Cloud and their corresponding fields:
Stream for managing data extension metadata and configuration information.Key Fields:Data Retention Properties:
Dynamic streams for each data extension containing the actual subscriber and customer data. Each data extension creates its own stream. Stream names are dynamically generated using the native name of the data extension (sanitized and transliterated to ASCII) plus a short ID suffix to guarantee uniqueness (e.g., data_extensions_newsletter_subscribers_1234abcd).Key Fields:Notes on Primary Keys: Primary keys for these streams are dynamically derived from the data extension’s field metadata (specifically using fields flagged as IsPrimaryKey). If a data extension has no fields flagged as a primary key (e.g., event/log DEs), no primary key is emitted, which will result in a full-table load for that extension.Field Types Supported:The connector maps native Salesforce Marketing Cloud field types to the following standard types. Note that any unknown or unsupported field types from Salesforce Marketing Cloud will automatically default to String.
The exact fields available depend on the specific data extension’s schema. Each data extension matching your search criteria will create a separate stream with its own field structure.

​
Data Model

The following diagram illustrates the relationships between the core data streams in Salesforce Marketing Cloud. The arrows indicate the join keys that conceptually link the different entities, providing a clear overview of the data structure. Key Relationships:
  • Data Extensions contains metadata about each data extension
  • Data Extensions by ID streams contain the actual data for each extension
  • Each data extension can be linked to others through common keys
  • The subscriberkey (or the specific primary key defined in the extension’s metadata) serves as the primary identifier across data extensions

​
Implementation Notes

  • Stream Naming Configuration: When replicating multiple data extensions, the connector translates accented characters to ASCII and replaces special characters with underscores to produce clean and readable tables in your destination catalog. An 8-character snippet of the ObjectID is appended to avoid naming collisions.
If you encounter any issues, reach out to us via Slack, and we’ll gladly assist you!

​
Skills for agents

Download Salesforce Marketing Cloud skills file

Salesforce Marketing Cloud connector documentation as plain markdown, for use in AI agent contexts.