GA4 Data Freshness Monitor
Stop reacting to incomplete data from the last 24–48 hours
GA4 reporting can be delayed, and some reports can be incomplete due to processing latency. This recipe sets "freshness rules," creates a monitoring checklist, and defines when to use real-time vs standard reports vs backend truth.
INGREDIENTS
PROMPT
Create GA4 data freshness rules for our team. Output: - Freshness policy (by KPI type and reporting cadence) - When to use real-time vs standard reports vs backend data - Stakeholder message template for "numbers may change" - Alert rules for when swings need verification before acting Inputs: - KPIs we monitor daily: - How often stakeholders expect updates: - Primary source of truth (CRM/ecom/backend): - Any known GA4 issues we've seen:
How It Works
This recipe reduces bad decisions caused by interpreting incomplete recent data.
Triggers
- Daily performance meetings rely on "yesterday" and the numbers keep changing
- Stakeholders panic on noisy swings that disappear 48 hours later
Inputs
- Your reporting cadence (daily/weekly/monthly)
- Which GA4 reports/explorations the team uses most
- Which KPIs stakeholders care about
Outputs
- "Data freshness rules" (what date ranges are safe to analyze)
- Decision guidance: real-time vs standard vs warehouse/backend
- A short stakeholder explanation template
Actions / Steps
- Categorize KPIs by tolerance: real-time ops vs strategic trend.
- Define a "no conclusions inside the freshest window" policy (customizable).
- Set a fallback: backend orders/CRM for near-real-time outcomes.
- Document known GA4 caveats (thresholding, sampling) that can worsen freshness interpretation.
Parameters
- Freshness window (e.g., exclude last 48h for standard reporting)
- KPI criticality tiers
- Alert thresholds (e.g., >30% swing triggers verification)