RecipeGoogle Analytics 4
Read GA4 performance by device
Device cuts on engagement and conversion, the site-side check on device debates.
IntentDevice-class truth from the site's own measurements.
- 2
- Steps
- 2
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Before device-based bidding.
- Mobile-performance arguments.
Do not use it when
- No specific contraindication beyond the preconditions below.
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 report.
Cut the worst device by browser before concluding.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
One browser drags the device class
Conclude
A compatibility bug wearing a device costume: name the browser for the product team.
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.
- Tablet is a rounding error most places: do not let its noise reshape mobile conclusions.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.