integration-nextjs-app-router

PostHog setup for Next.js App Router uses instrumentation-client.ts for initialization and captures events directly in user action handlers rather than useEffect. It identifies users during auth flows and links client and server events using matching distinct IDs.

You track server-side events in Next.js App Router by using the posthog-node library with matching distinct IDs. This approach ensures that server-side analytics correlate correctly with client-side user identification for reliable product insights.

Yes, PostHog feature flag usage works with Next.js 15.3+ App Router by leveraging the correct initialization strategy via instrumentation-client.ts. This setup supports feature flag hooks behavior for consistent evaluation across your application.

The recommended approach is to identify users directly within the authentication action handlers rather than using useEffect. This method ensures user identification correlates accurately between client and server events using matching distinct IDs.

You add error tracking to critical user actions in Next.js by implementing exception capture alongside your event instrumentation. This captures errors consistently within critical flows like onboarding and login for reliable product insights.

Yes, you can use PostHog with a reverse proxy by applying routing compatibility considerations for PostHog assets endpoints. This ensures analytics assets load correctly while maintaining your existing proxy infrastructure.