Understand NCE With An Example
The following sample datasets of customer data and non-customer data illustrate the concept of joining for better understanding:Customer Dataset (CE)
| CRM ID (Join ID) | Name | Phone Number | |
|---|---|---|---|
| 12345 | Jane Doe | jane.doe@email.com | 555-1234 |
| 67890 | John Smith | john.smith@email.com | 555-5678 |
Non-Customer Entity Dataset (NCE)
| CRM ID (Primary Key) | Order ID | Order Date | Total Amount |
|---|---|---|---|
| 12345 | ORD001 | 2024-01-01 | $250 |
| 67890 | ORD002 | 2024-01-15 | $400 |
Connect the Datasets Using the Join Key
In the above scenario, ensure that you map the CRM ID (common attribute) from both the Customer Dataset (CE) and Non-Customer Entity Dataset (NCE) to the respective Zeotap Catalogue fields.
In the mapping screen of the NCE source, under the Join ID section, perform the following steps:
- Select Add Enricher and choose Join Key Enricher as the enrichment type.
- Under Select User Attributes to Enrich, choose the crmid from your Catalogue, which is your Join ID from the customer data. To learn how to select the Join ID from the customer data, refer here.
- Use the Enable Composite Key toggle to select an additional column from the NCE dataset along with the Primary Key (of your NCE dataset) to enrich the customer profile with the non-customer data. Use this option to append data to a user profile instead of upserting it with a new value. For more information about how the Composite Key works, refer here.
Result of Mapping
After mapping:- Jane Doe’s profile (from the CE dataset) links to her order details (ORD001, 2024-01-01, $250) in the NCE dataset.
- John Smith’s profile (from the CE dataset) links to his order details (ORD002, 2024-01-15, $400) in the NCE dataset.
| CRM ID | Name | Phone Number | Order ID | Order Date | Total Amount | |
|---|---|---|---|---|---|---|
| 12345 | Jane Doe | jane.doe@email.com | 555-1234 | ORD001 | 2024-01-01 | $250 |
| 67890 | John Smith | john.smith@email.com | 555-5678 | ORD002 | 2024-01-15 | $400 |
