Mobile share of revenue shows what portion of online revenue is generated on mobile devices. It’s one of the most cited “mobile commerce”
metrics because it often differs from mobile share of traffic, revealing a measurable conversion/checkout gap on mobile.
Back to the hub:
E-commerce Statistics.
Compare revenue share with
mobile share of traffic
and funnel impact from
cart abandonment rate
and conversion rate (CR) benchmarks.
Table of Contents
ToggleKey benchmarks (quick reference)
Benchmarks depend on scope (retail-only vs broader e-commerce, web vs app, tracked panel size). Use one benchmark source consistently
within a report, or show two sources to communicate variance.
56.3%
Retail benchmark: mobile generated 56.3% of revenue for retailers (traffic share 77% in the same reference set).
> 50%
Retail benchmark (summary): mobile drove “more than half of revenue” in the referenced retail report summary.
Use mobile revenue share as a “device outcomes” metric. For device inputs, reference
mobile share of traffic.
For funnel-level explanations, use
cart abandonment
and CR benchmarks.
The “traffic vs revenue” gap (why this metric matters)
Mobile commonly dominates visits, but revenue share is usually lower—this gap is a measurable signal of mobile conversion friction,
payment friction, or category/device behavior differences.
Example benchmark gap (retail)
| Metric | Mobile share | How to interpret |
|---|---|---|
| Traffic share | 77% | Mobile is where most browsing happens. |
| Revenue share | 56.3% | Mobile under-indexes vs its traffic share (conversion/checkout gap). |
| Gap | 20.7 pp | Often explained by checkout friction, payment method fit, or category/device mix. |
How to use the gap in reporting
If your mobile traffic share is high but mobile revenue share lags, the next “why” pages to cite are:
cart abandonment rate (drop-offs),
payment methods share (method fit),
and delivery methods share (delivery expectations).
Breakdowns and segmentation ideas
Not every source publishes the same splits. Use the segmentation structure below to keep your own reporting consistent and comparable.
Recommended segment cuts (for “like-for-like” benchmarking)
- Market / region: your main country vs global reference.
- Category: high-ticket vs low-ticket categories (this can swing mobile revenue share substantially).
- Device type: mobile vs desktop vs tablet (tablet is often small or merged into mobile).
- Channel mix: paid social and top-of-funnel traffic can skew more mobile than high-intent search.
- Checkout/payment mix: local methods can reduce mobile friction; see BLIK share (Poland).
If you report mobile revenue share, always report mobile traffic share next to it:
mobile share of traffic.
Definition
Make sure “revenue” and “mobile” scope are consistent (web vs app, gross vs net).
Mobile share of revenue is typically calculated as:
Mobile revenue share = Mobile revenue ÷ Total online revenue × 100
- Revenue can be gross or net; be consistent with your reporting standard.
- Mobile may include smartphones only, or smartphones + tablets depending on the source.
- Scope may be retail-only, broader e-commerce, or a specific panel of sites—always cite it.
Reference pages: Glossary • Methodology
Sources
Primary sources used for the benchmark points shown on this page.
-
Contentsquare — Retail digital experience (engagement section) — benchmark reference: mobile generated 56.3% of revenue for retailers (and 77% traffic share in 2023):
contentsquare.com/guides/retail-digital-experience/engagement/ -
Contentsquare — Press release — summary benchmark: mobile driving more than half of revenue and nearly 80% of traffic:
contentsquare.com/press/…/
Hub-wide pages:
Sources •
Methodology •
Glossary
Cite this page
Copy and paste (adjust date if needed).
Suggested citation (APA style):
Best for Ecommerce. (2026). Mobile share of revenue (e-commerce). Retrieved from
/ecommerce-statistics/mobile-ux-tech/mobile-share-of-revenue/