Conversion by device type
Conversion by device type splits the rate across desktop, mobile, and tablet. A persistent mobile-vs-desktop gap is one of the most common findings in CRO, but it can be genuine friction (small forms, slow pages) or an artefact: mobile sessions skew toward research while desktop closes the purchase, and cross-device journeys split one buyer across devices.
What this means
You compute a conversion rate separately for desktop, mobile, and tablet sessions. A gap — most often mobile converting below desktop — is so common it is almost expected, which is exactly why it is easy to over-interpret. The split tells you where conversion differs, not yet why.
Friction or mix?
Part of a device gap is real friction: cramped forms, fat-finger targets, slower pages, and harder payment entry hurt mobile conversion. But part is mix: people browse on mobile and buy later on desktop, so a single buyer's research session counts as a mobile non-conversion and the purchase counts as a desktop conversion. Cross-device journeys therefore deflate mobile and inflate desktop rates.
Before blaming the mobile experience, check page speed, form analytics, and whether mobile traffic is more top-of-funnel. Avoid device fingerprinting to stitch journeys; read the gap directionally instead.
- Mobile-below-desktop is common, so resist over-reading it
- Gap mixes real friction with research-vs-purchase behaviour
- Cross-device journeys deflate mobile, inflate desktop
How it appears in analytics and logs
A device conversion gap flags where to look, not a verdict. Mobile may convert lower because of usability problems, or because mobile is the research device and desktop closes the deal across a split journey.
Diagnostic use case
Segment conversion by device to find friction that hits one form factor, while checking whether the gap is friction or a research-vs-purchase split.
What WebmasterID can help detect
WebmasterID classifies device category from first-party signals, so you can segment conversion by device without device fingerprinting.
Common mistakes
- Blaming mobile UX before ruling out a research-vs-purchase split.
- Using fingerprinting to stitch cross-device journeys.
- Comparing device rates with different conversion definitions.
Privacy and accuracy notes
Device segmentation uses a coarse device category, not fingerprinting. WebmasterID derives device class from the user-agent without building a cross-site profile.
Related pages
- Mobile conversion gaps
Mobile and desktop frequently show different conversion rates, but a lower mobile number is not automatically a defect. The gap can be real friction (small targets, slow pages), different intent (browsing versus buying), or a measurement artefact (consent, tracking loss). Diagnosing which one applies is the work. This page lays out the causes and how to tell them apart.
- Conversion by traffic source
Conversion by traffic source breaks the overall conversion rate down by acquisition channel — organic search, paid, direct, referral, social, email. Different sources carry different intent, so a blended rate hides which channels convert. The reading is complicated by attribution: which touch gets credit determines which source a conversion lands against.
- Page speed and conversion
Loading speed influences whether visitors stay and convert, and Google's Core Web Vitals formalise field metrics for it (LCP, INP, CLS). The direction is well established, but the magnitude is specific to each site and audience — borrowed 'every 100ms costs X%' figures are not yours to cite. This page explains the measurable link and how to study it honestly.
- Privacy-first analytics
Segment by device 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.