# Browsers and systems

On every plan, the dashboard breaks visits and installs down by browser, operating system, device and install path, with each browser’s and system’s logo. The values are coarse families, never full version strings.

## Visits

Each visit records a browser family and major version, an OS family and a device type, worked out on the server from the `User-Agent` header and the low-entropy `Sec-CH-UA` client hints. The SDK adds a hint only where those hide something: Chromium’s CPU architecture, Brave (which sends Chrome’s user agent), an iPad asking for the desktop site, and the time zone and language.

| Field | Values |
| --- | --- |
| Browser | `chrome`, `safari`, `firefox`, `edge`, `brave`, `opera`, `vivaldi`, `arc`, `samsung`, `duckduckgo`, `chromium`, `other` |
| OS | `macos`, `windows`, `linux`, `ios`, `android`, `chromeos`, `other` |
| Device | `desktop`, `mobile`, `tablet` |

Servers cannot tell some Chromium browsers apart from Chrome: Arc and Vivaldi often count as Chrome, and Brave does unless the SDK saw it.

## Installs

Each install records what the [hook reports](https://clitrail.com/docs/hook#what-it-sends): the system (`macos` or `linux`), the CPU architecture, the default browser’s family and the families of the supported browsers with a profile on the machine, plus its install path. The dashboard shows installs by default browser, system and install path.

## Plans

These breakdowns are on every plan, Free included: they describe your audience, not where an install came from. The time zone and language are kept only for [reconstruction](https://clitrail.com/docs/reconstruction) on paid plans.