integration-nextjs-app-router

To add PostHog analytics to a Next.js App Router project, initialize the client in instrumentation-client.ts and configure a server-side client using environment variables. This setup captures client and server events, enables feature flags, and tracks errors across API routes and components.

Yes, you can track server-side events with PostHog in Next.js 15+ by using a dedicated server-side PostHog client. This client includes flush and shutdown semantics to ensure events are properly captured in API routes and server components before execution ends.

The best way to identify users across domains in a Next.js PostHog integration is by calling identify(), passing distinct IDs, and forwarding session headers to server endpoints. Resetting identification on logout maintains correct user linkage across client and server captures.

Feature flags and error tracking work with PostHog in Next.js by initializing the client via instrumentation-client.ts for consistent hooks and capturing exceptions at recommended application boundaries. This allows actionable analytics without reorganizing the app structure.

Yes, you need environment variables to configure PostHog in a Next.js App Router application. Environment-variable-based configuration securely initializes both the client instrumentation and the server-side PostHog client for cross-domain correlation and event capture.