In order to send data from the SAP Customer Data Platform to a target system, you need to configure ‘Actions’. Actions are a part of the outbound integration capabilities of the SAP Customer Data Platform. They are used to define the specific operations that should be performed with the data, such as sending it to a target system. This is done by configuring the action to connect to the target system’s API, defining the data payload, and specifying when the action should be triggered. The SAP Customer Data Platform allows for the creation of custom actions or the use of pre-built actions for common tasks1.

References = The explanation provided is based on the information available in the SAP Help Portal documentation for the SAP Customer Data Platform

Within the SAP Customer Data Platform, you can perform various actions on a segment. Specifically, you can activate a segment to make it available for use in campaigns and other marketing activities. Additionally, you have the option to delete a segment if it is no longer needed or relevant. Activation is a crucial step to ensure that the segment is operational, while deletion helps maintain the organization and efficiency of your segment management by removing obsolete or unused segments.

References = This response is based on the official SAP Customer Data Platform documentation, which provides detailed guidance on managing segments, including the ability to activate and delete them12.

 When importing primary customer residential address data into SAP Customer Data Platform using the console, you should update the profile customer schema. This involves defining a customer schema to create a common data model for all incoming customer data, which allows for the coherent view of customers by unifying data from various sources1.

References = The procedure for updating the profile customer schema is detailed in the SAP Help Portal documentation under the section 'Configuration Customer Schema’1.

The SAP Customer Data Platform is distinguished by its ability to unify customer data from various sources into a single customer profile, which is a capability not typically found in CRMs or data warehouses. This unification allows for a comprehensive view of the customer and enables real-time data processing, providing insights into customer behaviors as they occur. These capabilities are essential for delivering personalized customer engagements and are a significant differentiation from other platforms that may not support real-time processing or may only handle structured data without the ability to unify it.

References = The information is based on the features highlighted in the SAP Customer Data Platform documents, which emphasize the importance of unifying customer data and the platform’s real-time data processing capabilities12345.

 In the SAP Customer Data Platform, a single segment can be defined with a maximum of 200 conditions. This allows for the creation of highly customized customer segments by using various ‘include/exclude’ and ‘and/or’ conditions, as well as different operators. These segments are evaluated in real-time whenever a customer profile is updated, ensuring that the segmentation is always current and applied to both the contextual profile and the unified customer profile views.

References = This information is confirmed by the SAP Help Portal documentation on Segments and Segment Attributes within the SAP Customer Data Platform12.

The SAP Customer Data Platform is designed to manage customer data across different levels of organization. A tenant represents an instance of the platform provisioned for an organization, and within this tenant, multiple workspaces can be created. These workspaces serve as separate environments for development and production purposes. Additionally, a business unit, which is a logical partition within a workspace, can also contain multiple workspaces, allowing for further segmentation and management of customer data within the same organizational unit.

References = This relationship is outlined in the SAP Customer Data Platform documentation available on the SAP Help Portal, which provides comprehensive information on the configuration and management of tenants, workspaces, and business units12.

Within the SAP Customer Data Platform, the customer schema can be configured to include various elements. Specifically, ‘Activities’ and ‘Profile entity’ are two components that can be configured as part of the customer schema. The ‘Profile entity’ is a collection of attributes associated with the customer’s identity, which includes both predefined attributes and custom attributes that can be added as needed. On the other hand, ‘Activities’ refer to the actions or events associated with the customer, which can also be defined and included in the customer schema12.

References =

SAP Learning: Using Customer Schema1.

SAP Help Portal: Customer Schema2.

In the SAP Customer Data Platform, a business unit is defined as the part of a business that is tasked with maintaining continuous business relationships with customers within a specific market. This definition implies that a business unit is not just a segment or a division, but a functional entity within the organization that directly interacts with the customer base. Furthermore, it is important to note that a single business unit can encompass multiple brands, indicating that it can operate across different product lines or service offerings under the broader corporate umbrella. References = This information is corroborated by the SAP Help Portal, which provides a clear definition of a business unit within the context of the SAP Customer Data Platform1.

 To configure SAP Customer Data Platform to ingest tracking data from your website, you need to create a Web Client Application within the SAP Customer Data Platform. After creating the application, you will load the SDK on your website. Then, you add the report function to start sending behavioral data from your website to the SAP Customer Data Platform application. The process involves setting up an application to receive events sent from your website, preparing a list of trusted domains, and creating events with all the parameters you’ll be reporting, such as page views and clicks.

