# Batch GA4 reports for a multi-cut analysis

> Tier: recipe. Operating recipe: real tool sequence, core rules, known traps.

Batch report runs for analyses needing many small tables, quota-aware by construction.

**Intent.** Several cuts in one flight, quota-shaped.

## When to use

- Weekly packs.
- Multi-market reads.

## When not to use

- No specific contraindication beyond the preconditions below.

## Sources

Required: Google Analytics 4

## Preconditions

- The account is ticked in the dashboard, confirmed via list_accounts.

## Inputs

- `window`: Analysis window. Default: last 30 days.

## Procedure

1. Design the cut list, then check quota. — tools: `ga4_get_property_quotas_snapshot`
2. Run as batches. — tools: `ga4_batch_run_reports`

## Decision rules

- **When** One cut in a batch fails validation → **conclude** Fix or drop it explicitly: partial batches must say what is missing.

## Evidence requirements

- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.

## Human approval boundary

- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.

## Failure modes

- Batches magnify thresholding across many small tables: totals across cuts will not reconcile.

## Output

- **Readout**: The figures, with windows and accounts named.
- **Flags**: What deserves a deeper skill or a human decision.