Enrichers in Destination Mapping

1. Concatenate – Allows you to add a prefix or suffix to a Catalogue field.
2. Timestamp – Allows you to add a timestamp to indicate the upload time of a data record.
3. Custom Enricher – Allows you to apply custom transformations such as hashing, formatting, value mapping and more to modify field values.
4. JavaScript – Allows you to apply a custom JavaScript function to a field, including reshaping or filtering a list of objects before sending it to a destination.

​

1. Concatenation Enricher

​

Use Cases

• Add a prefix to distinguish fields sent to a destination platform. For example, if you are sending customer purchase history to an analytics tool, you can add the prefix retail_to fields such as retail_total_spent to avoid naming conflicts.
• Append a suffix to indicate transformed data. For example, if you are converting a timestamp to a different timezone, you can append _converted to indicate the transformation (e.g., event_time_converted).
• Combine multiple fields into a single string for compatibility with destination platform requirements. For example, if you are exporting customer full names to a platform that only supports a single name field, you can concatenate first_name  and last_name into full_name.

​

Using Concatenation Enricher in Destination Mapping

1

Click the Add Enricher icon next to the desired Catalogue field.

2

In the Select Your Enricher Type window, choose Concatenation.

3

Click + to add the desired text as a prefix or suffix, then press Enter.

• Drag and drop the added text to reorder it as a prefix or suffix as needed.
• You can add multiple prefixes or suffixes.

4

Click Save to complete the configuration.

​

2. Timestamp Enricher

​

Use Cases

• Enable time-sensitive processing by external platforms – If a marketing automation tool needs to trigger campaigns based on the latest user interactions, adding a timestamp ensures that actions are taken on the most recent data.
• Maintain audit logs for compliance and reporting – If you need to track when user data is sent to an external platform for regulatory compliance, adding a timestamp provides a clear audit trail for reporting and verification.
• Optimise real-time bidding (RTB) in advertising platforms – If you are sending audience segments to an advertising platform for RTB, adding a timestamp ensures that bids are placed based on the most up-to-date audience data.
• Improve attribution modeling in analytics platforms – If an analytics tool is calculating conversion paths, adding a timestamp helps accurately attribute actions to the correct time period, improving the accuracy of performance reports.
• Synchronise data processing in ETL pipelines – If a destination platform processes data in batches, adding a timestamp ensures that records are correctly sequenced and processed in the intended order.

​

Using Timestamp Enricher in Destination Mapping

1

Navigate to the Destination Mapping screen.

2

Click the Add Enricher icon next to the desired Catalogue field.

3

In the Select Your Enricher Type window, choose Timestamp.

4

Select the preferred time format from the available options.

5

Click Save to apply the timestamp.

​

3. Custom Enricher

​

Build Your Own Directive (BYOD)

1. Identify the transformation requirement– Determine the business need, such as standardising text, applying encryption, or extracting specific data.
2. Select the appropriate directive– Refer to the list of commonly used CDAP Wrangler Directives and Apache Commons JEXL expression to choose the correct functions as required for your use case.
3. Customise the directive for Zeotap CDP– Let’s say you want to use the cut-character directive to extract the first three characters of a field value. In this case, the format of the directive is as below.

4. To use this directive in the Destination Mapping screen in Zeotap CDP:
   • Replace <source> with the Zeotap Catalogue’s Database Name (refer to the image below).
   • Replace <destination> with the Custom Destination Field Name (refer to the image below).
   • Define the <type> as character.
   • Specify the <range|indexes> to extract the required substring.
   The updated directive is, cut-character <Zeotap Catalogue’s DB Name> <Custom Destination Field Name> character 1-3

5. Apply the required prefix– To align with Zeotap CDP’s conventions, add the custom_ prefix to <Custom Destination Field Name>.

6. Use the the final directive in the Expression field as shown below and click Save. This extracts the first three characters of a user source country value.

7. Similarly, you can build your own custom directive specific to your use case.

​

Common Use Cases for Custom Enrichers

• Use Case 1: Calculate and Send the Count
• Use Case 2: Hash User Data for External Analytics Platforms
• Use Case 3: Trim Long Names to Meet Destination Platform Limits (String Subsetting)
• Use Case 4: Normalise Subscription Status for Destination Compatibility

