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.
What this means
Mobile model name is the device model — for example a phone's marketing name — associated with a session. GA4 populates it from the device data available via the platform and the user agent, normalising where it can.
It is a diagnostic and segmentation aid: which devices are most common, and where rendering or performance problems concentrate.
Coarseness and limits
Model names are shared by huge numbers of users, so on their own they are not identifying. They also lag: brand-new models may appear as generic or unresolved until lookup data catches up, and some sessions never resolve to a specific model. Browser efforts to reduce user-agent detail further blur device data. Read it as a coarse population view and resist combining attributes to single out people.
- Coarse, widely shared device label
- Lags new releases; can be generic or blank
- Population-scale only, not for identification
How it appears in analytics and logs
A model name groups sessions by device type. Generic or blank values mean the model could not be resolved, not that the device was unusual.
Diagnostic use case
Use mobile model name to spot device-specific rendering or performance issues and to prioritise testing across common models.
What WebmasterID can help detect
WebmasterID uses device attributes only at population scale for diagnostics, never to fingerprint or single out individual visitors.
Common mistakes
- Combining model with other fields to single out users.
- Treating generic model values as data errors.
- Assuming the newest devices resolve immediately.
Privacy and accuracy notes
Model name is shared by many users and is not an identifier. Using it with other attributes to single out individuals would undermine privacy and is discouraged.
Related pages
- Device model dimension
The device model dimension reports the specific device a visit came from. On the web it is inferred from the user-agent string or client hints; in apps the SDK reads it directly. This page explains the derivation, why web models are deliberately coarse for privacy, and how app data is more precise.
- 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.
- User agent entropy and privacy
The user-agent string packs many details — browser, version, OS, device — whose combination adds entropy that contributes to browser fingerprinting. To reduce passive tracking, browsers freeze and reduce the user agent and move high-entropy detail behind explicitly requested Client Hints. Coarse use stays privacy-safe; aggregating detail to identify users does not.
- Website observability
Device-segmented performance 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.