RecipeGoogle Ads
Read Google Ads performance by device
Device-level performance via GAQL, with the landing-page suspicion built in.
IntentWhether mobile, desktop and tablet earn their shares, campaign by campaign.
- 2
- Steps
- 2
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Before device bid adjustments.
- When mobile share grew and CPA moved.
Do not use it when
- On campaigns whose bid strategies ignore device adjustments: check the strategy first.
What it needs first
Required
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Run the device segmentation query.
Where mobile underperforms, cross with landing page speed before blaming the audience.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
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 every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- Cross-device journeys credit the closing device: mobile assists are invisible in a device table.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.