​

Before you Begin

• Replace <source> with the Zeotap Catalogue’s Database Name (refer to the image below).
• Replace <destination> with the Custom Destination Field Name (refer to the image below).

​

Use Case 1: Calculate and Send the Count

• Replace <Custom Destination Field Name> with the corresponding field name in the destination platform.
• Replace <Zeotap Catalogue’s DB Name> with the attribute name in the Zeotap database.

​

Use Case 2: Hash User Data for External Analytics Platforms

• Replace <Custom Destination Field Name> with the corresponding field name in the destination platform.
• Replace <Zeotap Catalogue’s DB Name> with the attribute name in the Zeotap database.

​

Use Case 3: Trim Long Names to Meet Destination Platform Limits (String Subsetting)

• Replace <Custom Destination Field Name> with the corresponding field name in the destination platform.
• Replace <Zeotap Catalogue’s DB Name> with the attribute name in the Zeotap database.

​

Use Case 4: Normalise Subscription Status for Destination Compatibility

• Replace <Custom Destination Field Name> with the corresponding field name in the destination platform.
• Replace <Zeotap Catalogue’s DB Name> with the attribute name in the Zeotap database.

​

Using Custom Enricher in Destination Mapping

1

Navigate to the Destination Mapping screen.

2

Click the Add Enricher icon next to the desired Catalogue field.

3

In the Select Your Enricher Type window, choose Custom.

4

Enter a custom expression under Enter Custom Expression to transform a field, derive new data points, or add data to an existing dataset based on your use case.In the above example, to derive the number of purchased products, we’ve used the following custom expression:

set column custom_product_number size(a_product_list)

Here,

• set column is a standard function.
• In ``custom_product_number, product_number is the destination field name prefixed with custom_
• size(a_product_list) fetches the count of items in the a_product_list field.

5

Click Save to apply the Custom Enricher.

​

4. JavaScript Enricher

​

Use Case: Send Only Specific Objects from a List of Objects

[
  { "product_id": 539604, "replenishment_date": 1745000000000 },
  { "product_id": 539626, "replenishment_date": 1745500000000 },
  { "product_id": 700800, "replenishment_date": 1600000000000 }
]

{ "user_id": "doug1", "product_id_replenishment": "539604 | 539626" }
{ "user_id": "doug2", "product_id_replenishment": "700800" }
{ "user_id": "doug3" }

​

Using the JavaScript Enricher in Destination Mapping

1

On the Map the Fields screen, click the Add Enricher icon next to the Catalogue field that holds your list of objects.

2

In the Data Enricher window, under Choose the Enricher, select JavaScript.

3

Under Select Input Parameters, choose the field(s) passed to your function. In this example, select the list-of-objects field (replenishment_model).

4

Under Select Sub-Properties, choose the nested fields you reference inside the function — here, product_id and replenishment_date.

5

In JavaScript Code, define a function named tx that receives the selected parameters and returns the transformed value:

function tx(replenishment_model) {

  // Guard: return null if input is missing or not an array
  if (!replenishment_model || !Array.isArray(replenishment_model)) return null;

  // Calculate the current timestamp and 30-day lookback window in epoch millis
  const now = Date.now();
  const thirtyDaysAgo = now - 30 * 24 * 60 * 60 * 1000;

  const filteredIds = replenishment_model
    .filter(item => {

      // Skip if product_id is null or undefined
      if (item.product_id == null) return false;

      // Skip if replenishment_date is null or undefined
      if (item.replenishment_date == null) return false;

      // Convert epoch millis to Date object for comparison
      const replenishDate = new Date(item.replenishment_date);

      // Skip if replenishment_date is not a valid date
      if (isNaN(replenishDate)) return false;

      // Keep only items whose replenishment_date falls within the last 30 days
      return replenishDate >= thirtyDaysAgo && replenishDate <= now;
    })

    // Extract product_id and cast to string
    .map(item => String(item.product_id));

  // Return pipe-separated product IDs, or null if no products qualify
  return filteredIds.length > 0 ? filteredIds.join(" | ") : null;
}

6

Click Test to validate the function against sample data, then click Save to apply the enricher.

​

FAQs