GA4 Device Category: Desktop, Mobile, Tablet (Definition & Reports)

Q: Is smart TV a device category in GA4?

Yes, smart tv is a valid device.category value but it is rare. It appears when connected-TV browsers like Roku, Apple TV, Samsung Tizen, LG webOS load a website. Most websites see under 1 percent of traffic in this bucket; streaming and broadcaster sites see more.

Q: How do I segment by device in GA4 Explorations?

Open Explore Free Form, add Device category as a dimension, drag it into Rows, then add Sessions, Engaged sessions, and Conversions as metrics. For deeper segmentation, build a User segment where Device category exactly matches mobile and apply it as a Segment in any exploration.

Q: What is the difference between device.category and device.model?

device.category is a four-bucket form-factor dimension: desktop, mobile, tablet, smart tv. device.model is the specific hardware identifier such as iPhone, Pixel 7, SM-G998B. Use category for high-level dashboards and model only when debugging device-specific bugs.

Q: Why are some iPads showing as desktop in GA4?

Since iPadOS 13, Safari on iPad defaults to a desktop User-Agent string. Because GA4 detects category from the UA, those sessions report as desktop rather than tablet. To estimate true tablet share, cross-reference device.brand equals Apple with screen-resolution data.

Q: Can I create an audience based on device category?

Yes. Go to Admin Audiences New audience, set the condition to Device category exactly matches mobile, desktop, or tablet, and save. The audience can be used as a remarketing list in Google Ads or as a comparison filter in any GA4 report.

The GA4 device category is the dimension that classifies every session into one of three default buckets — desktop, mobile, or tablet — based on the User-Agent string Google Analytics receives at collection time. It is the fastest way to compare behavior across form factors and the foundation for any device-aware segmentation, audience, or report. This guide covers the definition, the three (sometimes four) default values, how detection works, the difference between device.category and related dimensions like device.brand and device.model, where to find the dimension in reports, and how to segment Explorations by device.

What Is Device Category in GA4?

The device category dimension is part of GA4’s device scope and identifies the type of hardware the user accessed your site or app on. Every GA4 event automatically inherits a device category value at the session level. The full GA4 dimension name is device.category and its values are lowercase strings: desktop, mobile, tablet, and (rarely) smart tv.

Device category is the headline device dimension because it answers the most common segmentation question — “did this convert better on phone or laptop?” — without forcing analysts to bucket dozens of device.model values manually.

The Three Default Values: Desktop, Mobile, Tablet (and Smart TV)

GA4 reports populate device.category with one of these strings:

desktop — laptops and desktop computers running Windows, macOS, Linux, or ChromeOS in a non-touch browser context
mobile — phones running iOS or Android, plus mobile-mode tablets when the User-Agent string declares mobile rendering
tablet — iPads, Android tablets, Surface tablets — devices identified as tablet form-factor by the UA
smart tv — connected TV browsers (Roku, Apple TV, certain Samsung Tizen / LG webOS contexts). Rare; appears mainly when CTV traffic reaches a website

Roughly 99% of organic web traffic falls into desktop, mobile, or tablet. Smart TV is most common on streaming-related sites or when stray UA strings from connected devices reach a campaign URL. Other categories like “wearable” or “console” are not standard GA4 buckets — they roll up into the closest category Google’s parser can match.

How GA4 Detects Device Category (User-Agent Based)

GA4 derives device.category from the User-Agent (UA) string the browser sends with every request. When the gtag.js or GTM container collects an event, the User-Agent travels along with it; Google’s collection endpoint parses the UA against its device taxonomy and writes a category value into the event. The classification is not based on screen width, touch capability, or viewport — only on UA parsing.

User-Agent string parsing diagram showing how GA4 maps Mozilla, iPhone, iPad, and Smart TV User-Agent strings into device.category values desktop, mobile, tablet, smart tv — How GA4 parses the User-Agent string at event collection to assign device.category — desktop, mobile, tablet, or smart tv

Three implications follow from UA-based detection:

Spoofed User-Agents are taken at face value. A bot or headless browser claiming to be a phone is reported as mobile.
Resizing the browser window does not change the value. Shrinking a desktop window to phone width still reports desktop.
iPadOS UA quirks matter. Since iPadOS 13, iPads default to a desktop UA in Safari — these visits often misclassify as desktop rather than tablet.

device.category vs Other Device Dimensions

GA4 ships several device-scoped dimensions. They look similar but answer different questions:

Dimension	What it contains	Example values
`device.category`	Form-factor bucket — the headline device dimension	desktop, mobile, tablet, smart tv
`device.brand`	Hardware manufacturer parsed from the UA	Apple, Samsung, Google, Xiaomi
`device.model`	Specific device model identifier	iPhone, SM-G998B, Pixel 7
`device.operatingSystem`	OS family	iOS, Android, Windows, macOS, Linux
`device.operatingSystemVersion`	OS version string	17.4, 14, 11.0
`device.web_browser`	Browser application name	Chrome, Safari, Firefox, Edge

The GA4 device dimension hierarchy — device.category sits at the top of the tree, with brand, model, OS, and browser providing finer detail

Pick device.category for high-level dashboards. Drop down to device.brand or device.model only when you need to debug a specific issue (a CSS bug on a Samsung Galaxy fold, for example) — those values explode into hundreds of buckets and become unwieldy in standard reports.

Where to Find Device Category in GA4 Reports

The dimension surfaces in several standard places out of the box:

