Events enrichment
Last updated
Last updated
Enrich incoming events in real-time before to send it to destinations.
Enrichment could come from the Product catalog, a Custom external API, Weather database (coming soon) or any Custom data store.
You can import the full product catalog, as a result all details about products will be stored in our platform.
Click here to learn how to import the product catalog
When you are collecting events with products properties, you can send only the product_id, and we will be able to enrich incoming events with more product properties coming from the stored product catalog (weight, materials, color...) and send it to the destination(s).
Select the event you want to enrich first.
Select the property that will be used as matching key, meaning how to do a link between the incoming event and the stored product catalog? Most of the time, the link will be the product_id. This property should be common between the one in the event and the one in the stored product catalog.
Select properties you want to add in the incoming event from the product catalog.
You can define here where properties coming from the product catalog will be added in incoming events (in the payload). By default, it is at the same level as the matching key. It could also be at the root of the event or custom (enter the position).
Enrich events with data coming from any API.
For example, enrich a purchase event by adding properties from an external database. Via API, send a request with the matching key (an ID for example) and the API returns the desired data which will be integrated then into the purchase event.
Select to which sources and events the enrichment will be applied.
Configure the API (Method, URL, Body, Header)
Select which properties from the API do you want to integrate into selected events.
Coming soon
You can currently manage it manually via Enrichment from external API, but a plug&play version is in progress.
Enrich events from previously stored events. It allows you to store selected event and properties and use them later to enrich events, providing a more complete set of data for your marketing and analysis needs.
Selective Storage: Choose specific properties of an event to store after the event is cleaned. This ensures only relevant and clean data is stored.
Storage Duration: By default, properties are stored for 1 day.
Matching Key: Define a unique key to match events over time. This key helps link related events, allowing the properties of past events to be used in future ones.
Property Injection: Automatically inject properties from past stored events into more recent events. This creates a comprehensive dataset for each significant event in the customer journey.
Imagine that a customer adds a product to their cart, generating an add_to_cart event. A few hours later, the same customer completes the purchase, generating a purchase event. With the Event Enrichment feature, you can enrich the purchase event in realtime with properties from the earlier add_to_cart event, before the event is sent to your destinations.
Access Settings: Go to the Data Governance -> Storage settings.
Manage Storage Settings: Click on "New Storage" to create a new Data store.
Define Properties to be stored:
Select Consent Category: Ensure compliance with data privacy regulations.
Choose Sources and Environment
Select Event and Properties: Choose which events you want to store and which properties. If no properties are specified, the entire event will be stored.
Set Matching Key: This unique key have to be present both on the event to be enriched and the event to store.
Retention Period: The period until when the store events are deleted (maximum 30 days allowed).
Create an enrichment: In the Event Enrichment section, choose the option Custom Data Store
Define Enrichment:
Name: Name your enrichment rule.
Select Sources and Environment
Select the Storage you want to use for this enrichment
Choose Event: Select the event you want to enrich.
Select Properties: Define which properties from the stored event should be injected into the new event. The storage do not replace or override the value of an existing property. The storage will create new properties.
Review Settings: Ensure all settings are correctly configured.
Save: Save the new enrichment settings.
Administrators Only: This feature is accessible only to users with Administrator privileges. Custom profiles can be created to grant specific access to other users.
Complete Data Sets: Enriching events ensures that all relevant data is available for analysis and marketing actions.
Enhanced Customer Insights: Gain a more detailed understanding of customer behavior by linking related events over time.
