integration-nextjs-app-router

To integrate PostHog analytics into a Next.js App Router application, initialize posthog-js in instrumentation-client.ts for client-side tracking and use posthog-node for server-side API routes. This setup enables environment-based configuration, cross-domain correlation, and user identification across the app router architecture.

Server-side event tracking with Next.js App Router uses posthog-node within API routes and server components to capture events. This ensures cross-domain correlation between client boundaries, maintains session identification, and applies environment-based configuration for analytics data capture.

Yes, PostHog works with Next.js instrumentation-client.ts to enable client-side tracking. You initialize PostHog with your project token and host inside instrumentation-client, allowing you to capture user actions, identify users, and load feature flags directly within the App Router architecture.

The best way to track errors and feature flags in a Next.js App Router app is through PostHog integration. By configuring posthog-js and posthog-node, you capture errors, load feature flags, and track session identification across both client-side and server-side boundaries.

You need environment-based configuration for PostHog in Next.js when setting up analytics across App Router pages and API routes. It ensures proper project token initialization, host routing, and correct server integration for capturing user actions and tracking errors.