> For the complete documentation index, see [llms.txt](https://docs.tactyc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tactyc.io/portfolio-management/investments-table/using-deal-tags.md).
# Using Deal Tags
Deal tags enable you to evaluate performance metrics for sub-sections of your entire fund's portfolio.
Deal tags are a quick and easy way to label deals with custom tags relevant for your fund. Your fund's entire portfolio can then be filtered for specific tags.
## **Adding a Deal Tag**
* Open an existing investment and click on **Edit Information**
* Under **Deal Tags,** you can either select a tag from the pre-defined list or create your own by typing a new tag name
* You can add multiple tags to each deal
## **Filtering on Tags**
On the main **Investments Table,**
* Expose the **Tags** column using the **Columns** button (if Tags are not already shown on your investments table)
* Filter on specific tags to only show matching companies within each tag
## **Tag Performance**
Performance by Tags are also available under **Portfolio Insights.**
---
# 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.tactyc.io/portfolio-management/investments-table/using-deal-tags.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.
