saas-analytics-patterns

# 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 { private providers: AnalyticsProvider[] = [] private consentGiven = false addProvider(p: AnalyticsProvider): void { this.providers = [...this.providers, p] } setConsent(granted: boolean): void { this.consentGiven = grante...