PostHog makes it easy to get data about usage of your Vue.js (opens in a new tab) app. Integrating PostHog into your app enables analytics about user behavior, custom events capture, session replays, feature flags, and more.
If your site sets a Content-Security-Policy, it needs to allow PostHog. This applies to the snippet and to package installs alike: the SDK lazy-loads extra bundles (session replay, surveys) from PostHog’s CDN, and sends events to the ingestion host. PostHog serves from subdomains of posthog.com that change over time, so allow the wildcard:
script-src covers the snippet and the lazy-loaded bundles, connect-src covers event ingestion and feature flags, and worker-src covers session replay. The toolbar needs a few more (opens in a new tab), or use a reverse proxy (opens in a new tab) so everything is first-party. Failing to do so causes silent failures where capture and identify calls never send, so the integration looks complete while zero events arrive. Remember connect-src falls back to default-src, so default-src 'self' blocks event delivery even when the script itself is bundled.
Next, depending on your Vue version, we recommend initializing PostHog using the composition API or as a plugin.
We use the Composition API as it provides better accessibility, maintainability, and type safety.
PostHog initializes as a singleton, so you can initialize it in your main.ts file before you mount your app. This ensures PostHog is initialized before any other code runs.
src/main.ts
typescript
// src/main.tsimport { createApp } from 'vue'import { createPinia } from 'pinia'import App from './App.vue'import router from './router'import posthog from "posthog-js";const app = createApp(App);posthog.init(import.meta.env.VITE_POSTHOG_PROJECT_TOKEN || '<ph_project_token>', { api_host: import.meta.env.VITE_POSTHOG_HOST || 'https://us.i.posthog.com', defaults: '2026-05-30',});app.use(createPinia())app.use(router)app.config.errorHandler = (err, instance, info) => { posthog.captureException(err)}app.mount('#app')
Then, you can access PostHog throughout your app just by importing it from posthog-js.
Start by creating a plugins folder and adding a posthog.js file to that folder. In posthog.js, initialize PostHog using the install method with your project token and host. You can find these in your project settings (opens in a new tab).
// src/main.jsimport Vue from 'vue'import App from './App.vue'import PosthogPlugin from './plugins/posthog'Vue.config.productionTip = falseVue.use(PosthogPlugin)new Vue({ render: h => h(App),}).$mount('#app')
This makes PostHog available as this.$posthog in any Vue component.
Use a stable ID from your auth system when possible, not an email or display name. Send those as person properties instead. If your app has no other stable key, email works as a fallback if they are unique. Never a shared literal like "anonymous" or "user", which pools many people onto one person and corrupts their data. When no ID is available at all, skip the identify and retain the anonymous distinct ID that’s automatically assigned.
Call posthog.reset() on logout, so the next person to use the browser doesn’t inherit the last one’s identity.
If your app calls your own backend, tracing_headers adds X-POSTHOG-DISTINCT-ID and X-POSTHOG-SESSION-ID to matching fetch and XMLHttpRequest requests. This lets server-side SDKs link backend events, errors, and LLM traces back to frontend sessions and replays. Use hostnames only, without protocols or paths.
JavaScript
javascript
posthog.init('<ph_project_token>', { api_host: 'https://us.i.posthog.com', // Optional: send PostHog session/user context to your backend tracing_headers: ['api.example.com'],})
This works in local development too, but match on the hostname alone: use 'localhost', not 'localhost:3000'. Ports are never part of a hostname, so a value with one in it never matches anything. localhost and 127.0.0.1 are also different hostnames — use whichever your app actually calls.
Tracing headers help you attribute events across front and backend consistently. When this isn’t available, use your server-side stable IDs to deduce the matching distinctId, and pass it in when capturing the event.
Once you have PostHog initialized, there is a lot more you can do with it beyond autocapture, pageviews, and pageleaves. You can find the full details in our JavaScript SDK docs (opens in a new tab), but we’ll cover a few examples here.
To capture custom events, evaluate feature flags, and use any of the other PostHog features, you can use the posthog object returned from the usePostHog composable like this:
When using feature flags on pages that users navigate to directly, the flags may not be loaded when the component first renders. To ensure your UI updates reactively when flags load, create a composable that returns a reactive ref:
JavaScript
javascript
// src/composables/usePostHogFeatureFlag.tsimport { ref, type Ref } from 'vue'import { usePostHog } from './usePostHog'export function usePostHogFeatureFlag( feature: string,): Ref<string | boolean | undefined> { const { posthog } = usePostHog() const flag = ref(posthog.getFeatureFlag(feature)) posthog.onFeatureFlags(() => { flag.value = posthog.getFeatureFlag(feature) }) return flag}
To capture custom events, evaluate feature flags, and use any of the other PostHog features, you can use the $posthog object returned from the plugin like this:
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 (opens in a new tab).
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 (opens in a new tab), 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.
For any technical questions for how to integrate specific PostHog features into Vue (such as analytics, feature flags, A/B testing, or surveys), have a look at our JavaScript Web (opens in a new tab) SDK docs.
Alternatively, the following tutorials can help you get started: