# Inventory all GA4 events by volume

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

The full event census: what fires, what never does, what fires suspiciously much.

**Intent.** Every event the property collects, ranked, orphans flagged.

## When to use

- Onboarding.
- Before schema cleanups.

## 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. Run the event report over a long window. — tools: `ga4_run_report`
2. Cross with key events and registered definitions. — tools: `ga4_get_key_events`, `ga4_get_custom_definitions`

## Decision rules

- **When** Events fire that no definition or report uses → **conclude** Collection debt: candidates for cleanup, listed with volumes.

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

- Event name typos create twins: near-duplicate names are one finding, not two events.

## Output

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

## Related

- Skill: [tracking-audit](https://www.getmcpads.com/skills/tracking-audit.md)