Generated banner for Integration Nuxt 3 6
Generated logo for Integration Nuxt 3 6

Integration Nuxt 3 6

PostHogOfficialCreated by PostHog

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

From the author

PostHog integration for Nuxt versions 3.0 to 3.6
— the description by PostHog

AutoGineer summary

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

This skill provides a step-by-step procedure for adding PostHog analytics to Nuxt 3.6 projects. Because Nuxt 3.0-3.6 does not support the standard @posthog/nuxt package, this workflow guides developers through manual implementation using posthog-js and posthog-node. It covers client-side initialization, server-side tracking, user identification, and error tracking to ensure a complete analytics setup.

What it does

  • Guides the manual installation of PostHog packages for Nuxt 3.6
  • Provides a structured 4-step integration workflow
  • Demonstrates client-side plugin configuration for Nuxt
  • Outlines patterns for server-side event tracking in API routes
  • Explains how to identify users and maintain session correlation
  • Includes instructions for implementing error tracking

When to use it

  • When you need to add PostHog analytics to a Nuxt 3.0 through 3.6 application
  • When you require both client-side and server-side event tracking
  • When you need to implement user identification and error tracking in a Nuxt 3 environment
  • When you want to follow established patterns for environment variable management and API integration

Advantages

  • Provides a clear, sequential path for integration
  • Ensures consistent implementation of server-side and client-side tracking
  • Promotes best practices like using environment variables for sensitive keys
  • Offers a reference project to verify implementation patterns

Usage examples

“How do I start integrating PostHog into my Nuxt 3.6 project?”
The agent will initiate the workflow, starting with the setup phase and guiding you through the required file analysis and dependency verification.
“How should I handle user identification in Nuxt 3.6 with PostHog?”
The agent will direct you to the identification patterns, explaining how to use client-side login events and pass session headers to the backend.

Install

  1. Download the skill as a ZIP:

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

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

Documentation by PostHog

PostHog integration for Nuxt 3.6

This skill helps you add PostHog analytics to Nuxt 3.6 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 3.6 example project code

  • references/nuxt-js-3-6.md - Nuxt.js (v3.0 to v3.6) - 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-3-6.md

Nuxt.js (v3.0 to v3.6) - 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.

These docs are for Nuxt v3.0 to v3.6. You can see a working example of the Nuxt v3.0 integration in our Nuxt.js demo app

Setting up PostHog on the client side

  1. Install posthog-js using your package manager:

PostHog AI

npm
npm install --save posthog-js
Yarn
yarn add posthog-js
pnpm
pnpm add posthog-js
Bun
bun add posthog-js
  1. Add your PostHog API key and host to your nuxt.config.js file. You can find these in your project settings.

nuxt.config.js

PostHog AI

export default defineNuxtConfig({
  runtimeConfig: {
    public: {
      posthogToken: process.env.NUXT_PUBLIC_POSTHOG_TOKEN || '<ph_project_token>',
      posthogHost: process.env.NUXT_PUBLIC_POSTHOG_HOST || 'https://us.i.posthog.com',
      posthogDefaults: '2026-01-30',
    },
  }
})
  1. Create a new plugin by creating a new file posthog.client.js in your plugins directory.

plugins/posthog.client.js

PostHog AI

import { defineNuxtPlugin, useRuntimeConfig } from '#imports'
import posthog from 'posthog-js'
export default defineNuxtPlugin(() => {
  const runtimeConfig = useRuntimeConfig()
  const posthogClient = posthog.init(runtimeConfig.public.posthogToken, {
    api_host: runtimeConfig.public.posthogHost,
    defaults: runtimeConfig.public.posthogDefaults,
    loaded: (posthog) => {
      if (import.meta.env.MODE === 'development') posthog.debug()
    },
  })
  return {
    provide: {
      posthog: () => posthogClient,
    },
  }
})

PostHog can then be accessed throughout your Nuxt.js using the provider accessor, for example:

Vue

PostHog AI

<script setup>
   const { $posthog } = useNuxtApp()
   if ($posthog) {
      const posthog = $posthog()
      posthog.capture('<event_name>')
   }
</script>

See the JavaScript SDK docs for all usable functions, such as:

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).

Setting up PostHog on the server side

Install posthog-node using your package manager:

PostHog AI

npm
npm install posthog-node --save
Yarn
yarn add posthog-node
pnpm
pnpm add posthog-node
Bun
bun add posthog-node

Add your PostHog API key and host to your nuxt.config.js file. If you've already done this when adding PostHog to the client side, you can skip this step.

nuxt.config.js

PostHog AI

export default defineNuxtConfig({
  runtimeConfig: {
    public: {
      posthogToken: '<ph_project_token>',
      posthogHost: 'https://us.i.posthog.com',
      posthogDefaults: '2026-01-30',
    }
  }
})

Initialize the PostHog Node client where you'd like to use it on the server side. For example, in a server route:

server/api/example.js

PostHog AI

const runtimeConfig = useRuntimeConfig()
  const posthog = new PostHog(
    runtimeConfig.public.posthogToken,
    {
      host: runtimeConfig.public.posthogHost,
    }
  );
  posthog.capture({
    event: 'api_call',
    distinctId: distinctId,
    properties: {
      $current_url: url,
      query: query
    }
  })
  posthog.shutdown()
  return {
    message: "example response"

Note: Make sure to always call posthog.shutdown() after capturing events from the server-side. PostHog queues events into larger batches, and this call forces all batched events to be flushed immediately.

See the Node SDK docs for all usable functions, such as:

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-3.6 · 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-3-6.zip