Browser dimension and its limits
The browser dimension records which browser a visit used — Chrome, Safari, Firefox, Edge, and so on. It is parsed from the user-agent string (and increasingly User-Agent Client Hints), so it is a classification, not a fact reported by the device. UA freezing, Chromium-based browsers sharing tokens, and in-app webviews are why this dimension is fuzzier than it looks.
What this means
The browser dimension is assigned by parsing the user-agent string into a known browser family and version. Modern browsers are reducing UA detail under User-Agent Reduction and exposing precise versions only through high-entropy Client Hints, so parsers increasingly read sec-ch-ua instead of the legacy string.
Why the limits matter
Many browsers are Chromium-based and carry a 'Chrome' token, so smaller forks under-report. In-app webviews (a link opened inside a social app) often look like Safari or Chrome rather than the host app. Frozen UA versions mean the reported version may be a fixed value, not the real build. Read browser as a compatibility signal, not a precise census.
- Parsed from user agent / Client Hints
- Chromium forks frequently report as Chrome
- In-app webviews mask the real browser
How it appears in analytics and logs
A browser value is the parser's reading of the user agent. A surprising browser mix often reflects a parsing quirk (a Chromium fork reported as Chrome, a webview reported as Safari) rather than a real audience change.
Diagnostic use case
Use browser to guide compatibility and QA priorities, treating it as a UA-derived estimate and expecting Chromium forks and webviews to under-report as plain Chrome.
What WebmasterID can help detect
WebmasterID derives browser family from the user agent privacy-safely and categorises bot user agents separately, so automated traffic does not pollute the browser breakdown.
Common mistakes
- Treating the browser version as exact when UA reduction freezes it.
- Assuming Chromium forks show under their own name.
- Ignoring that in-app webviews distort the breakdown.
Privacy and accuracy notes
Browser is read from the user agent, a low-entropy signal, not from fingerprinting. WebmasterID classifies it without reading high-entropy device hints.
Related pages
- Operating system dimension
The operating system dimension records the platform a visit ran on: Windows, macOS, iOS, Android, Linux, ChromeOS. It is parsed from the user-agent string (and the sec-ch-ua-platform Client Hint), making it a classification rather than a reported fact. Frozen OS versions, iPadOS reporting as macOS, and webviews are the usual reasons it does not perfectly match reality.
- Device category: desktop, mobile, tablet
Device category groups visits into desktop, mobile, or tablet. It is derived from the user-agent string (increasingly, User-Agent Client Hints), so it is a classification, not a hardware fact. Tablets, desktop-mode mobile browsers, and foldables blur the boundaries, and the user agent can be spoofed.
- User-Agent Client Hints
User-Agent Client Hints are HTTP headers (the Sec-CH-UA family) that let a site request specific browser, platform, and version detail rather than reading it all from one passive string. They underpin UA reduction: the raw user agent is shrinking, and finer detail moves to opt-in hints. This page explains the model.
- Privacy-first analytics
Browser classification without fingerprinting.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.