Efficiently Map AWS S3 Customer Data to Salesforce Data Cloud

Mapping customer information stored in AWS S3 to individual and related Data Model Objects (DMOs) within Salesforce Data Cloud is essential for effective data integration. This process involves using custom Data Lake Objects (DLOs) to ensure accurate data representation. 

In this guide, we’ll focus on mapping data from the email address list and identifier list to the corresponding Contact Point Email Address and Party Identification DMOs. By following these steps, you’ll enhance your data management capabilities, ensuring a seamless flow of customer information within your Salesforce environment.

Step 1: Mapping AWS S3 Customer Data Stream

First, we start with the AWS S3 customer data stream, which hasn’t been mapped yet. We’ll map this data stream to the Individual Standard Data Model and the Contact Point Phone model.

1. Select the Individual Standard Data Model:

• Search for “Individual” in the Standard Data Model, then click the plus icon.
• Also, select “Contact Point Phone” and hit Done.

2. Map the Fields:

• First name, last name, and salutation are mapped automatically.
• Customer ID should be mapped to the individual ID.
• Map the mobile phone to the formatted E.164 phone number.
• Map Customer ID to the contact point phone ID key.
• Address the warning by mapping the Customer ID to the party.

Note: Alternate email address, primary email address, and reward number will not be mapped in this step. Passport numbers and reward numbers are also excluded from this mapping.

3. Save and Close: Once the mappings are complete, save and close this mapping.

Also Read: How To Install a Data Bundle in the Data Cloud?

Step 2: Mapping Custom Data Lake Objects

Next, we will map the custom Data Lake Objects: Identifier List and Email Address List.

1. Add DLOs to the Data Space:

• Go to Data Spaces and select the default data space.
• Click “Add Data Lake Objects,” select the Identifier List and Email Address List, click next, and add objects without filters. Save your changes.

2. Map Identifier List DLO:

• Go back to Data Lake Objects and select the Identifier List, which is not yet mapped.
• Start mapping this object to the standard object “Party Identification.”
• You will see that the Identifier Name, Identification Number, Party, and Party Identification Type are mapped automatically.
• Map the Identifier Key to the Party Identification Key and save. Ignore any error messages for now.

3. Map Email Address List DLO:

• Select the Email Address List, which is also not yet mapped.
• Start mapping this object to the “Contact Point Email Address” object.
• Ensure the Party is already mapped.

• Map the Email Address field and the Email Address Key to the Contact Point Email ID field.
• Save and close the mapping.

Explore our Salesforce Data Cloud series on YouTube for expert guidance and tips on leveraging Salesforce Data Cloud effectively.

Conclusion

By following these steps, you can effectively map customer data from AWS S3 to Salesforce Data Cloud, ensuring that multiple email addresses and identifiers per customer are correctly stored and managed. This process enhances your data integration and management capabilities, leading to more accurate and efficient data handling within your Salesforce environment.

For those looking to deepen their Salesforce expertise, consider exploring our Data Cloud Consultant Course. Sign up for a free trial to access 24+ Salesforce certification courses, 50+ mock exams, and 50+ hands-on Salesforce labs. 

Empower your career with saasguru today!