Data Enrichment

Data Enrichment Variables

Data Enrichment Variables in JENTIS are used to gather external data from third-party systems (APIs) and make that data available for tracking, transformation, or targeting purposes within the JENTIS Environment.

They allow you to enhance your data quality and completeness by integrating additional information during the tracking process.


Purpose

Use Data Enrichment Variables to:

  • Fetch additional information from external APIs (e.g., CRM, product catalogs, weather services, or geo IP providers)

  • Integrate external attributes (e.g., loyalty status, customer segment, product metadata)

  • Enrich tracking events with real-time data not present in the browser or JENTIS environment


Availability

Platform
Supported

Client-Side

✅ Yes

Server-Side

✅ Yes

Data Enrichment Variables can be used on both client and server side, depending on the use case and data source.


How It Works

  1. An Enrichment Plugin is Created

    • The plugin acts as the connector to the third-party system.

    • It defines the structure and logic for retrieving data.

    • It is registered and maintained in your JENTIS setup.

  2. Variables Are Defined via the Plugin

    • These variables become available in your JENTIS Tag Manager.

    • They can be referenced like any other variable.

    • The plugin determines how and when data is fetched (e.g., on page load, form submission, server event).

  3. Enriched Data Becomes Available

    • You can use the returned values in triggers, tags, or other variables.

    • Enrichment values are injected at runtime and treated as native values inside your setup.


Requirements

To use Data Enrichment Variables, you must:

  • Have a working Enrichment Plugin integrated with your JENTIS instance.

  • Define the external data logic within the plugin (e.g., API call, auth, response mapping).

  • Assign the plugin to the appropriate client-side or server-side tool in the JENTIS Tag Manager.


Use Cases

  • CRM Integration: Enrich user sessions with customer profile data (e.g., loyalty tier, region)

  • Geo Data: Retrieve city, ISP, or timezone based on IP

  • Product Catalog Enrichment: Add category or margin info to product views

  • Weather Data: Inject temperature or conditions for behavioral analytics

  • A/B Testing Info: Fetch experiment assignment from a testing platform


Notes

  • Performance-sensitive data should be handled server-side if possible.

  • Enrichment logic should be stateless and fast, as it runs inline with the tracking execution.

  • API responses must be structured and reliable to avoid blocking or delay.


Summary

Data Enrichment Variables allow you to integrate external intelligence into your JENTIS tracking pipeline—unlocking real-time, dynamic, and context-aware insights. Powered by plugins, they provide a flexible framework to bring third-party data into both client and server side logic without compromising performance or control.

Last updated

Was this helpful?