Skip to main content
Zeotap CDP allows you to send attributes as objects, list/array of objects, and Non-Customer data (NCE) to Destinations, enabling effective targeting. The following use case explains how and when to use these data types in Zeotap CDP for sending data to destinations.

Stock Replenishment Use Case

In this use case, we explore how Zeotap CDP can be used to send List/Array of Objects for targeting based on user data related to product replenishment.

Customer Overview

Assume that the below table represents your customer data available in Zeotap CDP, where there are four user profiles (UCID1, UCID2, UCID3, UCID4) with different product information associated with them as shown below.
UCIDAgeProduct NameReplenishment DatePropensity Score
ucid126Fitbit Charge 5 Battery Pack2/10/20240.6
ucid126Outdoor Patio Furniture Covers10/10/20240.4
ucid232Nespresso Coffee Pods (Limited Edition)11/12/20240.9
ucid232Smart Home Thermostat Filter1/12/20240.3
ucid329Wireless Earbuds15/11/20240.8
ucid329Yoga Mat with Carrying Strap25/11/20240.7
ucid434High-Speed HDMI Cable20/12/20240.5
ucid434Electric Kettle with Temperature Control5/1/20250.6

Step 1: Create an Audience and filter them by Age

Let’s say, you create an audience with condition to filter users above 30 years as shown below.
During the Activation stage, on the Mapping screen, use the drop-down against each attribute to choose the data type for your attribute or identifier and map the corresponding Catalogue fields to the Destination fields. If you select Objects or List of Objects, then you must also map the object properties below the object, as shown below. For more information about the data types supported and when to use them, refer here. In this example, Product Info is a List of Object with Product name, Replenishment Date, Propensity Score as its properties.
So, when you create this audience with condition to filter users above 30 years, only UCID 2 and UCID 4 qualify as shown below. Note that each user profile (UCID) has multiple product information associated with it.
UCIDAgeProduct NameReplenishment DatePropensity Score
ucid232Nespresso Coffee Pods (Limited Edition)11/12/20240.9
ucid232Smart Home Thermostat Filter1/12/20240.3
ucid434High-Speed HDMI Cable20/12/20240.5
ucid434Electric Kettle with Temperature Control5/1/20250.6

Step 2: Additional Filtering at Destination Level by Propensity Score

At this point, you can apply a filter on the properties of the objects to include only the required products in the user profiles. You can do this in the Destination Settings, as shown below.
In this example, the filter is added to include only products with a Propensity Score above 0.5.

Conclusion

Here, the following product information of the users UCID 2 and UCID 4 qualify for Destination upload at this stage:
  • UCID 2 with the product Nespresso Coffee Pods (Limited Edition).
  • UCID 4 with the product Electric Kettle with Temperature Control.
This approach allows you to successfully filter and specifically target only UCID 2 and UCID 4 with promotions or ads for relevant products, that is Nespresso Coffee Pods (Limited Edition) and Electric Kettle with Temperature Control respectively.

How Data is Sent to Destination

Depending on the destination platform, you can choose the data format in which the final data is sent to Destination. For example, Google Cloud Storage accepts only JSON or CSV formats. Below are the data examples in both formats. In JSON Format
JSON
[
  {
    "UCID": "ucid2",
    "Age": 32,
    "Product Name": "Nespresso Coffee Pods (Limited Edition)",
    "Replenishment Date": "11/12/2024",
    "Propensity Score": 0.9
  },
  {
    "UCID": "ucid4",
    "Age": 34,
    "Product Name": "Electric Kettle with Temperature Control",
    "Replenishment Date": "5/1/2025",
    "Propensity Score": 0.6
  }
]
In CSV Format
Code
UCID,Age,Product Name,Replenishment Date,Propensity Score
ucid2,32,Nespresso Coffee Pods (Limited Edition),11/12/2024,0.9
ucid4,34,Electric Kettle with Temperature Control,5/1/2025,0.6
Last modified on February 26, 2026