Reports → User → Tech → Tech details — primary dimension dropdown includes “Device category”
Reports → User → Tech → Overview — the “Users by Device category” card
Reports → Acquisition → Traffic acquisition — add Device category as a secondary dimension
Realtime — filter the realtime report by device category to watch live mobile vs desktop activity
Explorations — drag Device category into Rows, Columns, or Segments in any Free Form, Funnel, or Path exploration

Audiences can also use device category as a condition (Admin → Audiences → New audience → “include users when device.category exactly matches mobile”) to build mobile-only or desktop-only remarketing lists.

How to Segment by Device in Explorations

The cleanest way to compare device behavior is a Free Form exploration with device category as a comparison segment:

Open Explore → Blank and choose Free Form
In the Variables panel, click + next to Dimensions and add Device category
Drag Device category from Variables onto the Rows drop zone in the Tab Settings panel
Add metrics: Sessions, Engaged sessions, Conversions, and a revenue metric if relevant
For deeper segmentation, click + next to Segments, build a User segment with condition Device category exactly matches mobile, save it, and drag it into Segments

The output is a row-by-row breakdown — desktop, mobile, tablet — with your engagement and conversion metrics side by side. Drop in a date-range comparison to spot week-over-week mobile share shifts.

Mobile vs Desktop Behavior — Common Patterns

Across most B2C sites we have audited, three patterns repeat:

Mobile dominates traffic, desktop dominates revenue. Mobile typically carries 55-75% of sessions, but desktop converts at 1.5-3× the rate on transactional flows because forms, payment selectors, and side-by-side comparisons are easier on a larger screen.
Mobile bounces faster. Page-load latency hurts mobile harder — every 100ms of LCP regression on mobile costs measurable engagement, far more than on desktop.
Tablet is closer to desktop than mobile. Tablet sessions usually behave like desktop (longer sessions, higher conversion) even though the user is technically on a touch device.

If you build dashboards comparing mobile vs desktop performance, layer in Core Web Vitals by device — slow mobile LCP is the most common explanation for a mobile-revenue gap.

Limitations: Misclassification, Privacy Restrictions

The User-Agent based approach has well-known limits:

iPad-as-desktop drift. Modern iPadOS Safari sends a desktop UA, so a meaningful share of tablet traffic is logged as desktop. Cross-checking against device.brand = Apple + screen-resolution dimensions can recover some of it.
User-Agent Client Hints. Chrome is replacing the legacy UA string with reduced UA + Client Hints (UA-CH). GA4 supports it, but parsers occasionally fall back to desktop when hint values are not requested by the page.
Privacy browsers and ITP. Brave, Tor, and ad-blocked sessions sometimes strip or randomize UA strings, leading to desktop default-bucketing.
Mobile apps use different dimensions. Native iOS and Android apps report through Firebase SDK, so app sessions get their own device-platform metadata — including the screen view event instead of page_view.
Cross-device journeys are stitched separately. If a user starts on mobile and finishes on desktop, attribution depends on cross-device tracking and cross-platform tracking — device category alone tells you nothing about the journey.

Treat device.category as a reliable form-factor signal at scale, not as a precise per-user classifier. The aggregate trend is what you want.

Frequently Asked Questions

What is device category in GA4?

Device category is the GA4 dimension that classifies each session into desktop, mobile, tablet, or smart tv based on the User-Agent string. It is the headline device dimension and surfaces in Reports → User → Tech and any GA4 events exploration.

How does GA4 detect device category?

Detection happens at the collection endpoint by parsing the User-Agent string. GA4 does not look at screen size, touch capability, or viewport — only the UA. This means resizing your desktop browser to phone width still reports desktop, and a phone with a spoofed UA reports as the spoofed value.

Is smart TV a device category in GA4?

Yes — smart tv is a valid device.category value but it is rare. It appears when connected-TV browsers (Roku, Apple TV, Samsung Tizen, LG webOS) load a website. Most websites see <1% of traffic in this bucket; streaming and broadcaster sites see more.

How do I segment by device in GA4 Explorations?

Open Explore → Free Form, add Device category as a dimension, drag it into Rows, then add Sessions, Engaged sessions, and Conversions as metrics. For deeper segmentation, build a User segment where Device category exactly matches mobile and apply it as a Segment in any exploration.

What is the difference between device.category and device.model?

device.category is a four-bucket form-factor dimension (desktop, mobile, tablet, smart tv). device.model is the specific hardware identifier (iPhone, Pixel 7, SM-G998B). Use category for high-level dashboards and model only when debugging device-specific bugs — model values explode into hundreds of buckets.

Why are some iPads showing as desktop in GA4?

Since iPadOS 13, Safari on iPad defaults to a desktop User-Agent string. Because GA4 detects category from the UA, those sessions report as desktop rather than tablet. To estimate true tablet share, cross-reference device.brand = Apple with screen-resolution data.

Can I create an audience based on device category?

Yes. Go to Admin → Audiences → New audience, set the condition to “Device category exactly matches mobile” (or desktop / tablet), and save. The audience can be used as a remarketing list in Google Ads or as a comparison filter in any GA4 report.

Cross-Device Tracking — stitching journeys across phone, tablet, and desktop
Cross-Platform Tracking — unifying web and app sessions for the same user
Screen View — the mobile-app analog of page_view
Session — the GA4 session boundary that device category is attached to
GA4 events — the event taxonomy that inherits device.category
Source — pair with device category to compare device-by-channel