# Check GA4 server-side tagging health

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

Server-side diagnostics read: transport health, event flow, the modern tagging chain's weak link.

**Intent.** Whether the server container still relays truthfully.

## When to use

- After infrastructure changes.
- When client-side and server-side counts diverge.

## 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. Run server-side tagging diagnostics. — tools: `ga4_get_server_side_tagging_diagnostics`
2. Date any failure and bound what flowed through it.

## Decision rules

- **When** The transport failed for a period → **conclude** Everything measured through it in that period is suspect: bound the damage by dates.

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

- A healthy transport with wrong mapping still lies: health is necessary, not sufficient.

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