You are here:
Salesforce Data Extensions in Marketing Cloud Connect
A data extension is a table that contains your data. With Marketing Cloud Connect for Marketing Cloud Engagement, push tracking data from Engagement back to your Sales or Service Cloud orgs using a Salesforce data extension (SFDE). Push any tracking data for emails sent to SFDE audiences using Salesforce Sends to the Salesforce Contact or Lead record in the connected org. An SFDE can use the same Engagement segmentation and filtering tools as a standard data extension. Data extensions created from sends to reports or campaigns have a hard-coded retention policy of 5 days.
Prerequisites
Before you get started with Salesforce data extensions, check the subscriber key, Email field, and field names.
- Use an 18-digit Salesforce Contact or Lead ID (not 15-digit) to map to the subscriber key. If the report field containing the Contact or Lead ID is called Contact ID or Lead ID, subscriber Keys automatically convert from 15 to 18 digits. A field labeled 'ID' uses the 15-digit Contact or Lead ID, which can result in duplicate IDs in Engagement. Contact or Lead IDs that are imported into a standard data extension using a manual flat file import aren’t automatically converted from a 15-digit to an 18-digit subscriber key.
- To import into an SFDE, the email field must be set to type 'email address'. If not, the report is imported into a standard data extension and tracking isn’t returned to the Sales or Service Cloud.
- Field names can’t contain the ? or % characters.
Importing Salesforce Data Extensions
Import Salesforce data extensions into Engagement through Interactions. Create import activities with accessible Sales or Service Cloud reports. For example, if you can’t access a report in Engagement, you can’t access it in the Marketing Cloud Admin folder of Sales or Service Cloud.
Manual and automated imports behave differently in scope-by-user accounts:
- Manual import activities respect scoping, so the number of records that appear in the report are specific to the user who is running the import.
- All automated import activities are executed as the Marketing Cloud API user. Therefore, the number of records reflect the Salesforce system user’s (tracking user) level of access to data.
With non-scope-by-user accounts, imports return results based on the Salesforce system user’s data access.
