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.
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:
This recipe reduces bad decisions caused by interpreting incomplete recent data.
Explain missing rows, withheld data, and "why numbers don't match"
GA4 can apply thresholding to protect user privacy and sampling when report/exploration volume exceeds limits. This recipe produces a plain-English explanation, detection checklist, and mitigation playbook (including how to change the question—not just the dashboard).
Stop KPI arguments by defining metrics once and reusing everywhere
Many reporting conflicts come from undefined or inconsistent KPIs (what counts as a lead, which revenue number, what window, etc.). This recipe builds a KPI dictionary and maps each KPI to source systems and owners, including "confidence levels" and known limitations.
Label mistakes so patterns become obvious
Traders often report that profitability improved only after tracking mistakes (not just P&L). This recipe forces a mistake tag on every trade and compiles a mistake leaderboard.
Converts tags + stats into one concrete rule change
Traders often recommend a weekly review to spot repetitive patterns (revenge trades after first loss, overtrading during lunch, etc.). This recipe compiles the week into a short brief and proposes one fix.