Configuring Events Setup

Objectives

After completing this lesson, you will be able to:

  • Configure the Source Application to accept events sent to SAP Customer Data Platform for ingestion.

Events Setup

CDP ingestion – events setup

In the upcoming demo, we'll use the previously created Application that connects into the SAP BTP-provided S3 bucket to ingest profile and activity data from an external source into SAP CDP. First, we need to understand the data we're about to ingest and how it maps into our existing CDP data schemas. Then, we'll create one event per data file: one for ingesting profile data and another for ingesting activity data. Finally, we'll trigger the events, ingest the data, and check the status of the data ingestion.

Before ingesting new data into the SAP Customer Data Platform, we need to understand the nature of the data we're about to import. We need to be aware of the format and content of the raw data.

Let's say we have this simple JSON file containing common attributes such as first and last name, e-mail, gender, and masterDataID, which can link your data with your backend ERP system. We'll use this file format template to import profile information from our external bookstore system into SAP CDP. For our scenario, let's call the profile data file johnroberts-74859289-profile.json. This filename pattern is divided into four pieces: first and last name, masterDataID, the word profile, and the json file extension. We need a filename pattern to import the data into SAP CDP, as that is part of the event setup we're going to perform later on.

For our use case, we'll also need book view data from the same bookstore system. To link the transactional data with a customer account, we can either use e-mail or the MasterDataID as unique keys. The viewedBooks attribute contains an array of objects for customer viewed books. It includes information such as the category that the viewed book belongs to, when the book was viewed, and which device the customer was using while browsing the bookstore for that particular book. The viewed books is stored on a different json file. Its filename follows the same pattern as the profile one, changing the suffix to viewedbooks.

Now that we understand our data, let's setup the necessary events to ingest both of these files into SAP CDP.

Configuring events setup

In this video, you’ll learn how to create profile entity attributes and how to create an activity schema.

Log in to track your progress & complete quizzes