# Review GA4 key events and their volumes

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

The key events inventory with volumes, the property's definition of success made explicit.

**Intent.** Which events count as conversions, and whether they fire plausibly.

## When to use

- Onboarding.
- Before any conversion-based analysis.

## 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. List key events. — tools: `ga4_get_key_events`
2. Check volumes per event over the window. — tools: `ga4_run_report`

## Decision rules

- **When** A key event fires at implausible volume (zero, or per-pageview levels) → **conclude** Definition or wiring problem: route to tracking-audit before analyses lean on it.

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

- Renamed events keep old history under the old name: continuity breaks silently.

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