Join ID in the customer data. For example, if the primary key, such as Product ID, is of string type, it can only be mapped to a Join ID of either string type or a list of strings. Note that if there is more than one attribute of a customer that needs to be enriched with this NCE data source, then you can include them by editing the enricher of the relevant NCE data source. To know more about how to configure this enricher, refer to Configuring the Join Key Enricher.
How to Identify the Join ID and Primary Key
You can select a user attribute from categories such as ID, User Traits, Product, Event, or Campaign as the Join Key (Join ID). To understand how to identify the Join ID in customer data and the Primary Key in non-customer data, consider the following example datasets:Customer Dataset (CE)
Non-Customer Entity Dataset (NCE)
To merge the two datasets and enricher the user profiles, use the common attribute between them. In this case, the CRM ID from the Customer Dataset serves as the Join ID, while the same column in the Non-Customer Dataset acts as the Primary Key.
Below is the resulting enriched user profile: