Generated banner for Integration Nuxt 4
Generated logo for Integration Nuxt 4

Integration Nuxt 4

PostHogOfficialCreated by PostHog

  • Skill
  • Tool integration
  • Software development
  • MIT
  • No issues found

From the author

PostHog integration for Nuxt 4 applications
— the description by PostHog

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a systematic, multi-step process for adding PostHog analytics to Nuxt 4 projects. It emphasizes a secure and consistent implementation pattern, requiring the use of environment variables and specific identification practices for user authentication. The workflow covers both client-side and server-side tracking, ensuring critical business operations are captured accurately while maintaining correlation between sessions.

What it does

  • Guides the user through a four-step integration process for PostHog.
  • Provides patterns for identifying users during login and signup events.
  • Ensures server-side events are implemented for critical business logic.
  • Includes instructions for setting up error tracking.
  • Promotes secure configuration using environment variables.
  • References example project structures for implementation consistency.

When to use it

  • When you need to add product analytics to a Nuxt 4 application.
  • When you want to implement session replay and feature flags in Nuxt 4.
  • When you need to capture server-side events for authentication or payment flows.
  • When you want to ensure consistent error tracking across client and server boundaries.

Advantages

  • Provides a clear, step-by-step procedure to avoid common integration pitfalls.
  • Ensures data integrity by requiring server-side tracking for critical actions.
  • Promotes security by mandating the use of environment variables for API keys.
  • Maintains session correlation between frontend and backend components.

Usage examples

“Help me integrate PostHog into my new Nuxt 4 project.”
The agent will initiate the four-step workflow, starting with the project analysis and event tracking plan creation.
“How do I track user logins in my Nuxt 4 app with PostHog?”
The agent will guide you to identify users during the login flow using the recommended identify pattern and headers for session correlation.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/posthog/integration-nuxt-4/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip integration-nuxt-4.zip -d .agents/skills

Documentation by PostHog

PostHog integration for Nuxt 4

This skill helps you add PostHog analytics to Nuxt 4 applications.

Workflow

Follow these steps in order to complete the integration:

  1. basic-integration-1.0-begin.md - PostHog Setup - Begin ← Start here

  2. basic-integration-1.1-edit.md - PostHog Setup - Edit

  3. basic-integration-1.2-revise.md - PostHog Setup - Revise

  4. basic-integration-1.3-conclude.md - PostHog Setup - Conclusion

Reference files

  • references/EXAMPLE.md - Nuxt 4 example project code

  • references/nuxt-js.md - Nuxt.js - docs

  • references/identify-users.md - Identify users - docs

  • references/basic-integration-1.0-begin.md - PostHog setup - begin

  • references/basic-integration-1.1-edit.md - PostHog setup - edit

  • references/basic-integration-1.2-revise.md - PostHog setup - revise

  • references/basic-integration-1.3-conclude.md - PostHog setup - conclusion

The example project shows the target implementation pattern. Consult the documentation for API details.

Key principles

  • Environment variables: Always use environment variables for PostHog keys. Never hardcode them.

  • Minimal changes: Add PostHog code alongside existing integrations. Don't replace or restructure existing code.

  • Match the example: Your implementation should follow the example project's patterns as closely as possible.

Framework guidelines

No specific framework guidelines.

Identifying users

Identify users during login and signup events. Refer to the example code and documentation for the correct identify pattern for this framework. If both frontend and backend code exist, pass the client-side session and distinct ID using X-POSTHOG-DISTINCT-ID and X-POSTHOG-SESSION-ID headers to maintain correlation.

Error tracking

Add PostHog error tracking to relevant files, particularly around critical user flows and API boundaries.

Files

references/nuxt-js.md

Nuxt.js - Docs

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:

PostHog AI

npm
npm install @posthog/nuxt
Yarn
yarn add @posthog/nuxt
pnpm
pnpm add @posthog/nuxt
Bun
bun add @posthog/nuxt

Identifying users

Identifying users is required. Call posthog.identify('your-user-id') after login to link events to a known user. This is what connects frontend event captures, session replays, LLM traces, and error tracking to the same person — and lets backend events link back too.

See our guide on identifying users for how to set this up.

Configuration

Add the module to your nuxt.config.ts file:

nuxt.config.ts

PostHog AI

export default defineNuxtConfig({
  modules: ['@posthog/nuxt'],
  posthogConfig: {
    publicKey: '<ph_project_token>', // Find it in project settings https://app.posthog.com/settings/project
    host: 'https://us.i.posthog.com', // Optional: defaults to https://us.i.posthog.com. Use https://eu.i.posthog.com for EU region
    clientConfig: {
      // Optional: PostHog client configuration options
    },
  },
})

Usage on the client side

The module provides the usePostHog() composable which is auto-imported and available in all your Vue components:

app/pages/index.vue

PostHog AI

<script setup>
const posthog = usePostHog()
// Capture a custom event
posthog?.capture('button_clicked', { button_name: 'signup' })
</script>

Note: usePostHog() returns undefined on 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:

server/utils/posthog.ts

PostHog AI

import { PostHog } from 'posthog-node'
let client: PostHog | null = null
export function useServerPostHog(): PostHog {
  if (!client) {
    const config = useRuntimeConfig()
    client = new PostHog(config.public.posthog.publicKey, {
      host: config.public.posthog.host,
    })
  }
  return client
}

Then use it in your server routes:

server/api/example.ts

PostHog AI

export default defineEventHandler((event) => {
  const posthog = useServerPostHog()
  posthog.capture({
    distinctId: 'user_123',
    event: 'server_event',
  })
  return { success: true }
})

Set up a reverse proxy (recommended)

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, which is free for all PostHog Cloud users, 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.

Grouping products in one project (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.

Add IPs to Firewall/WAF allowlists (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: 3.75.65.221, 18.197.246.42, 3.120.223.253

US: 44.205.89.55, 52.4.194.122, 44.208.188.173

These are public, stable IPs used by PostHog services (e.g., Celery tasks for snapshots).

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.

Vue

PostHog AI

<script setup>
const isEnabled = useFeatureFlagEnabled('new-feature')
// returns true, false, or undefined
</script>
<template>
  <div v-if="isEnabled">Feature is enabled!</div>
</template>

Vue

PostHog AI

<script setup>
const variant = useFeatureFlagVariantKey('experiment')
// returns the variant string, true/false, or undefined
</script>
<template>
  <div v-if="variant === 'control'">Control group</div>
  <div v-else-if="variant === 'test'">Test group</div>
</template>

Vue

PostHog AI

<script setup>
const payload = useFeatureFlagPayload('config-flag')
// returns any JSON value or undefined
</script>
<template>
  <div v-if="payload">Config: {{ payload.value }}</div>
</template>

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:

Community questions

Ask a question

Was this page useful?

HelpfulCould be better

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
PostHog
Publisher
PostHog (Official)
Source
PostHog/skills · skills/posthog/integration/skills/nuxt-4 · commit a5d30e7
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
PostHog/skills

AutoGineer is not affiliated with or endorsed by PostHog.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download integration-nuxt-4.zip