Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

What is the principle of SAP Marketing Cloud's Contact import configuration and data merging

2025-02-22 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >

Share

Shulou(Shulou.com)06/01 Report--

Today, I will talk to you about the Contact import configuration of SAP Marketing Cloud and the principle of data merging, which may not be well understood by many people. In order to make you understand better, the editor has summarized the following contents for you. I hope you can get something according to this article.

The master data of many SAP systems can be imported from external systems, as is the case with SAP Marketing Cloud. Contact master data can come from social media such as Hybris Commerce,CRM,ERP or Twitter,Facebook. Contact from different channels may correspond to the same person in the real world, then there is a process in which the logic of the process is to integrate the contact data from different channels to piece together a contact master data containing complete information and store it in the Marketing Cloud system. The patchwork process is called merge, and the complete Contact structure formed after patchwork is called Golden record.

The blue circle in the following diagram is called Main facet, which represents the ID of each contact data on a source system, for example, ID 123 on ERP system, ID 456 on Twitter, and so on. The yellow circle is the attribute of contact in their respective source systems, such as a contact with an ID of 456 on the Twitter website, and its name attribute is jerrywang@sap. The yellow circle is called additional facet.

Through a series of configurations in SAP Marketing Cloud, tell the system what kind of contact operation should be performed when contact data from different data sources are detected and at least one of the same attributes exists, that is, merge or create.

For example, in the following figure, there are three pieces of contact data on ERP,Facebook and Web Shop, and the values of their Email addresses are all the same. Then when importing data, based on the predefined configuration, Marketing Cloud believes that the three pieces of data point to the same person, so at last merge comes out to generate a unique contact record.

The process of Marketing Cloud specific merge is to take three records with the same Email address as the input of the current merge according to the customizing configuration in the SAP Marketing Cloud system, and then project the attributes in this record to the final Golden Record one by one. If you think of Golden Record as a final complete jigsaw puzzle, the merge process is somewhat similar to a jigsaw puzzle-- piecemeal information scattered across various data sources is merged into a whole and stored in the Marketing Cloud system for subsequent processing.

The relevant customizing settings in Marketing Cloud for the merge operation of the contact import system play a vital role in the whole contact import process.

Like many cloud products such as SAP Cloud for Customer, SAP Marketing Cloud's customizing is done in browsers.

Click the tile of Manage Your Solution in Fiori Launchpad

Enter Configure Your Solution

Search according to the keyword contact and find the Contacts and Profiles-related configuration in the search results list:

The sixth step, OriginContactID-Configure, is to perform the configuration of merging or creating new operations for contact data from different platforms when merging.

After clicking, you can see a list of contact attributes. From the list of attributes, it is not difficult to infer that the data sources that SAP Marketing Cloud supports the import of contact are Same4HANAGO contact data sources, such as Twitter,Facebook and so on.

The figure above has two columns, corresponding to the interface that specifies whether One Per Contact and Shareable are true or false for each property. The former, as the name implies, if set to true, means that a contact can only have a unique value in the same data source system, such as a person's passport number, or the Customer ID; in the SAP system is like Email, landline number, fax number. If multiple values are allowed in the same data source system, One Per Contact is set to false. The Shareable attribute is set to true, which is suitable for attributes that allow multiple different contact to have the same value in the same data source system, such as the same landline number of a family's contacts.

For each Contact attribute, there are four true/false status permutations and combinations of One Per Contact and Shareable. In two cases where One Per Contact is true, even if the system detects a matching attribute, it may lead to the creation of contact data instead of merge, that is, the second and fourth lines in the following figure are marked with exclamation marks.

Look at some specific examples:

1. The Sharable of the mobile number attribute is false,One Per Contact and false.

The mobile fields of these two pieces of data from SAP ERP and Web Shop are the same, Marketing Cloud is merged, and the merged contact data has two facet from ERP and Web Shop, respectively.

two。 The Sharable of the mobile number attribute is false,One Per Contact and true.

There are two contact records in the same Web Shop system, although the values maintained by their mobile phone numbers are the same, because One Per Contact is set to true, Marketing Cloud does not merge, but creates two new Contact records, whose mobile facet values are both the same mobile phone number, and the Web Shop ID facet values are respectively from the original values of the Web Shop system.

3. The Sharable of the Email attribute is true,One Per Contact and false.

The two pieces of data from SAP ERP and SAP CRM have the same Email address, and One Per Contact also maintains false, but because their full name is inconsistent, two pieces of Contact data will be generated when they are imported into Marketing Cloud.

The source of each attribute can still be viewed through its tab Origin Data for Contact data imported into Marketing Cloud.

After reading the above, do you have any further understanding of SAP Marketing Cloud's Contact import configuration and data merging principles? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Internet Technology

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report