Understanding the Role of Data Extensions

Data Extensions play a vital role in managing and syncing data between Marketing Cloud and Salesforce. By using the lead or contact record ID as the subscriber key, teams can control which tracking data is synced and stored in Salesforce.

This level of control is particularly important for admins who manage multiple franchises or brands, as it allows them to decide which tracking data to store and which to discard. By intentionally placing DEs in the Salesforce DE folder, teams can ensure that tracking data is synced and stored in Sales Cloud.

Platform-Level Explanation

The ability to sync tracking data using DEs is a key feature of Marketing Cloud Connect. This feature relies on the use of subscriber keys to match tracking data with the corresponding lead or contact records in Salesforce.

The root cause of confusion around DE deprecation lies in the complexity of Marketing Cloud Connect and the various ways in which data can be synced and stored.

However, by understanding how to use DEs and subscriber keys effectively, teams can avoid confusion and ensure that their tracking data is synced and stored correctly.

Step-by-Step Solution

To sync tracking data using DEs, teams should follow these steps: use the lead or contact record ID as the subscriber key, create a DE in the Salesforce DE folder, and configure the DE to sync tracking data.

example.ssjs

var de = DataExtension.Init('DE_Name');
var subscriberKey = 'Lead_or_Contact_ID';
de.subscribers.add(subscriberKey);

Best Practices

Checklist for Syncing Tracking Data

• Use the lead or contact record ID as the subscriber key
• Create a DE in the Salesforce DE folder
• Configure the DE to sync tracking data
• Test the DE to ensure data is syncing correctly
• Monitor data storage and adjust as needed

By following these best practices and understanding how to use DEs effectively, teams can ensure that their tracking data is synced and stored correctly, and avoid any potential issues with data deprecation.

What is the purpose of using a lead or contact record ID as the subscriber key?

Using a lead or contact record ID as the subscriber key allows teams to control which tracking data is synced and stored in Salesforce.

Can I use a different type of subscriber key?

No, using a lead or contact record ID as the subscriber key is the recommended approach for syncing tracking data.

How often should I test my DEs to ensure data is syncing correctly?

Teams should test their DEs regularly to ensure data is syncing correctly, ideally after any changes to the DE or syncing configuration.

What happens if I don’t use a lead or contact record ID as the subscriber key?

If a team doesn’t use a lead or contact record ID as the subscriber key, their tracking data may not sync correctly, leading to potential issues with data storage and management.