> For the complete documentation index, see [llms.txt](https://docs.emaillabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emaillabs.io/en/analytics-panel/reports/status-per-tag.md).
# Status Per Tag
The 'Statuses per Tag' function allows you to select any tag and compare individual statuses. We can, for example, select 'order confirmation' or 'invoices' and see how many messages have been delivered, opened, clicked, or bounced.
\
This is particularly important for marketing campaigns and automation, whereby you can see the effects of that communication over time by tagging a particular type of message, e.g., an abandoned shopping cart. Similarly, for transactional emails, you can tag a particular type of email, e.g., invoices for invoice emails, and track their status.
⬅️ **Detailed instructions for each panel section under the "Status per tag" tab can be found in the drop-down menu on the left.**
***
You can find the described tags and message statuses in the following tabs:
✅ Tags
Automated tagging of a group of emails, which means labeling them with the appropriate tags.
---
# 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.emaillabs.io/en/analytics-panel/reports/status-per-tag.md?ask=&goal=
```
`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.