# Read Google Ads performance by device

> Tier: recipe. Operating recipe: real tool sequence, core rules, known traps.

Device-level performance via GAQL, with the landing-page suspicion built in.

**Intent.** Whether mobile, desktop and tablet earn their shares, campaign by campaign.

## When to use

- Before device bid adjustments.
- When mobile share grew and CPA moved.

## When not to use

- On campaigns whose bid strategies ignore device adjustments: check the strategy first.

## Sources

Required: Google Ads

## Preconditions

- The account is ticked in the dashboard, confirmed via list_accounts.

## Inputs

- `window`: Analysis window. Default: last 30 days.

## Procedure

1. Run the device segmentation query. — tools: `google_ads_run_gaql`
2. Where mobile underperforms, cross with landing page speed before blaming the audience. — tools: `google_ads_get_landing_pages`

## Decision rules

- **When** Mobile converts far below desktop on the same campaigns → **conclude** Suspect the page before the person: check mobile speed and the form, then bid.

## Evidence requirements

- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.

## Human approval boundary

- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.

## Failure modes

- Cross-device journeys credit the closing device: mobile assists are invisible in a device table.

## Output

- **Readout**: The figures, with windows and accounts named.
- **Flags**: What deserves a deeper skill or a human decision.

## Related

- Skill: [landing-page-audit](https://www.getmcpads.com/skills/landing-page-audit.md)
