> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vertracloud.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Web Analytics Traffic: Breakdowns and Cross Filters

> Traffic breaks your requests down by country, route, device, browser and more. Click any value to filter every panel at once.

The Traffic sub-tab splits your requests into slices, such as where visitors are, what device they use and which pages they open, and lets you click a slice to filter the whole tab. It is available on every plan.

Same data through the API: [Application traffic](https://docs.vertracloud.app/api-reference/endpoint/apps/analytics/traffic.md).

## The breakdowns

Each panel lists the top values with their request count and share.

| Panel | What it shows |
| - | - |
| **Countries** | Where the visitor is connecting from. |
| **Routes** | The path requested, such as `/pricing` or `/api/users`. The query string is not part of the route. |
| **IP addresses** | The visitor's address. Masked until you choose to show it; see [Privacy](https://docs.vertracloud.app/web-analytics/privacy.md). |
| **Status codes** | `200`, `301`, `404`, `500` and so on. |
| **Methods** | `GET`, `POST`, and the rest. |
| **Devices** | Desktop, mobile, tablet. |
| **Operating systems and browsers** | Which ones your visitors use. |
| **Protocols** | HTTP/1.1, HTTP/2 or HTTP/3. |
| **Referrers** | The site that sent the visitor. **Direct** means no referrer: typed address, bookmark or an app that hides it. |
| **Networks** | The internet provider or company network the visitor is on. |
| **Content types** | HTML, JSON, images, scripts and so on. |
| **Cache** | Whether the edge answered from its cache or had to ask your app. |
| **Bots** | Search engines and other known automated visitors, by category. |
| **Data centers** | Which edge location answered the request. |

## Cross filters

Click any value and it becomes a filter chip at the top. Every panel, chart and number in the tab narrows to the requests that match, so you can ask questions in a chain:

1. Click **Brazil** in Countries.
2. Click `/checkout` in Routes.
3. Look at Status codes: are Brazilian visitors to the checkout getting errors?

Filters add up (country **and** route). Remove one by clicking its chip. The filters stay when you switch to Errors or Performance, so you can follow one slice through all the views. Requests applies the same filters to its table.

> [!TIP]
>
> To separate human visitors from automated ones, filter by a **Bots** category, or look at Devices and Referrers: scanners usually show up as unknown devices with no referrer.

## Reading the numbers

* Shares are of the requests in the selected period and filters, not of all time.
* Panels show the top values only. A very long tail of rare values is grouped out of sight.
* Counts are estimates when traffic is high; see [Sampling and delay](https://docs.vertracloud.app/web-analytics/sampling-and-delay.md).

Next: [Errors](https://docs.vertracloud.app/web-analytics/errors.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.