Name: Processing of Imported Data in SAP Marketing Cloud
Uploaded: 2022-12-14
Duration: 321 s
Description: Now, what's the use of understanding the processing of imported contact data in SAP Marketing Cloud? Well, you prepare your contact data upload by configuring the relevant IDs: Origin IDs for your sources, and additional IDs, such as mobile number, or email. When you do this, just keep in mind how the system deals with the IDs you define.

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>Now, what's the use of understanding the processing of imported contact data in SAP Marketing Cloud? Well, you prepare your contact data upload by configuring the relevant IDs: Origin IDs for your sources, and additional IDs, such as mobile number, or email. When you do this, just keep in mind how the system deals with the IDs you define.<div><br></div></div></div></div></div>

Processing of Imported Data in SAP Marketing Cloud

You can load contacts from multiple sources into SAP Marketing Cloud. But how does the system process the imported data to build and enrich best records? For example, you have this record in your SAP marketing cloud system. Note the SAP Commerce Cloud Origin ID. Now you load this contact data from your SAP Commerce web shop. Note the origin ID when the processing starts by first checking whether or not the origin IDs match. In our example, the existing record and the loaded data have the same origin ID. The next step is to check whether there are further matches involving IDs that are flagged as identification. Relevant. Non IDs that cannot be shared by multiple contacts are considered to be identification relevant, such as a mobile number. If there's no further match, the system updates the existing best record by adding a new email address. In contrast, if there is a further match by an ID that cannot be shared, the system first updates the existing best record. In addition, it flags the updated record for the merge process, which is separately executed. That's the first branch of the data processing. Remember, the merge process runs independently from the import processing to continue. What's the data flow? When no matching origin ID is found, in this case, the system searches right away for contacts where an identification relevant ID match is found. As you know, identification relevant ID that is, non shareable IDs such as a mobile number provide a reliable criterion for the contact identification. If the system finds a matching contact, it checks whether the resulting best record would have two or more different IDs that are configured as one per contact. For example, if the resulting best record would have two different Social Security numbers, that would be contrary to the one per contact rule. If the rule is not violated, the system updates the matching best record. If the one per contact rule is violated, then the system creates a new contact. What if the system finds not only one, but multiple matching contacts? In this case, it creates a new contact and flags it for the separate merge process. That's the second branch of the data processing. What happens when there is neither a matching origin ID nor an identification relevant ID match? Then the system searches for a match with sharable IDs plus contacts. Full name. If it finds a match, just one match. Then it checks for a possible violation of the one per contact rule. If that is not the case, it updates the matching contact. Otherwise, it creates a new contact. If there's no match with shareable ID plus name, then again a new contact is created and the same applies when the system finds multiple matching contacts with shareable IDs plus name because the matches could be ambiguous. That's how the processing of imported contact data works in principle. Note the three levels there is first, the check on a possible origin ID match, then potential matches with the identification relevant IDs are focused on. Finally, the system checks the possible match with shareable IDs plus name and the result per record. You load. Exactly one contact is updated or newly created. You can adapt the standard process using business add ins or bodies. For example, to review imported interaction contact data even before it gets processed, or to reject the matching contact, or to find a matching contact as desired. All that remains is to show how the system processes contacts that are flagged for merge right? As mentioned, the merge is decoupled from the import data processing. Apart from that, the merge process is very similar. The system checks whether the flagged contact matches one or more contacts by identification relevant IDs. If there is a match, the system checks for a possible violation of the one per contact rule, and if it's not violated, the contacts are merged and the merge flag is removed. If there is a violation, the merge flag is simply removed. The same applies when no matching contact is found. Note that you can adapt the merge processes using bodies. Now what's the point of understanding the processing of imported contact data in SAP marketing Cloud? Well, you prepare your contact data upload by configuring the relevant IDs origin IDs for your sources, and additional IDs such as mobile number or email. When do you do this? Keep in mind how the system deals with the IDs you define.