Name: Planning and Configuring the Contact Data Load in SAP Marketing Cloud
Uploaded: 2018-9-6
Duration: 311 s

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div><div><div>Are you wondering what id origins are and how to configure them? Watch this video to get some important insights and aspects to consider when loading contact & account data into SAP Marketing Cloud. Stay tuned for more!</div><div><br></div></div></div>NOTE: This video refers to "Hybris Marketing Cloud" instead of "SAP Marketing Cloud" but the content of the video is still valid. Also, your SAP Marketing Cloud user interface may appear differently, but all functions remain the same, regardless of UI appearance.<br></div></div></div></div>

Planning and Configuring the Contact Data Load in SAP Marketing Cloud

In SAP Hybris marketing cloud contact master data is stored in one single best record per contact. You can load contact data from various sources. For example SAP Hybris, commerce or social media. Learn how to configure the data load to build best records and SAP Hybris marketing cloud from different data sources. Let's see how the system creates the best record when you load contact data, for example, from an SAP Hybris Commerce web shop. To find the matching contact, the system considers email and mobile number as well as the ID. Here it is SAP Hybris consumer number 4711. If the system cannot find one, it simply builds the new contact. Now let's load a second data record. Again the system uses the origin ID and the additional ID the mobile number to find the match and contact. This time it detects a record with a matching ID, the mobile number. As a result, the system updates the existing best record. Notice that the name, email address, and mobile number originate from the Hybris commerce record. While city and country are taken from the C for C record. What can we learn here? To enable the building of best records, you first define one origin per data source. Second, you configure additional IDs for the data of your sources. For example, email or mobile. Let's have a look at a configuration example. You can figure that the SAP Hybris Commerce ID and the SAP cloud for customer ID can not be shared. Additionally, the mobile number cannot be shared. In contrast, email addresses can be shared by multiple contacts. What happens when you load this SAP cloud for customer record based on your configuration? The system finds a matching contact. And this is what the updated best record looks like. Remember, you defined the mobile as not shareable, so this ID, the mobile number is a reliable match. The data can be merged. Now what happens when you load these two records from a web shop? Your customizing settings say that there must only be one workshop ID per contact. As you can see, the mobile IDs would match. However, only one web shop ID is allowed per contact according to your configuration settings. As a result, the system creates two new contacts. So how can you control the matching merge process? First, you should understand what kind of data you get from the connected sources. Which characteristics can be used as IDs to identify contacts? Which IDs do the sources have in common? Which IDs are shareable and therefore not useful for matching? What is your matching strategy? Second, determine the data source that is the most reliable. Third, transfer your rules into configuration. Let's see how it looks in the system. Navigate to the configuration app. Origin of contact IDs. Select one of the pre delivered origins or click add to define a new origin. Let's focus on the settings for Match and Merge. First. First define an origin. Why? Because the contacts are created and enhanced with the data from origin IDs. And remember only one origin per data source. Now decide whether a contact can only have one ID of the origin you are defining. For example, a contact can only have one social security number as an ID. Then decide whether the ID can be shared by multiple contacts. For example, family members can share a landline telephone number. Specify the priority of the origin one for high to 99 for low. The more reliable the data source, the higher the priority of its origin. Having configured the data load, you can import your contacts data. Finally, check your data load. The Marketing Data Stewardship Group offers a set of apps to help you verify your data. Use the Contact Origin data dashboard, for example, to get an overview of the contact origin mix. The comprehensive filter capabilities let you spot check the data and verify your assumptions.