posthog

Implement PostHog client- and server-side event tracking with TypeScript schemas.

Updated Oct 6, 2025
One-click install
npx skills add https://github.com/nathanielcrowell12-spec/photo-vault --skill posthog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: posthog
Source: https://github.com/nathanielcrowell12-spec/photo-vault/tree/main/.claude/skills/posthog
Command: npx skills add https://github.com/nathanielcrowell12-spec/photo-vault --skill posthog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual work of setting up analytics by providing pre-configured event tracking patterns.

Core Features & Use Cases

  • Dual Tracking System: Automatically implement both client-side and server-side analytics to bypass ad blockers.

Quick Start

Use the posthog skill to track when a client views a photo gallery, ensuring you capture critical funnel data even when client tracking is blocked.

Core Features & Use Cases

  • Revenue Event Tracking: Automatically track payment completions and subscription changes with guaranteed delivery.

Frequently Asked Questions about posthog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track user behavior across both client and server to bypass ad blockers?

Implement dual tracking with PostHog by setting up client-side events for engagement (page views, clicks) and server-side events for critical funnel data (signup, payment, churn). Server-side tracking ensures analytics capture even when client-side tracking is blocked by ad blockers.

What's the best way to ensure payment and subscription events are reliably tracked?

Track revenue events server-side with PostHog to guarantee delivery. Server-side flushing for payment completions and subscription changes ensures these critical funnel events reach your analytics regardless of client-side filtering or network conditions.

Can I use TypeScript with my analytics event tracking?

Yes. PostHog integration enforces strict TypeScript typings for all events, providing type safety and IDE autocomplete for client-side and server-side event schemas. This prevents tracking errors and enables early user identification with confidence.

How do I identify users early in the funnel for better analytics?

PostHog's dual tracking system supports early user identification on both client and server, allowing you to tag users at signup and track their behavior through the entire funnel for accurate cohort and conversion analysis.

Do I need separate implementations for tracking page views versus revenue events?

No. PostHog provides a unified pattern where engagement events (page views, button clicks) can be client-side tracked, while critical events (payment, subscription changes) are automatically server-side flushed with privacy defaults applied across both environments.