> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/app-tracking-setup/data-enrichment.md).

# Data Enrichment

The JENTIS App SDK empowers you to enhance your server-side tracking with data enrichment services. To use data enrichment within the App SDK environment, the only requirement is to track the properties required by the data enrichment plugin's arguments.

For example, if you have product enrichment configured, you must pass the `product_id` property to your App SDK Data Layer. This allows our enrichment plugin to enrich the dependent variables in our data processing environment.

With every incoming tracking packet, our service checks your current configuration. If a data enrichment variable is included, it inspects the tracking packet for the required argument property. Once found, it automatically enriches the dependent variables. No further setup is required on your end to use enrichment services in the App SDK environment.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jentis.com/app-tracking-setup/data-enrichment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.