Read Google Ads campaign performance the right way
Campaign performance ranked by spend with statuses, so the account's story is readable in one table.
IntentA clean campaign-level performance table, ranked by spend, with statuses attached.
- 2
- Steps
- 2
- Tools
- 2
- Rules
- 2
- Failure modes
When to use it
Use it when
- Any 'how are the campaigns doing' question.
- The first read on an unfamiliar account.
Do not use it when
- When the question is why something changed: use campaign-anomaly-investigation.
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.
Pull campaigns with status, type and serving state.
Pull performance over the window and rank by spend.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
A paused campaign still shows spend in the window
Conclude
It ran during the window: date the pause before reading the numbers as current.
When
The top campaign by spend is 'Limited by budget'
Conclude
The account's ceiling is money, not demand: say so before any efficiency judgement.
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.
- Reading removed campaigns' history as live performance.
- The last 72 hours under-report conversions on every read.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.