Setting up mobile traffic measurement isn’t about ticking a box and forgetting about it. It requires deciding which analytics property to use, how to separate desktop traffic from smartphone traffic, and what to do when the data doesn’t add up. Here’s the concrete process, with the points where it usually breaks down.
Step 1: choose the right property before touching anything
If your site has a separate mobile version (for example, m.yourdomain.com) and a desktop one, you need to decide whether to measure both in a single property or in two separate ones. The cleanest option is a single property with a data stream that distinguishes the platform. If you keep separate properties, any comparison between devices will force you to export and cross-reference data by hand; on projects with thousands of daily sessions, that becomes unmanageable.
A common mistake appears here: having the measurement tag duplicated on the mobile version because the theme or plugin injects it twice. The typical symptom is an inflated session count and an abnormally low bounce rate. Check it with the browser’s debugging extension or with the real-time view before accepting any figure as valid.
Step 2: segment by device in the analytics tool
In Google Analytics 4 there is no “mobile” report as such: the device category comes in as a dimension (device category) and you have to add it manually to the exploration reports. The procedure is:
- Open Explore and create a blank report.
- Add the Device category dimension as a breakdown.
- Choose metrics: active users, sessions, engagement rate, and average duration.
- Save the report and share it with the team with read-only permissions.
If you use an alternative such as Matomo or Plausible, the logic is similar: look for the device dimension in the segment settings. According to each platform’s official documentation, the classification is based on the user agent, so browsers that mask it may end up counted as “unknown.”
Step 3: cross-check with Search Console
Search Console offers a breakdown by device type in the Performance section. It doesn’t measure sessions; it measures impressions and clicks from Google Search, so it isn’t useful for calculating conversions. Its real value is in detecting mismatches: if Analytics says only 40% of sessions are mobile but Search Console shows 70% of clicks from smartphones, you have a measurement or redirection problem.
A case I see often: the mobile version redirects to desktop when it detects a large screen, so tablets end up recorded as desktop. The comparison gets thrown off and you lose track of part of the real traffic.
Step 4: verify event and conversion collection
Counting visits isn’t enough. Set up key events (form submission, phone click, add to cart) and check that they fire on mobile. Use the debug view connected to your device to verify each event in real time. If the phone click event doesn’t trigger on iOS, it’s usually because of how the tel: link is built; check that the event selector doesn’t depend on an attribute that Safari ignores.
Step 5: document limitations and keep measuring
No tool captures 100% of traffic: ad blockers, cookie consent, and incognito mode leave gaps. Mobile measurement also suffers more from interrupted browsing and background tabs. Don’t promise exact figures to anyone; present ranges and trends.
Review the setup every time you update the theme, the CMS, or the tags. A template change can remove the tracking code from the footer without anyone noticing until the numbers drop. Schedule a monthly real-time check from a real phone, not just from the desktop browser emulator.