HCL CDP Integration

HCL MaxAI CDM and the HCL Customer Data Platform (CDP) exchange data in both directions. HCL CDP sends campaign interaction data and reference data to CDM. CDM returns unified Customer 360 and Campaign 360 insights to HCL CDP.

Data from HCL CDP to CDM

HCL CDP provides the following data to CDM. CDM loads the data daily into the Landing Zone (LDZ) and then normalizes it in the Business Data Vault (BDV).

Table 1. Data from HCL CDP to CDM
Data Source Used for
Contact history HCL Unica Campaign (customer and account audiences) and CleverTap Shows which campaign, offer, and channel reached each customer, and when.
Response history HCL Unica Campaign (customer and account audiences) and CleverTap Records opens, clicks, bounces, failures, and other outcomes of each contact.
Customer profile HCL CDP customer data Links Unica and CleverTap customer IDs to the same customer.
Channel cost master HCL CDP reference data Calculates the cost of each contact by channel.
Product mapping HCL CDP reference data Links campaigns and goal events to products, and sets the conversion tracking period for each product.
Goal events HCL CDP event data, stored in cdm_ingest_db Identifies customer actions, such as an application submit, that lead to a conversion.
Conversions Conversion feed Records business outcomes, such as a loan disbursal, and the revenue that they generate.

How CDM Processes HCL CDP Data

  1. HCL CDP data lands in LDZ tables with no changes.
  2. CDM standardizes channel names (Email, SMS, Push, WhatsApp, and RCS) and response outcomes (Delivered, Opened, Clicked, Bounced, and Failed).
  3. CDM resolves each customer, account, or CleverTap audience ID to a single customer ID.
  4. CDM adds the product and contact cost to each interaction.
  5. CDM stores the results in two BDV tables: BDV_UA_COMBINED_CONTACTHISTORY_SNAPSHOT and BDV_UA_COMBINED_RESPONSEHISTORY_SNAPSHOT.
  6. CDM attributes each conversion to the campaign click that most likely led to it, and stores the result in FACT_CONVERSION.
  7. The Aggregate Layer calculates campaign and customer metrics, which feed Campaign 360 and Customer 360.
Note:
The rec_src column on each record shows whether the record came from Unica or CleverTap, so you can analyze both sources together or separately.

Data from CDM to HCL CDP

HCL CDP consumes Customer 360 and Campaign 360 outputs, as well as the underlying CDM history and fact datasets.

  • Customer 360 to HCL CDP: Customer resolution, demographic and behavioral attributes, consent, risk indicators, product holdings, and campaign engagement metrics, such as contacts, responses, conversions, revenue, and spend by channel.
  • Campaign 360 to HCL CDP: Performance feedback, segment lift, audience insights, and spend and revenue for return on investment (ROI) analysis. Includes Flowchart 360 execution-level engagement signals as a sub-component of Campaign 360.
  • Combined Contact History (CH) and Response History (RH) tables: Unified contact and response records in BDV_UA_COMBINED_CONTACTHISTORY_SNAPSHOT and BDV_UA_COMBINED_RESPONSEHISTORY_SNAPSHOT.
  • Conversion and Transaction facts: Fact-level conversion and transaction data, including FACT_CONVERSION and transaction fact tables, for campaign attribution and business-outcome analysis.

HCL CDP uses these datasets for segment definitions, journey orchestration, and real-time activation.

What This Means for Users

  • Unica and CleverTap campaign activity for the same customer appears in one Customer 360 profile.
  • Campaign metrics use the same channel names and outcome definitions across all sources.
  • Campaign 360 shows spend and revenue, so you can compare campaign cost with results.