Conversion Device Mix Chart

The Conversion Device Mix chart shows which devices visitors used when completing a conversion path.

Use it to compare the share of converting sessions completed on desktop, mobile and tablet, and to identify conversions for which the device could not be classified.

This is a conversion-device report. It does not attempt to identify the device on which a visitor originally started their journey.

Before you begin

Wheremore needs:

Interaction tracking installed and enabled for the selected website.
At least one configured conversion path.
Working conversion zones for the steps in that path.
Confirmed conversion-path completions.
Completed conversion background processing.

The chart works with both Cookie and Cookieless tracking.

Choose the reporting scope

Conversion Device Mix follows the filters at the top of the Conversion dashboard.

Date range

Choose a preset period or enter a custom start and end date.

The selected dates determine which confirmed path completions are included. Preset and custom ranges include the complete start and end dates in the Wheremore account's WordPress timezone.

Website

Select the website you want to analyse.

The website must belong to the active workspace and be available to your account. The chart remains hidden until a website is selected.

Conversion path

Select one conversion path to examine its device mix, or include all available paths for the website.

Selecting one path normally gives the clearest result because different goals can attract different device behaviour.

Only confirmed path completions are included. Individual conversion-zone interactions that did not complete a path are excluded.

Campaign

Select a UTM campaign to restrict the chart to converting sessions associated with that campaign.

The No campaign option includes sessions for which no attributed touchpoint contains a campaign value. It does not necessarily mean the visitor arrived directly.

Audience

The audience filter separates:

Prospects — sessions not marked as authenticated.
Identified visitors — sessions marked as authenticated.
All traffic — both groups.

Audience classification is separate from Cookie or Cookieless tracking. An authenticated session is not automatically a cookie-recognised visitor.

Device

Choose all devices to compare the complete mix, or select desktop, mobile or tablet to isolate conversions completed on that device.

When one device is selected, the chart only includes qualifying converting sessions completed on that device. Its column will therefore represent 100% of the filtered total.

How the chart is calculated

For each qualifying converting session, Wheremore:

Finds confirmed conversion-path completions matching the active filters.
Selects the first qualifying completion in that session.
Reads the device recorded for that completion.
Assigns the session to Desktop, Mobile, Tablet or Unknown.
Counts the session once.
Calculates each device's percentage of all qualifying converting sessions.

The calculation is:

Converting sessions completed on the device ÷ all qualifying converting sessions × 100

If one session contains several qualifying completions, it contributes only once to the chart. This prevents a single converting session from inflating the device totals.

Read the chart

The horizontal axis contains:

Desktop
Mobile
Tablet
Unknown

The vertical axis shows each device's share of qualifying converting sessions as a percentage.

The subtitle shows the total number of converting sessions included in the report.

Hover over a column to see:

The device.
The number of converting sessions.
The percentage of all qualifying converting sessions.

Desktop

Conversions completed in sessions recorded as desktop.

Mobile

Conversions completed in sessions recorded as mobile.

Tablet

Conversions completed in sessions recorded as tablet.

Unknown

Conversions for which Wheremore could not classify the recorded device as desktop, mobile or tablet.

Unknown activity remains visible so valid conversions are not silently removed from the report.

Interpret the results

This may indicate:

The conversion requires detailed comparison or form entry.
Business users are completing the goal during desktop-based working sessions.
The mobile experience is less convenient than the desktop experience.
Desktop campaigns are reaching visitors with stronger intent.

Compare desktop and mobile conversion-path performance before assuming the difference is caused by usability.

This can indicate:

Strong mobile traffic and intent.
A short or simple conversion path.
Effective mobile calls to action and forms.
Campaigns that primarily reach visitors on mobile devices.

Review Page Engagement and Session Replay on mobile to confirm that the experience remains usable throughout the path.

A low mobile share does not automatically mean the mobile experience is failing. The website may simply receive fewer relevant mobile visitors.

