# Check GA4 API quotas before heavy analysis

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

The property quota snapshot, read before batch work so the analysis does not die mid-flight.

**Intent.** How much API budget remains before a big pull.

## When to use

- Before batch reporting.
- When calls start failing with quota errors.

## 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. Read the property quota snapshot. — tools: `ga4_get_property_quotas_snapshot`
2. Size the planned pull against remaining tokens and split if needed.

## Decision rules

- **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 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

- Quota is shared across consumers of the property: your budget is not yours alone.

## Output

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