> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atomicagi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Devices

> Compare mobile, desktop, and device-level performance

<Frame>
  <img src="https://mintcdn.com/atomicai/2EwXzkqhhawPmJOp/images/data/google-search/app-google-search-devices.png?fit=max&auto=format&n=2EwXzkqhhawPmJOp&q=85&s=de91582cbcad1edcfb0d6b004508e4b0" alt="Google Search devices tab with device trend and breakdown table" width="1536" height="1024" data-path="images/data/google-search/app-google-search-devices.png" />
</Frame>

Use this page to compare performance by device and decide where to focus first. It helps you answer three practical questions:

1. Is growth or decline concentrated on one device type?
2. Are ranking and visibility changes different on mobile vs desktop?
3. Which device should drive your next optimization sprint?

## Before you analyze

* Keep the same date window when comparing devices.
* Check absolute volume first, then percentage movement.
* Check device shifts against recent page or template releases.

## What this page gives you

The Devices page combines:

* Device trend lines for `Desktop`, `Mobile`, and `Tablet`.
* Summary metrics per device to compare contribution and momentum.
* A compact breakdown table with `Clicks`, `Impressions`, and `Conversions`.
* Shared filters for keyword, page, device, and country segmentation.

## How to read device performance correctly

* `Clicks` tells you current traffic contribution by device.
* `Impressions` shows demand and visibility by device.
* `Conversions` helps avoid optimizing only for traffic volume.

A device with lower traffic but stronger conversions may deserve higher priority than a high-volume but weak segment.

## Quick weekly checklist

1. Read the overall trend.
   Check whether all devices move together or one diverges.
2. Compare contribution levels.
   Identify the dominant device and the fastest mover.
3. Evaluate conversion quality.
   Avoid over-investing in segments with weak downstream impact.
4. Link to release timeline.
   Match device shifts to recent page, template, or UX changes.
5. Convert into focused tasks.
   Assign mobile, desktop, or tablet-specific fixes and owners.

Use the device breakdown table for quick decision-making in weekly operations.

<Frame>
  <img src="https://mintcdn.com/atomicai/2EwXzkqhhawPmJOp/images/data/google-search/app-google-search-devices-table.png?fit=max&auto=format&n=2EwXzkqhhawPmJOp&q=85&s=743626e18767a7db6b946c023e7c48b5" alt="Google Search devices breakdown table with clicks impressions and conversions per device" width="958" height="219" data-path="images/data/google-search/app-google-search-devices-table.png" />
</Frame>

## How to use filters

Use filters to isolate root cause before assigning work.

<Frame>
  <img src="https://mintcdn.com/atomicai/2EwXzkqhhawPmJOp/images/data/google-search/app-google-search-devices-filters.png?fit=max&auto=format&n=2EwXzkqhhawPmJOp&q=85&s=5d5ff19dcc43f3373cf03d201fcaaf58" alt="Google Search devices filters panel" width="1536" height="1024" data-path="images/data/google-search/app-google-search-devices-filters.png" />
</Frame>

* `Device = Mobile`
  Isolate mobile behavior and validate UX-driven ideas.
* `Page contains [/blog/ or /product/]`
  Compare template-level device performance differences.
* `Country = [market]`
  Check whether device behavior shifts by region.
* `Keyword contains [cluster term]`
  Detect topic-specific differences in intent and CTR by device.

## What to fix first

| Pattern in device data                        | What it usually means            | Recommended action                                       |
| --------------------------------------------- | -------------------------------- | -------------------------------------------------------- |
| Mobile down, desktop stable                   | Mobile UX or rendering issue     | Audit mobile templates, performance, and search snippets |
| Impressions up, clicks flat on one device     | CTR is weak                      | Improve titles/meta and intent alignment                 |
| Clicks stable, conversions down on one device | On-page friction after the click | Review layout, CTA placement, and forms                  |
| Tablet volatile with low baseline             | Low sample-size noise            | Monitor longer before high-effort changes                |
| Desktop up, mobile down after redesign        | Responsive layout regression     | Run targeted QA and fix breakpoint-specific issues       |

## Team routine

1. Weekly: flag largest device divergence and assign corrective tasks.
2. Bi-weekly: validate if fixes improved target device metrics.
3. Monthly: report device split trend and conversion quality changes.
4. Quarterly: review device-specific template strategy and performance debt.

## Keep in mind

* Tablet data can be sparse; treat large percentages carefully.
* Device type alone does not explain intent; pair with page and keyword segments.
* Short windows can overstate noise, especially on smaller traffic sources.

## Where to go next

* [Google Search overview](/data/google-search/overview): top-level trend context
* [Landing pages](/data/google-search/landing-pages): page-level impact by device behavior
* [Keywords](/data/google-search/keywords): query intent differences behind device shifts
* [Geography](/data/google-search/geography): device performance differences across markets