Name: Checking the Imported Data in SAP Marketing Cloud
Uploaded: 2018-9-6
Duration: 286 s
Description: When you load contacts into SAP Marketing Cloud, you want to check whether your data came in as expected. In this video you will learn about the various ways you can do this in SAP Marketing Cloud.

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>When you load contacts into SAP Marketing Cloud, you want to check whether your data came in as expected. In this video you will learn about the various ways you can do this in SAP Marketing Cloud. <div><br></div></div></div>

Checking the Imported Data in SAP Marketing Cloud

When you load contacts into SAP Marketing Cloud, you want to check whether your data came in as expected. First, you check the data load monitor to find out about general issues with your uploads, as described in the Video Data Load Monitor. Then it's time to deep dive into the apps import monitor and browse contact origin data to get to the root cause of the error. Let's start with Import Monitor. In our first example, we've uploaded a CSV file with five contacts to find the upload. We can enter the source system, the user, or other relevant information. In our case, we specify the name of the CSV file. The upload is not indicated in the list of errors. Very good. Let's view the success tab. Search for the upload. Here are the details. We have a successful upload. However, as you can see, some data format issues are indicated. Let's check the CSV file. Correct the errors and upload the data again. Search. Okay. Here are two uploads. The latest should be the one with the corrected CSV file. No issues anymore. All right. Another example. Again a very simple CSV file. Click the monitor to search for the upload details. Type the file name of our second example. That's our upload error. Let's see. Okay. It says the origin of the record is not defined. What does that mean? Well it seems the origin we use in the upload specification is not known in the system. Okay. Understood. We'll define the origin in the configuration and then restart the upload processing. We've seen how you can use the import monitor to check the upload process. Now let's go to browse contact origin data. Here you can check whether the data that arrived is what you expect for the check. We filter the contacts using the origin of the data source. For the video. We've uploaded just a few contacts from an origin named Valtrex. So we type V and select Valtrex. The browser displays the data originating from Valtrex, and we can check whether the number of contacts meets our expectation. Okay, that's the expected number of contacts. Now let's make sure that all the data is there. For example, the email addresses. If a field is not in the table by default, we can put it in there and move it to the top. Okay. The email addresses are there. Finally you can spot check the data. We'll pick this contact. That's the inspect contact view. And here we have the best record. We expect that the data from the origin. Valtrex is added to the contact which already exists in the system. Okay. Quite a number of data origins, but here. Yes. The system has added the data from the Valtrex origin to the contact. That means I can see that the data was merged, presumably because the mobile number in my Valtrex data matches the mobile number and the existing contact data. Let's back check another contact. We know that the sample data includes a particular contact with three email addresses. Let's see whether or not they're in the system now. Okay a new contact was created. It only has data from the Valtrex origin right now. Scroll down. Yes. Here are the email addresses. Perfect. So far we have seen how you can use the browser to check your uploaded contact data. But what about interactions for interactions? You can use an additional browser. This browser helps you to verify that your interaction data comes in as expected. For example, in comparison to the numbers indicated by the web analytics of your web shop. As for the contacts, you can use the compact filters for the check or pick and interaction for spot checking, interest tags, or relationships to other products. In addition, you can use the browser to check the aging of your interactions. This is how you can use the import monitor and browse contact origin data to check if your data was imported correctly.