event-analytics

Featured

Customer event analytics across every GTM system — Intercom, Zendesk, Salesforce, HubSpot, Segment, Amplitude, Mixpanel, PostHog, and custom event pipelines. Covers event taxonomy design, tracking implementation, event-driven workflows, and unified customer views. Use when implementing event tracking, building a customer data pipeline, or designing event-driven GTM automations. Triggers on: "event analytics", "customer events", "event tracking", "product analytics", "Segment setup", "event pipeline".

AI & Automation 49 stars 14 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
57
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Event Analytics ## Overview Events are the atomic unit of customer understanding. Every signup, click, feature use, upgrade, and cancellation is an event. The mistake: tracking events haphazardly ("track everything!") with no taxonomy, creating a data swamp instead of a data pipeline. This skill covers event analytics across every GTM system — how to design an event taxonomy, implement tracking, and unify event data across your stack to build a complete customer picture. ## Authoritative Foundations - **Segment — Customer Data Platform (CDP) and event taxonomy** — Customer Data Platform (CDP) and event taxonomy - **Amplitude — Behavioral analytics and event design** — Behavioral analytics and event design - **Mixpanel — Product analytics and event-based reporting** — Product analytics and event-based reporting - **Intercom — Event-driven messaging and automation** — Event-driven messaging and automation - **Avo — Event taxonomy and governance** — Event taxonomy and governance - **Snowplow — Open-source event pipeline** — Open-source event pipeline ## When to Use Trigger phrases: "event analytics setup", "customer event tracking", "implement Segment", "Amplitude setup for SaaS", "event taxonomy design", "customer data pipeline", "product analytics events", "Intercom events", "event-driven workflows" ## Step-by-Step Process ### Phase 1: Event Taxonomy Design **The 4 event types (Segment spec):** 1. **Identify:** Who is the user? `identify(userId, traits)` 2. **Track...

Details

Author
LeadMagic
Repository
LeadMagic/gtm-skills
Created
3 months ago
Last Updated
4 days ago
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

analytics-tracking

Set up, audit, and debug analytics tracking implementation — GA4, Google Tag Manager, event taxonomy, conversion tracking, and data quality. Use when building a tracking plan from scratch, auditing existing analytics for gaps or errors, debugging missing events, or setting up GTM. Trigger keywords: GA4 setup, Google Tag Manager, GTM, event tracking, analytics implementation, conversion tracking, tracking plan, event taxonomy, custom dimensions, UTM tracking, analytics audit, missing events, tracking broken. NOT for analyzing marketing campaign data — use campaign-analytics for that. NOT for BI dashboards — use product-analytics for in-product event analysis.

25,834 Updated 1 weeks ago
alirezarezvani
Code & Development Listed

analytics

Product analytics implementation — event tracking, funnel analysis, A/B testing, Segment/Amplitude/Mixpanel/PostHog, privacy-compliant instrumentation.

26 Updated 1 weeks ago
arbazkhan971
Web & Frontend Listed

event-taxonomy

Establish one canonical event taxonomy and versioned schema registry for product analytics — object.verb naming, schema-as-code with CI validation, cross-source normalization, and forward-compatibility rules. Use when the user wants to name analytics events, design a tracking plan, clean up inconsistent event names, or unify analytics with webhook event types. Also use when they mention "instrumentation", "Segment spec", "Amplitude/Mixpanel/PostHog events", "usage metering", or are wiring metered billing to usage data, even if they never say "taxonomy".

0 Updated 1 months ago
alexpate