> 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.md).

# Traffic Analytics

Here is a list of the different reports in your dashboard.

* [Site Visits Over Time](/home/osiris/traffic-analytics/site-visits-over-time.md) (stock): shows monthly, weekly, daily traffic to your site, filterable by date range and medium.
* [Visits to URLs](/home/osiris/traffic-analytics/visits-to-urls.md) (stock): shows total visits by URL to URLs on your site, filterable by date range and medium.
* [Visits to Tags Over Time](/home/osiris/traffic-analytics/visits-to-tags-over-time.md) (stock): shows monthly, weekly, daily traffic to your site per *tag*.  A tag can be applied to one or more URLs on your site to group them.  For instance, you might tag everything on your blog as "Blog" or you might take all of your competitor comparison pages as "Competitor Comparison."  You can see the combined traffic to tagged groups of URLs, filterable by date range, medium, and of course tag(s).
* [Visits to URL Over Time](/home/osiris/traffic-analytics/visits-to-url-over-time.md) (stock): shows monthly, weekly, daily traffic to one or more individual URLs with separate lines for traffic per medium.  In other words, you can pick a URL and see how it has done in one or more media over time.  Filterable by URL(s), medium, and date range.
* [Normalized Tag Performance](/home/osiris/traffic-analytics/normalized-tag-performance.md): use this view to see how your tags perform, per-URL.  The default view shows how they all do together, which obviously heavily favors tags with more URLs.  This view shows you the tag's performance, on average, *per-URL*.  Filterable by tags, of course, and date range and medium.
* [User Metrics over Time](/home/osiris/traffic-analytics/user-metrics-over-time.md): this view shows holistic site metrics monthly, daily, and weekly, including new users, total users, and sessions.  Filterable by date range and medium.
* [New Users Over Time](/home/osiris/traffic-analytics/new-users-over-time.md): a simpler version of the above, just showing new users with no distractions.  Filterable by date range and medium.
* [AI Traffic Over Time](/home/osiris/traffic-analytics/ai-traffic-over-time.md): this view shows monthly, weekly, daily referral traffic from known AI answer engine sources, broken out by source.  Filterable by date range and source.
* [AI Percentage Over Time](/home/osiris/traffic-analytics/ai-percentage-over-time.md): shows the percentage of traffic to your site's total traffic attributable to AI sources over time.&#x20;
* [AI Traffic to URLs](/home/osiris/traffic-analytics/ai-traffic-to-urls.md): this is similar to the Visits to URLs view, but filtered by visits with views with an AI referrer of some kind.  Filterable by date range and medium.


---

# 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.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.
