Skip to main content
Non-Customer Entity Data refers to data that is not directly tied to a user but to an attribute associated with the user. The most common forms of Non-Customer Entity Data are product cataloguesorder data, feed datacampaign dataaccount data and so on. Zeotap allows you to further enrich the information available on a user’s profile using Non-Customer Entity Data. To do this, you can use a Join ID or common key to connect the user’s data with the non-customer data set. You can also use non-customer data to handle scenarios where there is a one-to-many relationship. For example, consider a scenario where a single UCID (Unique Customer Identifier) is associated with multiple subscription plans, each having varying propensity scores for customer conversion. In this case, the UCID maintains a one-to-many relationship with multiple subscription plans and their corresponding propensity scores. Therefore, setting up a Non-Customer Entity source can be an ideal solution to meet such requirements. Note that Zeotap performs an upsert operation on the Non-Customer Entity data, for every record received from a Non-Customer Entity data source. For example, let’s say, a UCID is associated with profile attributes such as agegenderlocationdevice information and more. Consequently, whenever a new record is received, the existing information is updated with the new data and not appended.
NoteIf multiple attributes contribute to creating a unique record, then we recommend that you create a composite key before ingesting the data as Non-Customer Entity Data.

Examples of NCE Data

  • Product data: Provides details about items available for purchase such as, Product name: Ultra HD TV, Price: $999, Category: Electronics, Stock status: In stock, Description: 4K resolution with HDR.
  • Order data: Includes information about transactions or purchases such as Order ID: 12345, Purchase date: 2024-11-01, Payment status: Paid, Total amount: $250.
  • Feed data: Represents updates from external sources or systems, such as real-time pricing or inventory updates. For example, Feed type: Inventory update, Product ID: 67890, Current stock: 30.
  • Campaign data: Contains details of marketing or promotional activities such as, Campaign ID: CMP001, Start date: 2024-11-15, End date: 2024-12-15, Budget: $10,000.
  • Account data: Relates to organisational or account-level information like Account ID: ACC001, Account type: Business, Account owner: John Doe, Region: North America.

How to use NCE?

Why do we need NCE?

Understand One-to-Many Relationship in NCE

How to use the Composite Key in NCE?

Understand Join Key Enricher and how to configure it

Create an NCE source for the source types: Flat Files, Server to Server, CRM Data, and Data Warehouse

How to map NCE data in the Zeotap Catalogue?

How to create an NCE attribute in Zeotap Catalogue?

Last modified on March 30, 2026