saas-analytics-patterns
SaaS analytics event taxonomy, metric formulas (MRR, churn, LTV), provider-agnostic tracking, funnel analysis, cohort setup, and privacy-respecting instrumentation.
Profile →npx skills add vibeeval/vibecosystem --skill saas-analytics-patterns --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# SaaS Analytics Patterns Provider-agnostic analytics for SaaS products. Track what matters, name it consistently, respect privacy. ## Event Naming Convention Use `object_action` format. Past tense for completed actions. ```typescript // GOOD: structured object_action naming const Events = { USER_SIGNED_UP: 'user_signed_up', PLAN_UPGRADED: 'plan_upgraded', PLAN_DOWNGRADED: 'plan_downgraded', PAYMENT_FAILED: 'payment_failed', TRIAL_STARTED: 'trial_started', FEATURE_USED: 'feature_used', INVITE_SENT: 'invite_sent', ONBOARDING_COMPLETED: 'onboarding_completed', } as const // BAD: ad-hoc, inconsistent naming // 'click_upgrade_button' -- UI action, not business event // 'userSignedUp' -- camelCase breaks grouping in dashboards // 'Signed Up' -- spaces break queries // 'signup' -- ambiguous (started? completed?) ``` ## Analytics Provider Abstraction Never couple your app to a specific vendor (Mixpanel, Amplitude, PostHog). ```typescript interface AnalyticsProvider { identify(userId: string, traits: Record<string, unknown>): void track(event: string, properties?: Record<string, unknown>): void page(name: string, properties?: Record<string, unknown>): void reset(): void } class Analytics {
- Event Naming Convention
- Analytics Provider Abstraction
- SaaS Metric Formulas
- Event Taxonomy Design
- Funnel Tracking
- Feature Flag + Analytics
- Server-Side vs Client-Side
- Privacy-Respecting Analytics
- Cohort Analysis Setup
What does the saas-analytics-patterns skill do?
SaaS analytics event taxonomy, metric formulas (MRR, churn, LTV), provider-agnostic tracking, funnel analysis, cohort setup, and privacy-respecting instrumentation.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill saas-analytics-patterns --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.