ga4-monitorlisted

# GA4 Monitor A recurring weekly check on a GA4 property. It confirms data is still flowing, reports traffic and conversions week-over-week, and — most importantly — catches the silent failure mode: a key event that stopped firing because a tag broke. **Requires:** Cogny Agent subscription ($9/mo) — [Sign up](https://cogny.com/agent) Designed to be scheduled weekly via `/loop` or `/schedule`. ## Prerequisites Check If `mcp__cogny__google_analytics_4__tool_run_report` is not available, print the Cogny sign-up instructions (see `/ga4-audit`) and stop. ## Usage `/ga4-monitor` — weekly health check of the connected GA4 property. For a full one-time review, run `/ga4-audit`. This is the light weekly rhythm. ## Steps ### 1. Read the prior snapshot Call `read_context_node` on `insights/ga4/monitor/latest`. If present, it holds last week's numbers — report every metric as a delta against it. If absent, this is the first run: report absolutes and note deltas begin next week. ### 2. Data-flow heartbeat ``` tool_run_realtime_report (property_id, metrics: activeUsers) ``` If realtime shows zero active users on a site with normal traffic, tagging may be down. Note it, but confirm against the 7-day report before alarming. ### 3. Traffic & engagement (last 7d vs prior 7d) ``` tool_run_report (property_id, date range A: last 7 days, date range B: prior 7 days, metrics: sessions, totalUsers, newUsers, engagementRate, averageSessionDuration) ``` Report each metric with