Compare the device mix with:

Overall session volume by device.
Conversion Path Flow.
Path conversion rate.
Mobile page engagement.
Mobile session replays.

If mobile receives substantial traffic but contributes relatively few converting sessions, investigate the path for layout, form or interaction friction.

Check whether:

Device information is missing from recent conversion records.
New device values are being recorded outside the expected desktop, mobile and tablet classifications.
Conversion processing has completed correctly.
Tracking implementation changes coincide with the increase.

Cookie tracking can connect eligible activity across sessions when consent and identification rules permit it. However, Conversion Device Mix still classifies each converting session by the device used for its qualifying completion.

It does not claim that the visitor used the same device throughout the wider journey.

Cookieless tracking

Cookieless tracking cannot reliably recognise the same visitor across separate sessions or devices.

The chart remains valid because it reports the device recorded within each individual converting session. It does not require cross-session or cross-device identity.

Why this is not a journey start-versus-finish report

Wheremore does not currently have a reliable way to connect the same anonymous visitor across different devices.

For example, a mobile visit and a later desktop conversion cannot safely be treated as one cross-device journey unless a dependable shared identity exists. Presenting those devices as a confirmed journey start and finish would therefore overstate what the tracking data proves.

Conversion Device Mix makes the narrower, reliable claim: it shows the device used when each qualifying converting session completed a path.

Export the chart

Use the chart menu to:

View the chart full screen.
Download it as PNG.
Download it as JPEG.
Download it as PDF.
Download it as SVG.

The downloaded chart reflects the filters active when it was generated.

Important limitations

Completion device only

The chart reports the device used for the first qualifying completion in each included session. It does not show all devices used earlier in the customer journey.

No cross-device identity

Separate visits on different devices are not presented as one confirmed journey merely because their timing or behaviour appears related.

First qualifying completion

Each session contributes once. If it contains several completions matching the active filters, Wheremore uses the first qualifying completion.

Session-based counting

The chart counts converting sessions, not unique people, conversion events, path steps or revenue.

The same visitor can contribute more than one converting session if they complete qualifying paths in separate sessions.

Device classification

Values other than desktop, mobile and tablet are grouped under Unknown.

Campaign filtering

Campaign filtering uses attributed touchpoint data associated with the converting session. A session can qualify for a named campaign when that campaign appears on one of its recorded attribution touches.

Background processing

New path completions may not appear immediately. Conversion processing must finish before they can qualify.

What to do next

Use Conversion Device Mix with:

Conversion Path Flow — see where sessions progress or leave the selected path.
Path Conversion Rate Trend — compare conversion performance over time.
Channel Performance — compare the channels associated with converting sessions and revenue.
Days to Conversion Distribution — understand how long fully attributed visitor journeys take.
Sessions to Conversion Distribution — understand how many sessions fully attributed journeys require.
Page Engagement — compare scroll, time and click behaviour by device.
Session Replay — investigate individual desktop, mobile or tablet experiences.

Troubleshooting

The chart is not displayed

Check that:

A website is selected.
The website belongs to the active workspace.
Your account has access to the website.

The chart shows no data

Confirm that:

The selected period contains confirmed path completions.
The selected path has configured and working conversion zones.
Conversion background processing has completed.
Campaign, audience and device filters are not excluding the converting sessions.

Try a wider date range with all paths, all campaigns, all traffic and all devices.

Only one device is shown

Check the dashboard's Device filter. If desktop, mobile or tablet is selected, the chart intentionally isolates that device.

Select All Devices to compare the complete conversion-device mix.

The total is lower than another conversion report

Conversion Device Mix counts each qualifying session once and only includes confirmed path completions matching all active filters.

Another report may count conversion events, path-step activity, revenue records or sessions under a different attribution rule.

The Unknown column is unexpectedly high

Review recent conversion data for missing or unfamiliar device values and confirm that the current tracking and conversion-processing code is active.