References = This information is verified and matched with the details provided in the SAP Customer Data Platform documentation, specifically within the Integration Guide for Web Client Application1.

 Within the SAP Customer Data Platform, you can design predictive models, also known as predictive indicators, for various purposes. The types of models you can create include predicting churn probabilities for individual profiles (CHURN Profile), predicting churn probabilities for groups (CHURN Group), and predicting customer lifetime value for individual profiles (CLV Profile). These models help in understanding and anticipating customer behaviors, which is crucial for maintaining customer relationships and maximizing customer value.

References = The types of predictive models available for configuration in the SAP Customer Data Platform are detailed in the SAP Help Portal documentation on managing models and predictive indicators1.

The correct query syntax for searching customers belonging to a segment using the REST API in the SAP Customer Data Platform is to use the having function in conjunction with the segments object. This allows the query to specify the segment name and value as conditions for the search. The syntax select * from profile where having(segments, (segments.name = and segments.value = )) is used to retrieve all profiles that match the specified segment criteria. References = This information can be found in the SAP Help Portal’s documentation on Query Syntax Specification for the SAP Customer Data Platform1.

In the context of the SAP Customer Data Platform, the active processing purpose status for an incoming event is always attached to the event. This status indicates whether the data is allowed to be stored in the system, and which data may be sent out to destination applications. The processing purpose can be dynamic, meaning it is part of the incoming event’s data model and is saved to the customer profile with the status and timestamp data that was sent with the event. This is achieved by mapping the event purpose nodes to the data privacy framework within the platform.

References = The information is based on the SAP Help Portal documentation on Processing Purposes, which details the use cases, core concepts, and data governance enforcement related to processing purposes within the SAP Customer Data Platform1.

To ingest a single event by ID in the SAP Customer Data Platform, the appropriate API endpoint must be used that specifically allows for the identification and ingestion of an event based on its unique identifier:

B. /api/businessunits/{businessUnitId}/applications/{applicationId}/dataevents/{dataEventId}/event:This API endpoint is structured to target a specific event within the context of a business unit and application, using the unique event ID (dataEventId) to precisely locate and ingest the event in question. The endpoint'sstructure facilitates the targeted ingestion of events, ensuring that the correct event is processed and incorporated into the platform based on its unique identifier.

This method allows for precise control over event ingestion, enabling the integration of specific events into the customer data platform as needed, based on their unique identifiers.

References:

SAP Customer Data Platform API documentation detailing endpoints for event ingestion.

Technical guides on ingesting events into the SAP Customer Data Platform using API calls.

 To implement a B2B data model within the SAP Customer Data Platform, the use of groups and relationships is recommended. This approach allows for the creation of a unified view of customer contacts, associated accounts, and the relationships within these accounts. It enables enriched, real-time insights into B2B interactions and activities, which are crucial for understanding and responding to business needs and customer demands in a timely manner.

References = The implementation of a B2B data model using groups and relationships is described in the SAP Customer Data Platform training and community resources, which provide detailed information on how to leverage these features for B2B use cases12.

 The event model in the SAP Customer Data Platform supports various metadata fields to provide information about the event itself. Two of the supported metadata fields are:

Timestamp: This field is used as the original timestamp of the event occurrence. If not defined, the time of event ingestion is used instead.

Deduplication Identifier: This field is assigned for deduplication purposes to prevent the same event from being ingested more than once. If multiple events are sent with the same identifier value in this field, only the first will be ingested.

These metadata fields are crucial for ensuring the accuracy and uniqueness of event data within the platform.

References = The details about the supported metadata fields are found in the SAP Customer Data Platform documentation under the section "Event Metadata"1.

Before ingesting customer data into the SAP Customer Data Platform (CDP), it is essential to configure processing purposes within the system. This is a built-in mechanism that identifies the different purposes for handling customer data that streams into and out of the system. The processing of personal data is governed by regional and local regulations, such as GDPR and CCPA. The CDP ingestion process allows businesses to ensure compliance with these regulations, restrictions, and policies applicable to customer data usage. It is important to note that the CDP ingestion process does not collect, audit, or handle the actual collection of processing purposes. Instead, it allows for storing those collected purposes and applying data governance based on those purposes. In the context of CDP, the processing purpose is sent as data points in an event from a source, and multiple processing purposes may be defined per business unit. Only those processing purposes needed for managing customer data in CDP should be added.

References = The detailed explanation is based on information found in the SAP Help Portal, specifically within the documentation for processing purposes in the SAP Customer Data Platform1.

When creating a calculated indicator within the SAP Customer Data Platform, you can utilize attributes from the customer schema such as Events (B), Profile ©, and Activity indicators (D). These attributes can be combined in a mathematical equation to create a new indicator that reflects complex calculations. For example, you can use numeric profile attributes, activity indicators, or activities from the CDP schema to calculate the new indicator, and you can also apply conditions to narrow down the customer profiles to which the calculation will be applied.

