analytics▌

### PostHog Android Error Tracking - Initialize PostHog in the Application class onCreate method using environment variables for keys and host URLs. - Enable exception autocapture for global coverage and use captureException for specific error boundaries and catch blocks. - Upload source maps to resolve minified stack traces and ensure activities have labels for accurate screen view tracking.

### 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 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 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.

### PostHog Flutter Error Tracking - Integrate PostHog by enabling exception autocapture during SDK initialization before implementing manual error reporting. - Use environment variables for API keys and host URLs to maintain security and avoid hardcoding sensitive configuration data. - Upload source maps to ensure minified stack traces are resolved into readable code for effective debugging and issue monitoring.

### PostHog Error Tracking for Hono - Integrate PostHog error tracking into Hono apps using environment variables for keys and host URLs to ensure security. - Enable exception autocapture in the SDK initialization and use captureException() for errors at specific boundary catch blocks. - Upload source maps to resolve stack traces to original source code and maintain existing error handling structures without replacement.

Multi-platform content analytics via Apify Actors for Instagram, Facebook, YouTube, and TikTok. \n \n Supports 17+ specialized Actors covering posts, reels, stories, comments, hashtags, followers, and ads across all four platforms \n Dynamically fetches Actor schemas using mcpc CLI to determine required inputs and available output fields \n Outputs results in three formats: quick chat display, CSV export, or JSON export with customizable result counts \n Requires Apify token in .env file and Nod