Configure Discover Integration

Before you begin

Before configuring the integration, ensure you have:

• Administrative access to HCL CDP
• Administrative access to HCL Discover
• Configuration details from the Discover team (if applicable), including:
  • Source ID
  • WriteKey
  • Segment ID (if using segmentation)
• Enable Customer One View in the HCL CDP Admin portal. For more information, refer Enabling Customer One View.
• Configure HCL Discover attributes to receive events triggered in HCL Discover. For more information, refer Integrating HCL Discover and HCL CDP in the Unica Discover Admin Guide.

Enabling Customer One View

Customer One View (COV) provides a unified profile of customer activities across touchpoints.

To enable Customer One View:

1. In the Admin Portal, click the Enable/Disable Module option.
2. Select a Campaign ID, and click SUBMIT.
3. Click EDIT, and on the MISCELLANEOUS tab, select the Customer One View checkbox.
4. Once enabled, click SAVE. You can view customer activities in the Customer One View tab.

Configuring the REST API source

To enable HCL Discover to send events to HCL CDP, you must first create a REST API source.

To create a REST API source:

1. From the Menu bar, click Data Pipeline > Sources.
2. Click + Create New Source.
3. Select REST API, and then click Proceed.
4. Enter a source name, and then click Create Source.
5. On successful creation, copy and save the following authentication keys:
   • x-api-key
   • x-api-passkey
   You will use these keys to authenticate event payloads from HCL Discover.
6. Copy the Source ID from the REST API source. This ID will be used as the WriteKey in the event payload.
7. Copy the ID displayed at the end of the URL. This ID will be used as srcid in the event payload.
   Note: Currently, only one DIAPI data source can be added for HCL Discover integration.

   For more information about creating REST API sources, see REST API.

Configuring destinations

After creating the REST API source, you must add destinations to define where events should be routed.

To add destinations:

1. Open the REST API source you created.
2. Add one or both of the following destinations based on your integration flow:
   • For SST flow: Add HCL CDP Unified Profile
   • For Non-SST flow: Add Kafka
3. Ensure the destinations are enabled.

Configuring the event dictionary

The event dictionary defines which events CDP should recognize and process from HCL Discover.

To configure events:

1. From the Menu bar, click Data Pipeline > Event Dictionary.
2. Define custom events that need to be tracked, such as login, sign-in, product selection, and product navigation.
3. For each event, add the appropriate destinations:
   • Enable Unified Profile for SST flow events
   • Enable Kafka for Non-SST flow events

Configuring the Discover event payload

HCL Discover sends events to HCL CDP using the DIAPI endpoint /v3/data. The event payload must include specific required parameters.

Required parameters

The following parameters are required for HCL CDP to determine the source and type of event:

Request headers

The request headers must include:

• x-api-key: Obtained from the REST API source
• x-api-passkey: Obtained from the REST API source

Supported data types

HCL CDP currently accepts the following data types:

• String
• Number
• JSON
• Array

Sample DIAPI request

The following example shows a sample curl request for sending event data to HCL CDP:

curl --location '<domain>/v3/data' \
--header 'Content-Type: application/json' \
--header 'x-api-key: <x-api-key>' \
--header 'x-api-passkey: <x-api-passkey>' \
--data '{
  "properties": {
    "Origin": "Discover",
    "identity": "xy_0000004640",
    "category": "Travel",
    "label": "Tours and Packages",
    "action": "Submitted",
    "CT App Version": "10.4",
    "CT Source": "Web"
  },
  "eventname": "Tours and Packages Submitted",
  "type": "track",
  "ts": 1747215980
}'

Replace <x-api-key> and <x-api-passkey> with the values obtained from the REST API source.

Sample event payload

The following example shows a complete event payload structure:

{
"srcid": "2931",
"WriteKey": "7i3rtmzivxstrbnk7vhi",
"id": "a12b3egd-b563-42c5-9fb7-558103a566ca",
"ts": 1748539959,
"type": "track",
"eventname": "OrderTotal2",
"properties": {
    "vizid": "B8891326D9873FEADFB287FE49850821",
    "identity": "ENC_CUST_145",
    "ordervalue2": "ENC_CUST_145"
    }
}

Integrating with Journey

After configuring the integration, you can use HCL CDP Journey to create personalized customer experiences based on Discover events. For more information about Journey Integration, refer Journey Integration.