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

# Enrichment Insights

Enrichment insights allow you to keep track of the enrichment of your products, categories,  variants or variantgroups based on criteria chosen by you.

You can add or update enrichment measurements through [Product model setup](/pim3/reference/product-model-setup.md) > [Enrichment Insights](/pim3/reference/product-model-setup/enrichment-insights.md).

### View enrichment measurements

Enrichment measurements are shown directly in the enrichment insights page.

### Find enrichment measurement

1. Click column header for Alias, Label or Entity type
2. Type value to search for

### Add a new enrichment measurement

1. Click "Add enrichment measurement"
2. Set Entity type, Alias and Label along with additional [details](/pim3/reference/product-model-setup/enrichment-insights/enrichment-insight-details.md)
3. Click "Create enrichment insight setup"

### Edit enrichment measurement

1. Click "Edit"-icon
2. Modify enrichment measurement [details](/pim3/reference/product-model-setup/enrichment-insights/enrichment-insight-details.md)
3. Setup [Insights](/pim3/reference/product-model-setup/enrichment-insights/insights-setup.md)
4. Click "Save enrichment insight setup"

### Delete enrichment measurement

1. Click "Delete"-icon
2. Confirm deletion


---

# 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.struct.com/pim3/reference/product-model-setup/enrichment-insights.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.