Creating Actions

Objective

After completing this lesson, you will be able to discover and evaluate ways to ensure that destination applications receive data as Actions.

Introduction to Actions

In this lesson, you will explore and evaluate strategies to ensure data is accurately activated and delivered to destination applications as Actions. We'll guide you through the setup process in the SAP Customer Data Platform console, focusing on how Actions are configured, validated, normalized, and mapped to facilitate seamless data integration across systems.

Actions in SAP Customer Data Platform are essential for configuring how data is pushed to external systems through pre-configured Destination Applications. By setting up Actions, you define the specific way in which data transitions from the CDP to external platforms, ensuring it aligns with governance rules, data formats, and application requirements.

Once defined, Actions can be used with Audiences for cloud connector actions or triggered in CX Flows. This flexibility facilitates targeted data delivery aligned with audience journeys and interaction flows.

Creating the Actions Schema

While you can create an Action schema by manually adding nodes and assigning attributes, you can also streamline the process by dragging and dropping a JSON file onto the canvas. This flexibility allows you to tailor the schema to meet specific business needs, ensuring that the right attributes are included in data processing.

An example Action Schema definition is displayed in Tree format on the left side, and JSON format on the right side.

Action Validation

Validation ensures that only valid data is transmitted to destination applications by an action triggered by a CX Flow or an Audience. When an action is initiated, outbound data undergoes a validation check against predefined rules associated with specific action attributes. This process helps maintain data integrity by preventing erroneous data from moving forward through system flows. Should the data fail to meet these validation criteria, the action is halted; the data is not passed onward, preventing the destination applications from receiving and processing invalid information.

Validation is shown turned on for an example Action Schema attribute, two validation types are presented, By Format and By Allowed values. By Format is selected, and a drop-down shows the available validation formats.

Validation supports a range of common data formats, including date-time, email address, hostname, and IP address, ensuring broad applicability across various data scenarios. Additionally, this feature offers flexibility by allowing users to customize validation rules using regular expressions, allowing precise control over data requirements and compliance standards. This customization empowers users to tailor validations to their specific business needs, enhancing the reliability of data handling processes within the SAP Customer Data Platform.

Action Normalization

Normalization ensures that data is transmitted in a format that aligns with the specific requirements of each destination application. Much like a universal translator, normalization transforms customer information to meet diverse formatting standards, thus preventing errors and promoting operational efficiency.

Normalization is turned on for an example Action Schema attribute, along with the normalization rules. Using regular expressions to find and replace a specific part of the string value is also supported.

Normalization is essential, especially when dealing with data elements like phone numbers, which are notoriously formatted differently across applications. Some might accept spaces, while others demand compactness without any punctuation. The normalization rules are pivotal in stripping out unnecessary spaces and punctuation, employing techniques like Regular Expressions (Regex) for precise modifications. This transformation guarantees that your data is adaptable and adheres to the standards of each platform, maintaining consistency and enhancing interoperability.

Actions Schema Mapping

Proper mapping of action attributes to your existing customer schema builds structured pathways for your customer data, enabling seamless integration and improved data utility. It involves aligning attributes such as profile, metadata, activity indicators, and processing purposes to ensure they integrate seamlessly into destination applications.

Schema Mapping links the Customer Schema attributes on the left side to the Action Schema attributes on the right side. Mapped attributes are highlighted on both sides.

Your existing customer schema can be enhanced by integrating these mapped action attributes. Within your customer schema, you can target:

Profile and Group Entities
Align customer profiles and groups for a cohesive view.
Metadata.
Use enriched metadata for informed decision-making.
Calculated and Predictive Indicators
Leverage indicators to anticipate future customer actions and trends.
Processing Purposes
Direct data towards its intended analytical and operational use.
Activities
Track and manage customer interactions and engagements seamlessly.
Application Configuration Attributes
Fine-tune application settings for maximum performance and personalization.

Actions Playground

The Action Playground is designed to streamline the testing and verification of application actions and Customer Experience (CX) Flows. Users can input test actions using mock values through a dedicated form or apply real customer data, enabling a comprehensive examination of the data's journey through the entire action flow. The platform offers a visualization of this flow, allowing users to easily track results, pinpoint failures, and diagnose data processing issues, such as connector problems. With the ability to display logs and errors in both table format and JSON, the Action Playground aids in identifying specific errors related to schema mapping, identity resolution, and various CX Flow steps and actions.

The Actions Playground tool, with the Mock customer tab open. Users can test and verify the action by mocking a customer profile or pick and use a real customer profile to trigger the action. As part of the mock form, an activity indicator is selected, along with the updated date. The action flow and result is visualized, the action mapping popup shows detailed log information about the step in the flow.

Action Playground accelerates the creation of applications and facilitates their initial setup. By providing users with tools to achieve higher-quality application configurations, the platform enhances the overall performance and reliability of the SAP Customer Data Platform. It enables the testing of CDP and connector settings to assess their performance in the pipeline, offering transparency and fostering confidence in the data flow.

Creating Actions Demo – Video

Summary

By mastering the creation and management of Actions, users can effectively tailor their data activation processes in the SAP Customer Data Platform. Through schema mapping, action validation & normalization, and the Actions Playground tool, data is accurately and efficiently delivered to destination applications.