api-analytics-posthog-analytics

# PostHog Analytics Patterns > **Quick Guide:** Use PostHog for product analytics with structured event naming (`category:object_action`), server-side tracking for reliability, and proper user identification integrated with your authentication flow. Client-side for UI interactions, server-side for business events. Always call `reset()` on logout, never store PII in event properties, and use `captureImmediate()` or `await shutdown()` in serverless environments. **Detailed Resources:** - [examples/core.md](examples/core.md) - Event naming, user identification, property conventions - [examples/client-tracking.md](examples/client-tracking.md) - React hooks, provider setup, component tracking - [examples/server-tracking.md](examples/server-tracking.md) - posthog-node, serverless patterns, auth events - [examples/group-analytics.md](examples/group-analytics.md) - B2B organization tracking - [examples/privacy-gdpr.md](examples/privacy-gdpr.md) - GDPR consent, cookieless mode, PII filtering - [reference.md](reference.md) - Decision frameworks, anti-patterns, event taxonomy --- <critical_requirements> ## CRITICAL: Before Using This Skill > **All code must follow project conventions in CLAUDE.md** (kebab-case, named exports, import ordering, `import type`, named constants) **(You MUST call `posthog.identify()` ONLY when a user signs up or logs in - never on every page load)** **(You MUST include the user's database ID as `distinct_id` in ALL server-side events)** **(You MUST ...