> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/wan-insights/how-it-works/estimating-user-counts.md).

# Estimating User Counts

WAN Insights determines the number of hourly active users as follows:

* Count the number of different source and destination IPs for network traffic on every site – on an hourly basis.
* Consider a week of hourly numbers and take their 80th percentile. This number is representative of the number of users during activity hours for the past 7 days.

You can see hourly vs weekly as follows:

* Hourly users is shown on the recommendation detail timelines
* Weekly average user counts appear on the recommendation summary cards.
* The weekly average is calculated once a day, using a rolling 7-day time window.


---

# 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.thousandeyes.com/product-documentation/wan-insights/how-it-works/estimating-user-counts.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.