cyberneticlibrary

event-tracking-design

Creating and implementing systems for monitoring and analyzing user interactions.

no-skill baseline: 68% — anything below it makes the model worse.

1WORKS 90
analyticsskilldefault
Solo founder or analyst setting up analytics for the first time — provides tool recommendation by stage, event naming conventions, core metrics framework, and GA4 setup checklist to track decisions not dashboards.
2WORKS 82
analyticsskill
When you're instrumenting a site and need consistent, decision-first tracking architecture.
3WORKS 82
data-and-funnel-analyticsskill
B2B SaaS and e-commerce when you need event naming conventions, funnel architecture, and benchmark interpretation to measure marketing ROI.
4WORKS 82
analytics-trackingskill
Analyst or PM setting up comprehensive analytics for SaaS or product — covers full workflow from business context → decision questions → event naming → GA4 implementation, with templates for essential events.
5WORKS 82
analytics-trackingskill
PM or analyst implementing analytics for SaaS product — full workflow from business questions → event design → GA4 setup, with essential event templates for apps and marketing sites.
6WORKS 58
analytics-trackingskill
Startups building analytics infrastructure correctly from scratch or teams auditing data quality before strategic decisions.
7WORKS 50
trackingskill
Content marketer or analyst tracking article ROI via CTA clicks and funnel attribution — sets up user ID for cross-session tracking, event naming convention for consistency, and conversion marking for multi-touch attribution.
8WORKS 50
analyticsskill
When defining and implementing product telemetry and metrics.
9WORKS 31
analytics-trackingskill
Finding why metrics don't match between platforms (GA4 vs ad account) before rebuilding reporting