analytics▌

### PostHog Node.js Integration - Install the posthog-node SDK and initialize it with environment variables, ensuring exception autocapture is enabled. - Instrument route handlers with posthog.capture() for user actions and integrate posthog.captureException() into error middleware. - Identify users during authentication and pass session headers from the frontend to maintain event correlation across the stack.

### PostHog Astro SSR Integration - Initialize PostHog using a reusable component in your Astro layout and store the server-side client in a singleton pattern. - Use environment variables with the PUBLIC_ prefix for client-side keys and keep all PostHog script tags marked as is:inline. - Maintain session correlation by passing distinct IDs and session IDs via headers when tracking events across frontend and API routes.

### PostHog Error Tracking for Nuxt - Integrate PostHog error tracking into Nuxt applications using environment variables for secure configuration of keys and host URLs. - Enable exception autocapture in the SDK initialization and use captureException for manual error handling at specific boundaries. - Upload source maps to ensure stack traces resolve to original source code rather than minified production bundles.

### PostHog Feature Flags for Next.js - Initialize PostHog globally via instrumentation-client.ts to enable hooks without wrapping components in a provider. - Evaluate flags server-side using posthog-node and pass values as props to client components to prevent hydration mismatches and flicker. - Use useFeatureFlagEnabled or useFeatureFlagPayload hooks in client components and handle loading states for asynchronous flag data.

### PostHog React Feature Flags - Use useFeatureFlagEnabled or useFeatureFlagPayload hooks to manage flags while handling loading states and external synchronization. - Secure PostHog keys using environment variables and prefer server-side flag evaluation to prevent UI flickering during rendering. - Avoid using useEffect for state management or event handling; reserve it strictly for synchronizing with external systems.

### PostHog Error Tracking for React - Initialize PostHog with exception autocapture enabled and use environment variables for all sensitive configuration keys. - Upload source maps to ensure stack traces are readable and use captureException in error boundaries for non-propagating errors. - Integrate error tracking alongside existing logic without restructuring or replacing current error handling patterns.

### PostHog React Native Error Tracking - Install posthog-react-native and react-native-svg, using environment variables for project tokens and host URLs. - Enable exception autocapture in the SDK initialization and use captureException() within error boundaries for manual reporting. - Upload source maps to ensure stack traces resolve to original source code and wrap the app with PostHogProvider for full integration.

### PostHog Python Error Tracking - Initialize the Posthog client with enable_exception_autocapture=True and use instance-based constructors instead of module-level config. - Protect user privacy by excluding PII from capture() event properties, using set() or identify_context() for person-related data instead. - Ensure reliable event delivery by registering posthog_client.shutdown with atexit and using environment variables for sensitive keys.

### PostHog Angular Error Tracking - Implement a singleton PosthogService using inject() to wrap the SDK and manage initialization within standalone components. - Enable exception autocapture during SDK initialization and use captureException() for errors caught at specific boundaries. - Secure credentials via environment files and upload source maps to ensure stack traces resolve to original source code.

### PostHog iOS Feature Flags - Securely manage PostHog keys using environment variables and a dedicated enum to prevent hardcoding sensitive configuration data. - Implement SPM dependencies by creating distinct PBXBuildFile, XCSwiftPackageProductDependency, and XCRemoteSwiftPackageReference objects. - Prioritize server-side flag evaluation to prevent UI flickering and enable outgoing network connections for sandboxed applications.