Configuring Event Metadata in the SAP Customer Data Platform

In SAP Customer Data Platform, configuring event metadata is a critical step in ensuring accurate and efficient data ingestion and processing. This lesson will delve into the concepts of deduplication ID and timestamps, their use cases, and practical application examples.

A deduplication ID is a unique identifier assigned to each event to prevent duplicate events from being ingested into the system, which enhances data accuracy and reduces redundant data storage. When multiple events are sent with the same identifier, only the first instance is ingested, while the others are discarded.

• Use Case

  Consider a scenario where multiple systems record a purchase event at different transaction confirmation stages. Without a deduplication ID, each confirmation could spur the creation of multiple event records, inflating the actual number of purchases. By assigning a deduplication ID, redundant events are filtered out, ensuring the generation of a single, accurate event record per purchase.

• Application Example

  In a retail CRM system, whenever a customer completes a transaction, the transaction ID (which is unique for each purchase) can be mapped to the deduplication ID field in the event metadata. This ensures that if the same event data is received multiple times due to retries caused by system errors, only one event per transaction ID is ingested.

The Timestamp field is used to record the exact time an event occurred. This can be different from the ingestion time, which records when the event data was received by the SAP Customer Data Platform system. Mapping the original event timestamp is crucial for maintaining the chronological sequence of events and ensuring data consistency.

• Use Case

  In customer profile updates, understanding when an activity occurred (for example, a website visit, a purchase, or a customer service interaction) is vital for behavioral analysis and timely decision-making. The timestamp field allows the system to accurately update the customer's profile with the exact time the event occurred.

• Application Example

  For a marketing campaign, an email open event needs to be tracked. It is the timestamp marking when the customer opened the email that should be recorded, not the time when the SAP Customer Data Platform system processed this information. Mapping the 'open event timestamp' field to the event metadata timestamp ensures that customer engagement metrics accurately reflect true interaction times.

You can configure the Timestamp Format to match the data format of your events. Standardizing the timestamp format is essential for ensuring seamless data integration and accurate time-series analysis.

Application Example

If your events record time in ISO 8601 format (for example, 2023-07-23T18:25:43.511Z), you need to specify this format in the timestamp field configuration so the SAP Customer Data Platform can correctly interpret and process the event times.

To configure event metadata using the deduplication ID and partitioning event data with the timestamp field in SAP Customer Data Platform, follow these steps:

1. Identify Fields:

   Select the fields in your event schema that will serve as the deduplication ID and the timestamp.

2. Map Fields:

   Assign the chosen fields to the deduplication ID and timestamp metadata in the event schema.

3. Set Timestamp Format:

   Specify the timestamp format to ensure correct data ingestion.

4. Validate Configuration:

   Verify that the configuration filters out duplicate events and accurately records event times.

On the Model step of the event configuration screen, click the Metadata button to configure the Deduplication ID, Timestamp Field, and Timestamp Format on the Metadata popup. By correctly configuring event metadata, organizations can enhance data quality, ensure accurate customer profiling, and improve operational efficiency in their SAP Customer Data Platform implementations.

In this lesson, we covered the essentials of configuring event metadata in SAP Customer Data Platform, focusing on the deduplication ID and timestamp field. The deduplication ID prevents redundant event ingestion by ensuring only the first occurrence of an event with a given identifier is ingested. The timestamp field records the exact event occurrence time, vital for maintaining chronological accuracy. We also highlighted the importance of setting the correct timestamp format to ensure accurate data processing. By following steps to identify, map, and validate these fields, users can ensure data accuracy and operational efficiency in their SAP Customer Data Platform implementations.