> 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/ai-traffic-over-time.md).

# AI Traffic Over Time

This popular report shows the monthly, weekly, and daily traffic to your site where that traffic has a session source of a known answer engine site as evaluated by a regex in the query matching popular ones.  So, for instance in the screenshot below for the community [makemeaprogrammer.com site](https://makemeaprogrammer.com/),  you can see traffic coming from ChatGPT, Perplexity, and You.com.  

You can filter this report by:

1. Date range
2. Source(s) you're interested in

The dots in the weekly view are a curious artifact of Looker not fully understanding the concept of "week" for small data sets that we'll work out eventually.

<figure><img src="/files/lavDsxpYvHGPQkpJl8zN" alt=""><figcaption></figcaption></figure>


---

# 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/ai-traffic-over-time.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.