Platform device category dimension
The platform device category dimension combines the platform a session ran on — web, iOS, or Android — with its device category, such as mobile, tablet, or desktop. GA4 derives the pair from the data stream and device signals. It is more specific than device category alone, letting you separate, for example, web-on-mobile from an Android app; reading either half in isolation can hide where behaviour actually differs.
What this means
Platform device category answers two questions at once: what platform served the session (web, iOS app, Android app) and what kind of device it ran on (mobile, tablet, desktop). GA4 builds it from the data stream's platform and the device signals on the hit.
The combined view is sharper than device category alone — mobile web and an Android app are both 'mobile' by form factor but very different experiences.
Why the pair matters
Reading platform or device category separately can mask real differences: an issue affecting only the iOS app, or only desktop web, is easy to miss when the halves are collapsed. The combined dimension also surfaces anomalies — a desktop form factor on an app platform usually means stream mis-tagging. Use it to target fixes precisely, while remembering these are coarse, non-identifying attributes.
- Pairs platform with form factor
- Sharper than device category alone
- Odd combinations flag stream mis-tagging
How it appears in analytics and logs
A value pairs platform with form factor. A surprising combination — desktop on an app platform — can signal mis-tagged streams or unusual environments.
Diagnostic use case
Use platform/device category to compare experiences across the platform-and-form-factor combinations that matter, like app versus mobile web.
What WebmasterID can help detect
WebmasterID segments by platform and form factor at population scale for diagnostics, keeping device data away from individual identification.
Common mistakes
- Reading platform and form factor only in isolation.
- Ignoring impossible combinations that signal mis-tagging.
- Using the pair to try to identify individuals.
Privacy and accuracy notes
Platform and device category are coarse, widely shared attributes, not identifiers. They are unsuitable for singling out individual users.
Related pages
- 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.
- Platform dimension: web, Android, or iOS
Platform is the dimension that records the broad surface a hit came from: web, Android, or iOS. In GA4 it is determined by the data stream the event arrived through, since a property can combine app and web streams. It is coarser than the operating-system dimension and is the right axis for comparing app versus web behaviour — but mixing app-only and web-only metrics across platforms is a frequent reporting error.
- Mobile model name dimension
The mobile model name dimension reports the marketing or model name of the device a session ran on. GA4 derives it from the device information the platform and user agent expose. It is useful for device-compatibility and performance segmentation, but model names are coarse and shared by many users, lag behind new releases, and can fall back to generic values — so it is a population-level dimension, never a way to identify individuals.
- Website observability
Compare experiences by platform and form factor.
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.