> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/settings/data-management.md).

# Data Management

- [Traffic Sources](https://docs.fusion.vectra.ai/settings/data-management/traffic-sources.md)
- [Context Integrations](https://docs.fusion.vectra.ai/settings/data-management/context-integrations.md)
- [Context Labels](https://docs.fusion.vectra.ai/settings/data-management/context-labels.md)
- [Flow Tags](https://docs.fusion.vectra.ai/settings/data-management/flow-tags.md): Flow tags are labels that are applied to flow data, based on user-defined criteria and are activated as Netography ingests the data into the platform. The required fields are the Rule Name for specify
- [Traffic Classification](https://docs.fusion.vectra.ai/settings/data-management/traffic-classifications.md): Traffic Classifications define the internal IP address blocks and domain names for your organization. This is an important configuration step for Fusion, as understanding internal vs external communic


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fusion.vectra.ai/settings/data-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.