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.
Build a KPI dictionary and metric mapping document. Output: - KPI dictionary table (name, definition, formula, owner, source system) - Source-of-truth hierarchy (when numbers conflict, which system wins) - Known limitations and "how to interpret discrepancies" notes - Review process (who updates definitions, how often) Inputs: - KPIs used in reporting: - Systems/tools: - Who consumes the reports: - Known disagreements or confusion:
This recipe creates shared measurement language across SEO, PPC, social, email, and analytics.
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.
Make GA4 usable by fixing event naming, parameters, and conversions
GA4 is event-based and flexible—but teams often ship messy event names, missing parameters, and inconsistent conversions. This recipe audits your event taxonomy and produces a clean naming standard, a conversion map, and a QA checklist.
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.