RecipeGoogle Analytics 4
Check GA4 dimension and metric compatibility before building
The compatibility check run before complex reports, so failures happen at design time.
IntentWhether the planned report's fields can legally combine.
- 2
- Steps
- 2
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Designing bespoke reports.
- After an incompatible-combination error.
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.
Check the field combination.
Adjust the design and only then run.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Fields are incompatible
Conclude
Redesign, do not retry: the API's compatibility rules are constraints, not moods.
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.
- Compatibility differs between core and realtime: check the surface you will run.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.