PostHog makes it easy to get data about traffic and usage of your Angular (opens in a new tab) app. Integrating PostHog into your site enables analytics about user behavior, custom events capture, session recordings, 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.
posthogHost: Your project’s client API host. Usually https://us.i.posthog.com for US-based projects and https://eu.i.posthog.com for EU-based projects.
Then, inject the service in your app’s root component app.component.ts. This will make sure PostHog is initialized before any other component is rendered.
app.component.ts
typescript
// src/app/app.component.tsimport { Component } from "@angular/core";import { RouterOutlet } from "@angular/router";import { PosthogService } from "./services/posthog.service";@Component({ selector: "app-root", styleUrls: ["./app.component.scss"], template: ` <router-outlet />`, imports: [RouterOutlet],})export class AppComponent { title = "angular-app"; constructor(posthogService: PosthogService) {}}
In your src/main.ts, initialize PostHog using your project token and instance address. You can find both in your project settings (opens in a new tab).
main.ts
typescript
// src/main.tsimport { bootstrapApplication } from '@angular/platform-browser';import { appConfig } from './app/app.config';import { AppComponent } from './app/app.component';import { environment } from "./environments/environment";import posthog from 'posthog-js'posthog.init(environment.posthogKey, { api_host: environment.posthogHost, defaults: '2026-05-30'})bootstrapApplication(AppComponent, appConfig) .catch((err) => console.error(err));
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.
Note: If you’re using Typescript, you might have some trouble getting your types to compile because we depend on rrweb but don’t ship all of their types. To accommodate that, you’ll need to add @rrweb/types@2.0.0-alpha.17 and rrweb-snapshot@2.0.0-alpha.17 as a dependency if you want your Angular compiler to typecheck correctly.
Given the nature of this library, you might need to completely clear your .npm cache to get this to work as expected. Make sure your clear your CI’s cache as well.
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.
PostHog automatically tracks your pageviews by hooking up to the browser’s navigator API as long as you initialize PostHog with the defaults config option set after 2026-01-30.
Session replay uses change detection to record the DOM. This can clash with Angular’s change detection.
The recorder tool attempts to detect when an Angular zone is present and avoid the clash but might not always succeed.
If you followed the installation instructions for Angular v17 and above, you don’t need to do anything.
If you followed the installation instructions for Angular v16 and below and you see performance impact from recording in an Angular project, ensure that you use ngZone.runOutsideAngular (opens in a new tab).
posthog.service.ts
typescript
import { Injectable } from '@angular/core';import posthog from 'posthog-js'@Injectable({ providedIn: 'root' })export class PostHogSessionRecordingService { constructor(private ngZone: NgZone) {}initPostHog() { this.ngZone.runOutsideAngular(() => { posthog.init( /* your config */ ) }) }}
Update your posthog.service.ts to restrict the initialization of the PostHog web JS client to the client-side. The web SDK uses methods that are not available on the server side, so we need to check if we’re on the client side before initializing PostHog.
posthog.service.ts
typescript
import { PLATFORM_ID } from "@angular/core";@Injectable({ providedIn: "root" })export class PosthogService { constructor( private ngZone: NgZone, @Inject(PLATFORM_ID) private platformId: Object ) { // Only initialize PostHog in browser environment if (isPlatformBrowser(this.platformId)) { this.initPostHog(); //+ } } private initPostHog() { this.ngZone.runOutsideAngular(() => { posthog.init(environment.posthogKey, {
Extracts the distinct ID from the cookie header. This is set by the web JS client.
Captures an event on the server side.
Evaluates a feature flag on the server side. This can be passed as a provider to the Angular application.
Calls shutdown on the PostHog Node client to ensure all events are flushed.
Using PostHog in server-side code
Angular SSR does not allow Node.js code to be bundled into client-side components. Even though resolvers and other server-side code can be written along with client-side components, you cannot use PostHog Node in those components.
For any technical questions for how to integrate specific PostHog features into Angular (such as feature flags, A/B testing, surveys, etc.), have a look at our JavaScript Web SDK docs (opens in a new tab).
Alternatively, the following tutorials can help you get started: