KiloClawPowered by OpenClaw
Back to Cookbook

GA4 Event Taxonomy Auditor

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.

House RecipeWork12 min setup
Try in KiloClawFree 7-day trial

INGREDIENTS

🔎Web Search📄Google Docs🌐Browser

PROMPT

Audit our GA4 event taxonomy and propose a clean standard. Deliver: - Event naming convention (with format rules and examples) - Required parameters dictionary (per funnel stage) - Conversion/key-event map (event → business outcome) - QA checklist (pre-release + weekly monitoring) - Governance rules (who can create events, deprecation process) Inputs: - Business type + funnel stages: - Existing events (paste list or top 50): - Key events/conversions: - How events are implemented (GTM/gtag): - Known pain points:

How It Works

This recipe turns GA4 "event soup" into a maintainable measurement layer.

Triggers

  • Reports don't answer basic questions without custom work
  • Conversions are missing, duplicated, or hard to interpret
  • Multiple teams implemented tracking without a shared standard

Inputs

  • Current event list (top events, key events/conversions)
  • Business funnel definitions (lead → MQL → SQL → purchase)
  • Tagging method (gtag, GTM) and where parameters are set

Outputs

  • Event naming convention + parameter dictionary
  • Conversion / key event mapping to business outcomes
  • QA checklist (pre-release and weekly)

Actions / Steps

  1. Inventory events and group them by funnel stage.
  2. Identify duplicates (same meaning, different names) and collisions (same name, different meaning).
  3. Define mandatory parameters per funnel stage (e.g., value, currency, content_id, form_id).
  4. Specify governance: who can create events, how changes are reviewed, how to deprecate events.

Parameters

  • Funnel stages (custom to business)
  • Required parameters per stage
  • Naming format (snake_case, verbs, etc.)

Examples

  • "Our 'lead' event exists 5 different ways. Fix the taxonomy."
  • "We can't tie content to conversions because content_id is missing."
Tags:#ga4#analytics#measurement#digital-marketing#governance

Related Recipes

Attribution Gap Triage

Diagnose missing conversions and "flying blind" measurement fast

Use this when the numbers don't match: ad platforms over/under-report, GA4 looks off, CRM revenue doesn't reconcile, or privacy changes (ATT/cookie loss/consent) have degraded tracking. It produces a root-cause shortlist, a "what to trust" guidance note, and a prioritized fix plan.

Work10 min setup

Privacy-First Measurement Blueprint

Rebuild measurement around first-party data, consent, and signal loss

Create a privacy-first measurement architecture that accepts signal loss as permanent: define a durable KPI stack, implement consent-aware tracking priorities, and choose when to use modeled vs deterministic data. Outputs a blueprint plus an implementation backlog for a quarter.

Work15 min setup

Mistake Tagger

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.

Personal6 min setup

Weekly Review Compiler

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.

Personal5 min setup