Nuxt.js
Contents
PostHog makes it easy to get data about usage of your Nuxt.js app. Integrating PostHog into your app enables analytics about user behavior, custom events capture, session replays, feature flags, and more.
This guide covers Nuxt v4.x and v3.7+. For these versions, we recommend using @posthog/nuxt module for client-side capture.
The @posthog/nuxt module provides:
- Automatic client-side PostHog initialization
- Auto-imported composables for PostHog and feature flags
- Automatic exception capture for error tracking
- Source map configuration and upload for error tracking
For server-side event capture beyond error tracking, use the posthog-node SDK directly.
Using an older version? See our docs for Nuxt 3.0-3.6 or Nuxt 2.x.
Installation
Install the PostHog Nuxt module using your package manager:
Configuration
Add the module to your nuxt.config.ts file:
Usage on the client side
The module provides the usePostHog() composable which is auto-imported and available in all your Vue components:
Note:
usePostHog()returnsundefinedon the server side during SSR, so use optional chaining?.when calling methods.
Usage on the server side
The @posthog/nuxt module initializes a server-side client for error tracking only. For general event capture in Nitro routes, create your own posthog-node SDK client.
The @posthog/nuxt module makes your config available at runtimeConfig.public.posthog.
First, create a server utility to reuse the PostHog client across requests:
Then use it in your server routes:
We recommend setting up a reverse proxy, so that events are less likely to be intercepted by tracking blockers. We have our own managed reverse proxy service included in the platform packages, which routes through our infrastructure and makes setting up your proxy easy. If you don't want to use our managed service then there are several other options for creating a reverse proxy, including using Cloudflare, AWS Cloudfront, and Vercel.Set up a reverse proxy (recommended)
If you have multiple customer-facing products (e.g. a marketing website + mobile app + web app), it's best to install PostHog on them all and group them in one project. This makes it possible to track users across their entire journey (e.g. from visiting your marketing website to signing up for your product), or how they use your product across multiple platforms.Grouping products in one project (recommended)
For certain features like heatmaps, your Web Application Firewall (WAF) may be blocking PostHog’s requests to your site. Add these IP addresses to your WAF allowlist or rules to let PostHog access your site. EU: US: These are public, stable IPs used by PostHog services (e.g., Celery tasks for snapshots).Add IPs to Firewall/WAF allowlists (recommended)
3.75.65.221, 18.197.246.42, 3.120.223.25344.205.89.55, 52.4.194.122, 44.208.188.173
Feature flags
The module provides auto-imported composables for feature flags. All composables return reactive refs that automatically update when flags are loaded or changed.
Error Tracking
For a detailed error tracking installation guide, including automatic exception capture and source map configuration, see the Nuxt error tracking installation docs.
Troubleshooting
TypeScript errors in posthog config: Remove the .nuxt directory and rebuild your project to regenerate config types.
PostHog not capturing events: Ensure you're using optional chaining (posthog?.capture()) since usePostHog() returns undefined during server-side rendering.
Next steps
For any technical questions for how to integrate specific PostHog features into Nuxt (such as analytics, feature flags, A/B testing, surveys, etc.), have a look at our JavaScript Web and Node SDK docs.
Alternatively, the following tutorials can help you get started: