RecipeGoogle Analytics 4
Check GA4 server-side tagging health
Server-side diagnostics read: transport health, event flow, the modern tagging chain's weak link.
IntentWhether the server container still relays truthfully.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- After infrastructure changes.
- When client-side and server-side counts diverge.
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 server-side tagging diagnostics.
Date any failure and bound what flowed through it.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
The transport failed for a period
Conclude
Everything measured through it in that period is suspect: bound the damage by dates.
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.
- A healthy transport with wrong mapping still lies: health is necessary, not sufficient.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.