RecipeGoogle Analytics 4
Batch GA4 reports for a multi-cut analysis
Batch report runs for analyses needing many small tables, quota-aware by construction.
IntentSeveral cuts in one flight, quota-shaped.
- 2
- Steps
- 2
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Weekly packs.
- Multi-market reads.
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.
Design the cut list, then check quota.
Run as batches.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
One cut in a batch fails validation
Conclude
Fix or drop it explicitly: partial batches must say what is missing.
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.
- Batches magnify thresholding across many small tables: totals across cuts will not reconcile.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.