RecipeGoogle Analytics 4
Check GA4 event parameters actually populate
Event parameters read for coverage: what the schema promises versus what events carry.
IntentDeclared parameters versus filled ones, the metadata truth.
- 2
- Steps
- 3
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Before parameter-based reports.
- After tagging changes.
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.
Read declared parameters and custom definitions.
Verify population rates on the ones analyses need.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
A registered dimension's parameter rarely populates
Conclude
Reports on it sample the minority: quantify the fill rate in every finding that uses it.
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.
- Unregistered parameters are invisible to reports even when they populate.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.