D Health Checks
This phase guide is being expanded including detailed walkthroughs. The structure and steps below are accurate.
After go-live, check your setup health anytime. The assistant detects drift, missing events, and routing failures by comparing current state against the baseline captured during go-live.
What this phase does
Phase D is the ongoing health monitoring layer. Each time you run a health check, the assistant compares the current state of your setup against the post-cutover baseline. It checks routing health, container drift, and critical event presence.
Health checks are on-demand — they run when you open the app or click "check health." The assistant also detects when a GTM container version has changed since the last check and suggests re-scanning if needed.
Before you start
- Phase C complete: production is server-routed and the baseline is captured.
What gets checked
| Check | What it detects |
|---|---|
| Routing liveness | Is the server endpoint still responding? |
| sGTM confirmation | Is the endpoint running server-side GTM? |
| Critical event presence | Are verified critical events still visible in GA4 realtime? |
| Web container drift | Has the web GTM container changed since go-live? |
| Server container drift | Has the server GTM container changed since go-live? |
Health status
- Healthy — all checks passing. Routing is live, events are arriving, no container drift detected.
- Warning — container drift detected, or event attestation not yet completed for the current check run. Worth reviewing but not an outage.
- Attention needed — routing is down, a verified critical event is missing, or the server endpoint is unreachable. Investigate promptly.
What you'll have when done
An ongoing health dashboard showing the current state of your server-side setup compared to the post-cutover baseline. Check anytime to catch drift, missing events, and routing failures before they affect your data.