Tracking Enrichment: How to Enrich Website Trackings Using Your Product Catalog

Tracking Enrichment allows you to supplement your website tracking with additional metadata sourced directly from your Product Catalog. This is especially useful when the tracking setup cannot capture certain values reliably—such as CategoryPath, Brand, or structured attributes—but these values exist in your product feed.

Use this guide to understand how Tracking Enrichment works, how to configure it, and how to validate that your enrichment behaves as expected.

When to Use Tracking Enrichment

Tracking Enrichment is relevant when:

Tracking data is missing attributes that already exist in your Product Catalog
Your tracking implementation cannot reliably capture certain values (e.g., CategoryPath during buy-events)
You need consistent, normalized product metadata across datasources
You work with GetPIMRelatedItems or other modules that depend on complete product context

💡Example: Buy-events often lack category information because categories may not be available in the frontend at the moment the event fires. Enriching buy-events with CategoryPath from the Product Catalog solves this issue without modifying your tracking script.

Viewing All Existing Tracking Enrichments

To see a full overview of all enrichments configured for your tracking setup:

Go to Data Management
Click Implement Tracking → Go to admin
Select Tracking enrichment from the top menu

This overview lets you quickly verify existing rules, avoid duplicates, and maintain a clean setup.

⚠️ Note: Currently, Tracking Enrichment is only available to Raptor users.

How Tracking Enrichment Works

Tracking Enrichment supplements incoming tracking events with additional metadata from the Product Catalog.

It works through three main steps:

Lookup: The system uses a chosen lookup key (e.g., ProductId, VariantId, SKU) to match your tracking event with the corresponding product in the Product Catalog.
Extraction: It retrieves the required metadata from the Product Catalog using the selected FeedIdentifier (schema name).
Enrichment: It overwrites the value of the selected tracking parameter only for the specific events defined in your condition expression.

Important Behavior to Understand

The enrichment only impacts datasources where the parameter is used
The enrichment overwrites existing values (but only for events defined by your condition)
You can verify the enrichment in the Live Tracking Stream (values typically appear within 60 minutes)

Creating a Tracking Enrichment

Follow these steps to configure new enrichment rules:

In Implement Tracking, find the parameter you want to enrich
Click Map tracking from feed to tracking
Select the FeedIdentifier (schema name used in Data Manager)
The enrichment is automatically added under Tracking enrichments

Selecting the Lookup Key

By default, ProductId is used as the match key — this works in nearly all cases.
If you need another lookup key:

Click Edit on the enrichment
Choose a different lookup key from the list

Read more about how to set up the Product Catalog for Recommendation Engine here.

🔍 Note: The lookup key must exist both in your tracking events and in your Product Catalog. A mismatch will prevent enrichment from happening.

The mapping is automatically created under the headline "Tracking enrichments"

👀 Use case: if you don't want to use the ProductId as lookup in the feed (which is used in 99% of the cases) then the Tracking enrichment is not yet completed.

Only relevant if you want another lookup than ProductId:

If you want to change the parameter that is used as lookup in the Product Catalog:

Click "Edit"

Select the needed lookup key from the list

Condition Expressions (Event Filters)

Condition expressions define which events should be enriched.

Examples

EventType == "visit"
→ Only enriches visit events
EventType == "buy"
→ Only enriches buy events
EventType == "visit" && EventType == "buy"
→ Enriches both visit and buy events

Use these expressions to target only relevant event types and prevent unintended overwrites.

Validating Your Enrichment

Once the enrichment is created:

Open Live Tracking Stream
Locate the parameter you enriched
Confirm that the enriched values differ from what the tracking script normally sends
Remember that Live Tracking Stream refreshes about every 60 minutes

This is the most reliable way to confirm that your enrichment is active and correct.

Removing a Tracking Enrichment

If an enrichment is created by mistake or no longer needed:

1. Click the enrichment icon next to the rule

2. Select Delete

This removes the enrichment without affecting the underlying parameter.

If you wrongfully create an enrichment and want to remove/delete it, then:

A screenshot of a computer

Description automatically generated

Summary

Tracking Enrichment is a powerful way to ensure high‑quality, complete, and consistent product metadata across your tracking setup. Whether you're filling gaps, normalizing data, or supporting modules like GetPIMRelatedItems, enrichment helps improve data reliability without requiring frontend development changes.

🗯️ FAQ

Q: Do Tracking Enrichments apply to all datasources?

A: No. An enrichment applies only to datasources where the enriched parameter is used. If a parameter (e.g., p23) exists in Datasource A but not in Datasource B, only Datasource A is affected.

Q: Will the enrichment overwrite existing values?

A: Yes — but only for the events defined in your condition expression.

If you see values in the column before enrichment should apply, they likely originate from other event types not covered by your rule.

Q: How can I confirm the lookup is working correctly?

A: Check the Live Tracking Stream. If the enriched value appears correctly and differs from what the frontend sends, the lookup is working.