Managing Additional Properties

Configure additional metadata and manage extended table properties in HCL CDP so that downstream applications, such as the segment builder, can query non-profile relational sources, including transaction histories, conversion facts, interaction history, and identity mapping tables.

Note:
This page is available for CDM-enabled tenants.

While profile metadata manages direct customer demographic attributes, such as those in vw_profile, additional properties drive extended data sources across your Canonical Data Model (CDM). By registering these properties in HCL CDP, you map the physical database columns of underlying tables, for example id_mapping, vw_fact_conversion, fact_transactions, and vw_contacthistory, to functional attributes that business users can filter on during segmentation.

You can view configured properties on the Additional Properties page and import batch property mappings by uploading a formatted Comma-Separated Values (CSV) file.

Prerequisites

Before configuring additional properties, verify that you have:

  • Enabled the CDM tenant feature in CDP Admin UI and established the underlying database connections.
  • Provisioned the target physical tables and views in your relational database or data warehouse, for example id_mapping, vw_fact_conversion, vw_contacthistory, or fact_transactions.

Viewing Additional Properties

To view configured metadata properties across extended data sources:

  1. Sign in to HCL CDP.
  2. In the left navigation pane, expand Data Pipeline, and select Additional Properties.

The Additional Properties table displays the registered attributes and their database mapping details:

Column Description Example Values
Property The unique internal identifier for the property. old_id, customerid, campaignId, offerId
Display Name The user-friendly label displayed in the segmentation builder and dashboards. old_id, customerid, campaignId, offerId
Table Name The physical database table or view where the property resides. id_mapping, vw_fact_conversion
Source Column The physical column name in the database table mapped to this property. old_id, latest_id, customer_id, campaign_id
Data Type The technical data format of the attribute. STRING, DATETIME, NUMBER, DATE
Key Type Specifies the role of the property in identity resolution. pri (Primary), Secondary, none
Segmentable Indicates whether the attribute can be used as a filtering condition in segmentation rules, represented by a check mark or cross. Check mark (True) or cross (False)

Uploading Additional Properties via CSV

To add or update multiple properties at once, upload a CSV file containing property mappings.

Step 1: Prepare the CSV File

Create a CSV file containing the necessary column headers and attribute mappings. The following table lists the required CSV columns and expected values:

Column Header Description Allowed / Expected Values
Data Source Name The logical data source group associated with the table. Transactions, History, Conversion, Demographic
Table Name The database view or table name containing the attribute. fact_transactions, vw_contacthistory, vw_responsehistory, vw_fact_conversion
Source Column The physical column name in the source table. For example, transaction_id, cellid, customer_id
Property The internal identifier for the property. Alphanumeric characters without spaces, for example customer_email_test
Display Property Name The user-facing label shown in segmentation interfaces. For example, Customer Email, Customer Mobile, Offer Code
Data Type The data type of the source column. STRING, NUMBER, DATE, DATETIME
Key Type Key classification used for identity and joins. Primary (or pri), Secondary, none, or leave blank
Segmentable Specifies whether the property is available in the segment builder. True, False

Step 2: Upload the Properties File

  1. On the Additional Properties page, select Upload located in the upper-right corner.
  2. In the file selection dialog box, browse to and select your prepared .csv file.
  3. Confirm the upload.

Upon successful ingestion, the new properties appear in the Additional Properties grid and are instantly queryable in downstream segmentation builders.

Verifying Properties in Segmentation

To verify that the newly mapped metadata properties are available for rule definitions:

  1. In the left navigation pane, select Segments.
  2. Select Create Segment.
  3. In the criteria palette, expand the configured data source category, such as Transactions or History.
  4. Confirm that the attributes defined with Segmentable set to True appear as selectable filtering criteria.