AutoGineer
Generated banner for Integration Angular
Generated logo for Integration Angular

Integration Angular

PostHogOfficialCreated by PostHog

  • Skill
  • Tool integration
  • Data and AI
  • MIT
  • No issues found
Download ZIP

From the author

PostHog integration for Angular applications
— the description by PostHog

AutoGineer summary

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

This skill provides a structured approach to integrating the PostHog JavaScript SDK into Angular projects. It emphasizes creating a singleton service to wrap the SDK, ensuring SSR safety, and following best practices for environment configuration and user identification. The integration covers event tracking, session recording, and error monitoring, with specific patterns for modern Angular versions.

What it does

  • Provides a pattern for creating a singleton PostHog service in Angular.
  • Ensures SSR safety when using PostHog in Angular applications.
  • Guides the configuration of environment variables for API keys and hosts.
  • Demonstrates how to identify users during authentication flows.
  • Includes patterns for capturing custom events and tracking errors.
  • Offers guidance on initializing PostHog outside the Angular zone for performance.

When to use it

  • When you need to add product analytics to an Angular application.
  • When you want to implement session replay or error tracking in Angular.
  • When you need to identify users to link frontend events to backend data.
  • When you are setting up a new Angular project and want to include PostHog from the start.

Advantages

  • Promotes a clean, maintainable architecture using singleton services.
  • Prevents performance issues by running PostHog outside the Angular zone.
  • Ensures secure handling of API keys via environment variables.
  • Provides SSR-safe implementation patterns for universal Angular apps.

Usage examples

“How do I initialize PostHog in my Angular app?”
The skill guides you to create a PostHogService singleton and initialize it in the root component, ensuring it is ready before other components render.
“How do I track a user login in Angular with PostHog?”
The skill provides the pattern for using the identify method within your authentication service to link user sessions to specific IDs.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/posthog/integration-angular/download

  2. Unzip it into the cross-client skills folder of your project:

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

Documentation by PostHog

PostHog integration for Angular

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

  • references/angular.md - Angular - 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

  • Use inject() instead of constructor injection. PostHog service should be injected via inject() in components/services that need it.

  • Create a dedicated PosthogService as a singleton root service that wraps the PostHog SDK.

  • Always use standalone components over NgModules.

  • Configure PostHog credentials in src/environments/environment.ts files, as Angular reads environment variables from these configuration files

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/basic-integration-1.3-conclude.md

title: PostHog Setup - Conclusion description: Review and fix any errors in the PostHog integration implementation

Use the PostHog MCP to create a new dashboard named "Analytics basics" based on the events created here. Make sure to use the exact same event names as implemented in the code. Populate it with up to five insights, with special emphasis on things like conversion funnels, churn events, and other business critical insights.

Search for a file called .posthog-events.json and read it for available events. Do not spawn subagents.

Create the file posthog-setup-report.md. It should include a summary of the integration edits, a table with the event names, event descriptions, and files where events were added, along with a list of links for the dashboard and insights created. Follow this format:

<wizard-report> # PostHog post-wizard report

The wizard has completed a deep integration of your project. [Detailed summary of changes]

[table of events/descriptions/files]

Next steps

We've built some insights and a dashboard for you to keep an eye on user behavior, based on the events we just instrumented:

[links]

Agent skill

We've left an agent skill folder in your project. You can use this context for further agent development when using Claude Code. This will help ensure the model provides the most up-to-date approaches for integrating PostHog.

</wizard-report>

Upon completion, remove .posthog-events.json.

Status

Status to report in this phase:

  • Configured dashboard: [insert PostHog dashboard URL]

  • Created setup report: [insert full local file path]

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/angular · 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-angular.zip