> For the complete documentation index, see [llms.txt](https://docs.keeping.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeping.com/help/reporting-and-analytics/advanced-reports/tag-intersection-analytics.md).

# Tag intersection analytics

#### What are Tag Intersection Analytics?

The Tags analytics page normally shows one row per tag. Tag Intersection lets you go further -- select 2-4 tags and see a combined row showing stats for tickets that match **all** of those tags.

This is useful for answering questions like "How many tickets were tagged both 'Billing' AND 'Urgent' last month?" or "What's the average response time for tickets tagged 'VIP' AND 'Bug Report'?"

#### How to Use Tag Intersection

1. Go to **Analytics > Tags**
2. Above the tags table, you'll see a **tag selector dropdown**
3. Select **2-4 tags** using the checkboxes
4. Click **Add Row**
5. A new row will appear at the bottom of the table showing combined stats for tickets matching all selected tags

#### Understanding the Results

* **New** and **Closed** columns show counts for tickets that have all of the selected tags
* **Response Time** and **Resolution Time** show averages for those tickets
* **Open** and **Pending** columns show N/A (these can't be computed for tag combinations)
* Intersection rows are pinned at the bottom of the table and won't move when you sort

#### Tips

* You can add up to **5 intersection rows** at a time
* Intersection rows are included when you **export to CSV**
* Rows are **ephemeral** -- they'll disappear if you navigate away from the page
* The tag selector resets after each row is added, so you can quickly build multiple combinations


---

# 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.keeping.com/help/reporting-and-analytics/advanced-reports/tag-intersection-analytics.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.