References = This information is supported by the SAP Help Portal documentation on creating a calculated activity indicator1 and activity indicator calculation2.

In the SAP Customer Data Platform, when creating a calculated indicator, certain attributes from the customer schema are pivotal for defining complex metrics that provide deeper insights into customer behaviors and preferences. The attributes you can use include:

B. Events:These attributes encompass various customer interactions and behaviors captured as events, such as purchases, website visits, or engagement with marketing campaigns. Events can be used to calculate indicators that reflect customer activity levels, preferences, or engagement patterns.

C. Profile:Profile attributes contain demographic and personal information about the customer, such as age, location, preferences, and more. These attributes can be used in calculated indicators to segment customers, personalize experiences, or predict customer behaviors based on their profiles.

D. Activity indicators:These are metrics or flags derived from customer activities and behaviors, such as frequency of purchases, average transaction value, or recent engagement. Using activity indicators to create calculated indicators allows for the synthesis of complex metrics that can measure customer loyalty, lifetime value, or risk of churn.

By leveraging these attributes, calculated indicators can provide multifaceted insights into customer behavior, preferences, and value, driving more informed business decisions and personalized customer experiences.

References:

SAP Customer Data Platform documentation on creating calculated indicators and using customer schema attributes.

Best practices for leveraging customer data attributes in the SAP Customer Data Platform for advanced analytics and segmentation.

In B2B scenarios within the SAP Customer Data Platform, accurately identifying and managing business entities is crucial. The customer schema is designed to accommodate the complexities of B2B interactions, including the need to manage relationships between individual contacts and their associated organizations.

D. BusinessId:This predefined attribute is essential in B2B scenarios, as it serves as a unique identifier for business entities within the platform. The BusinessId allows for the clear distinction and management of business accounts, facilitating effective B2B data handling, segmentation, and personalized engagement strategies.

The inclusion of predefined attributes like BusinessId in the customer schema underscores the platform's capability to cater to both B2C and B2B environments, providing the necessary tools for comprehensive customer data management.

References:

SAP Customer Data Platform documentation on customer schemas and B2B capabilities.

SAP help articles and best practices for managing B2B scenarios within the SAP Customer Data Platform.

When configuring events in a source application for integration with SAP Customer Data Platform, certain key steps ensure the seamless and secure transmission of event data. Two critical components of this configuration process are:

B. Mappings:Event data often originates in formats and structures that differ from the schema used by the target system, in this case, the SAP Customer Data Platform. Mappings are essential for translating the event data structure from the source application into a format that is understood by the platform. This involves defining how each piece of data in the source event correlates to attributes within the SAP Customer Data Platform, ensuring data is ingested accurately and meaningfully.

C. Authentication:Securely transmitting event data from a source application to the SAP Customer Data Platform requires proper authentication mechanisms. This step ensures that only authorized sources can send data, maintaining the integrity and security of the data being ingested. Authentication can involve various methods, such as API keys, OAuth tokens, or other secure authentication protocols, to establish a trusted connection between the source application and the SAP Customer Data Platform.

These steps are fundamental in the event configuration process within a source application, ensuring that the data is not only correctly mapped to the SAP Customer Data Platform's schema but also securely transmitted.

References:

SAP Customer Data Platform documentation on integrating source applications and event data ingestion.

Best practices guides for data mapping and secure authentication in the context of event configuration for SAP Customer Data Platform.

 Within the SAP Customer Data Platform, CX flows are designed to be triggered by specific events that signify a change or an action related to a customer or group. The supported triggers for CX flows include:

Event occurrence: This trigger is activated when a specific event is ingested into the platform, indicating an action or change has occurred.

Customer or group update: This trigger responds to any updates made to customer or group attributes within the platform.

Segment membership: This trigger is based on the inclusion or exclusion of a customer or group within a particular segment, reflecting their changing status or behavior.

These triggers enable the SAP Customer Data Platform to react in real-time to changes in customer data, allowing businesses to deliver personalized experiences at crucial moments in the customer journey.

References = The details provided here are consistent with the information available in the SAP Customer Data Platform documentation, which outlines the various triggers that can initiate CX flows123.

In the context of a B2B data model within the SAP Customer Data Platform, the role of an individual, such as a Sales Manager or CEO, should be stored at the ‘Relationship’ level. This is because the ‘Relationship’ level allows for the association of roles and responsibilities with specific individuals within the context of their interactions and connections to other entities in the B2B landscape12.

References =

SAP Help Portal: B2B for SAP Customer Data Platform2.

SAP Customer Data Cloud Group Model Management documentation3.