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.
What this means
Device category is a bucket — desktop, mobile, or tablet — assigned by parsing the user-agent string. Modern browsers are shrinking the UA and moving detail into User-Agent Client Hints, so parsers increasingly read those instead.
Why the line is fuzzy
iPadOS reports a desktop-class UA; some mobile browsers offer 'desktop site'; foldables and large phones blur tablet vs mobile. Because the signal is the user agent, it can also be spoofed. Treat device category as a useful estimate for experience analysis, not a precise hardware census.
- Derived from user agent / Client Hints
- iPad desktop-class UA is a classic edge case
- User agent is spoofable — it is an estimate
How it appears in analytics and logs
A device category is the tool's classification of the user agent. An odd device mix can reflect a UA-parsing quirk (e.g. iPad reporting desktop) rather than a real audience shift.
Diagnostic use case
Segment by device to understand experience differences, while treating the category as a UA-derived estimate rather than ground truth.
What WebmasterID can help detect
WebmasterID derives a coarse device category from the user agent and keeps it privacy-safe — no fingerprinting, and bot user agents are categorised separately.
Common mistakes
- Treating device category as exact hardware truth.
- Ignoring the iPad/desktop-mode edge cases.
- Building fingerprinting to 'improve' it — a privacy anti-pattern.
Privacy and accuracy notes
Device category comes from the user agent, a low-entropy signal, not from device fingerprinting. WebmasterID classifies it without reading canvas, fonts, or device entropy.
Related pages
- Source / medium: the core traffic-origin dimension
Source/medium is the dimension that records where a visit came from (the source, e.g. google) and how it arrived (the medium, e.g. organic). It is derived from the referrer and UTM parameters, with rules that vary by tool. The big caveat: when neither is available, the visit lands in 'direct / (none)', which is a catch-all, not a channel.
- 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.
- Mobile vs desktop UA detection
Distinguishing mobile from desktop clients is one of the few user-agent checks still broadly reliable: mobile browsers include a Mobile token and platform markers. But user-agent reduction trims finer detail, so for form-factor decisions the modern, robust approach is the Sec-CH-UA-Mobile Client Hint and responsive design rather than deep UA parsing.
- Privacy-first analytics
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.