What's New in HCL CDP

The following list mentions the new features, and the changes to existing features, in HCL CDP 25.1.1:

Discover Integration

Enhanced HCL Discover Integration for CDP with the following:

• Real-Time Behavioral Data: Live events from Discover now directly sent to CDP and Journey.
• Smarter Customer Profiles: Customer One View is enriched with the latest activity data to allow the current understanding of each user.
• Accurate Segmentation: Discover interactions can be used to create both real-time and batch segments to deliver more targeted and relevant experiences.
• Optimized Data Flows:
  • Real-Time Flow: Ideal for immediate actions and personalization, supporting COV updates, activity tracking, and live event triggers.
  • Batch Flow: Designed for historical analysis and batch activation, supporting path and funnel insights with next-day availability.

Simplified Journey Integration

In this release, the Journey integration is simplified with fewer configuration parameters in the General Rule and Configure Parameter tabs. You can now map fields from CDP (Athena) to journey fields through a simplified mapping interface. An auto-configuration feature automatically matches fields when exact name or structure matches are detected.

HCL Link Integration

HCL CDP now supports direct integration with external platforms via the HCL Link connector.

Streamlined Integration Workflow

The HCL Link integration process is now clearly defined and broken down into two main parts:

1. Creating a Link Connection: Define a new source type (e.g., HubSpot) by providing connection details like the URL, client ID, and client secret.
2. Configuring a Link Connector: Create a new source from the established connection. This action defines the "Link Action," which specifies how data will be read and processed by CDP.

Data Flow for External Sources

HCL Link acts as an intermediary to ensure data flows into CDP:

• HCL Link retrieves data from the configured external source.
• It transforms the data to meet CDP's specific format requirements.
• The processed data is then pushed to HCL CDP using the Data Ingestion (DI) REST API.

Event Routing

You can now define routing at a granular level using the Event Dictionary, enabling precise control over which events are sent to which destination based on:

• Event Name: Routing based on the track events.
• Event Type: Differentiate routing based on the event's category (e.g., page, identify).

Event Transformation

The Event Transformation feature allows modifying and standardizing event payloads before they are sent to downstream systems. This is powered by the FreeMarker Template Language (FTL), which allows you to:

• Standardize Data: Convert nested input structures into flattened, consistent output formats.
• Rename and Filter Properties: Easily rename event fields to meet destination schema requirements (e.g., properties.FirstName to first_name) and filter out unnecessary attributes (e.g., userAgent).
• Apply Business Logic: Implement custom rules to modify the event data.

Role Based Access Control (RBAC) for Dashboard

While accessing HCL CDP from the Platform, admins can now create, edit or delete user roles, and manage access to the features. For this release, HCL CDP supports the View Dashboard and Manage Dashboard Builder accesses to control access to specific users based on the assigned roles.

RTS Segment edit and activation workflow

Introducing RTS segment workflow with three-stage lifecycle that provides clear, step-by-step status tracking and preserves the live segment during update failures, ensuring reliability and zero campaign downtime.

The stages of the RTS Segment Edit and Activation workflow:

Data Preparation:

This is the initial stage where the system analyzes the segment definition and prepares the data for processing. This step involves communicating with the Detect API to validate and set up the segment logic.

• Current Status:Data_Preparation_In_Progress
• Success Status: Data_Preparation_Completed
• Terminal Failure Status:Data_Preparation_Failure

Data Synchronization (Data Sync):

Once the data preparation is complete, the system proceeds to synchronize the necessary data. This involves transferring the data according to the new segment rules so it is ready to be used.

• Current Status:Data_Sync_In_Progress
• Terminal Failure Status:Data_Sync_Failure

Activation

This is the final stage where the segment is deployed and made available to downstream systems and channels. This includes the final two-step activation call to ensure deployment is successful and reliable.

• Status:Activation_In_Progress
• Success Status: Active
• Terminal Failure Status:Activation_Failure

The segment is considered Live and ready for use once the Activation stage is successfully completed and the status is Active.

UX revamp of CDP Dashboard

UI of CDP has been fully migrated to Angular for enhanced scalability and maintainability. This enhancement improves the marketer usability through drag-and-drop segment building, responsive dashboards, and robust security and compliance features.