> For the complete documentation index, see [llms.txt](https://hitsubscribe.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hitsubscribe.gitbook.io/home/osiris/traffic-analytics/normalized-tag-performance.md).
# Normalized Tag Performance
This report is a handy way to see what parts of your site or campaigns (i.e. tags) have performed the best, normalized for the number of URLs. For instance, let's say that you have 100 "blog" URLs and only 10 "news" URLs. Since more URLs typically means more traffic, it's hard to say if, pound-for-pound, blog is actually outperforming news.
This view corrects for that. It divides the tag by the number of URLs in it to normalize the performance on a per-URL basis. And it does this across filterable date range and media.
You can filter the report by
1. Tag(s)
2. Session media
3. Date range
And this report is generally good for answering the question "which groups of URLs perform the best in which channels?"
And here is a video walk-through of the report.
{% embed url="" %}
---
# 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://hitsubscribe.gitbook.io/home/osiris/traffic-analytics/normalized-tag-performance.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.