kai-analyticslisted

# /kai-analytics — A Measurement System Whose Numbers Can Be Trusted ## Objective A marketing measurement system the team can operate: an event taxonomy with defined triggers and properties, a UTM convention nobody has to guess at, an attribution model matched to the actual data volume, dashboard specs for three audiences, and a pixel/tag plan that survives a consent check. The result is that "where do customers come from" and "which ads work" have answers someone can reproduce. Matching the model to the data is the load-bearing judgment. A data-driven attribution model on 50 conversions a month produces confident nonsense. ## Done when Work type `strategy-plan` — floor **E3/C3/O1** (`harness/eco-floors.yaml`). - **E3** — a named human approved the exact tracking plan, UTM guide, and dashboard specs. - **C3** — the deliverables clear `banned_word_check`, and someone other than the author read them end to end. Every metric in every dashboard spec carries a written definition ("conversion rate = signups / unique visitors"); an undefined metric is a craft failure. - **O1** — each P0 implementation item names the blind spot it closes, its owner, and how anyone will know the event is firing correctly. The plan's own outcome is instrumentation proven, not documents delivered. A tracking plan nobody implements is not CLOSED. Its first work item is named in the implementation checklist. ## Constraints - **Read `MARKETING.md` from the project root first.** It carries product,