RecipeGoogle Analytics 4
Check GA4 API quotas before heavy analysis
The property quota snapshot, read before batch work so the analysis does not die mid-flight.
IntentHow much API budget remains before a big pull.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Before batch reporting.
- When calls start failing with quota errors.
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.
Read the property quota snapshot.
Size the planned pull against remaining tokens and split if needed.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
The planned pull exceeds remaining quota
Conclude
Split across hours or narrow dimensions now: a half-completed batch is worse than a delayed one.
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.
- Quota is shared across consumers of the property: your budget is not yours alone.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.