AutoGineer
Generated banner for Integration Astro Ssr
Generated logo for Integration Astro Ssr

Integration Astro Ssr

PostHogOfficialCreated by PostHog

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

From the author

PostHog integration for server-rendered Astro applications with API routes
— 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 implementing PostHog analytics in Astro projects configured for server-side rendering (SSR). It covers the setup of both client-side browser tracking via the PostHog web snippet and server-side event tracking using the posthog-node library. The integration ensures session continuity by passing session IDs between the client and server, and provides patterns for user identification, error tracking, and environment variable management.

What it does

  • Configures client-side PostHog tracking using a reusable Astro component.
  • Sets up server-side event tracking in API routes using posthog-node.
  • Implements a singleton pattern for the server-side PostHog client.
  • Enables session continuity by passing session IDs via HTTP headers.
  • Provides guidelines for secure environment variable usage.
  • Supports user identification and error tracking across the application.

When to use it

  • When you need to add analytics to an Astro application using SSR.
  • When you require both client-side and server-side event tracking.
  • When you need to maintain session consistency between browser and API routes.
  • When you want to track user login, signup, or custom events in an Astro project.

Advantages

  • Unified tracking across client and server environments.
  • Prevents common Astro build errors with proper script directives.
  • Maintains clean architecture with singleton server-side clients.
  • Ensures secure handling of project tokens via environment variables.

Usage examples

“How do I initialize PostHog in my Astro SSR project?”
The agent will guide you to create a posthog.astro component with the web snippet and include it in your root layout.
“How can I track events from an Astro API route?”
The agent will show you how to use the posthog-node singleton in your API route files to capture events server-side.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/posthog/integration-astro-ssr/download

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

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

Documentation by PostHog

PostHog integration for Astro (SSR)

This skill helps you add PostHog analytics to Astro (SSR) 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 - Astro (SSR) example project code

  • references/astro.md - Astro - 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

  • Always use the is:inline directive on PostHog script tags to prevent Astro from processing them and causing TypeScript errors

  • Use PUBLIC_ prefix for client-side environment variables in Astro (e.g., PUBLIC_POSTHOG_PROJECT_TOKEN)

  • Create a posthog.astro component in src/components/ for reusable initialization across pages

  • Import the PostHog component in a Layout and wrap all pages with that layout

  • Use posthog-node in API routes under src/pages/api/ for server-side event tracking

  • Store the posthog-node client instance in a singleton pattern (src/lib/posthog-server.ts) to avoid creating multiple clients

  • Pass the client session ID to server via X-PostHog-Session-Id header for unified session tracking

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.

Needs: Needs Node.js

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/astro-ssr · 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 or PostHog.

Download ZIP

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