event-analytics
FeaturedCustomer 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".
Install
Quality Score: 90/100
Skill Content
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
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.
analytics
Product analytics implementation — event tracking, funnel analysis, A/B testing, Segment/Amplitude/Mixpanel/PostHog, privacy-compliant instrumentation.
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".