> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/features/data-explorer/tracked-products.md).
# Tracked products
Manage assemblies and parts that are important to your team with **Tracked Products****.**
When a part number is tagged as `Tracked`, that part or assembly, as well as all of its children (if applicable), becomes filterable in data explorer and other Violet features.
You can indicate which items should be tracked in your Company Profile.
### Adding a Tracked Product
{% @arcade/embed flowId="Zwhv7J8syb7siQQFYnjW" url="" %}
Note, `Tracked Product` attributes will appear after the next full fetch of parts from your integration(s).
#### Finding Tracked Products
In the Data Explorer or in a Multisource Report, filter on the `Tracked Part` attribute to locate the tracked part number across integrations.
Filter on the `Tracked Product Ancestors` attribute to locate all child parts of the selected Tracked Product(s); in the source integration as well as in any other integration.
---
# 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.violetlabs.com/features/data-explorer/tracked-products.md?ask=&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.
