RecipeGoogle Analytics 4
Inventory all GA4 events by volume
The full event census: what fires, what never does, what fires suspiciously much.
IntentEvery event the property collects, ranked, orphans flagged.
- 2
- Steps
- 3
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Onboarding.
- Before schema cleanups.
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.
Run the event report over a long window.
Cross with key events and registered definitions.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Events fire that no definition or report uses
Conclude
Collection debt: candidates for cleanup, listed with volumes.
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.
- Event name typos create twins: near-duplicate names are one finding, not two events.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.