posthog-analytics

Instrument PostHog analytics for SaaS with event naming and privacy compliance.

3|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/robotijn/ctoc --skill posthog-analytics-robotijn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: posthog-analytics
Source: https://github.com/robotijn/ctoc/tree/main/skills/saas/posthog-analytics
Command: npx skills add https://github.com/robotijn/ctoc --skill posthog-analytics-robotijn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SaaS teams often lack reliable, privacy-compliant instrumentation for user behavior tracking, leading to orphaned analytics events, missing B2B organizational reporting, PII leaks, and unfilled insights into activation, retention, and revenue drop-off points.

Core Features & Use Cases

  • End-to-end PostHog setup for SaaS applications covering client and server-side event capture
  • B2B group analytics for org-level funnel and retention reporting
  • Privacy-safe session replay and autocapture configuration to prevent PII and sensitive data leaks
  • Enforced event naming conventions and allowlists to eliminate taxonomy drift
  • Feature flag and A/B/n experiment implementation for product changes
  • Ad-blocker-resistant reverse-proxy setup for reliable client-side event delivery
  • Use Case: A B2B SaaS team can use this skill to track how many organizations complete onboarding activation, identify drop-off points in the free-to-paid conversion funnel, and test whether a new checkout feature improves subscription rates without leaking customer PII.

Quick Start

Use the posthog-analytics skill to instrument your SaaS application with PostHog for product analytics, funnel tracking, and feature flags, following 2026 best practices for privacy, reliability, and B2B reporting.

Frequently Asked Questions about posthog-analytics

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

FAQPage Schema
How do I track B2B organization events in PostHog without orphaned user data?

PostHog group analytics links individual user events to organizational accounts, eliminating orphaned user data. By implementing server-side canonical tracking and enforced event naming conventions, SaaS teams achieve reliable B2B organizational reporting for activation and retention.

What is the best way to prevent PII leaks during PostHog session replay and autocapture?

Preventing PII leaks during PostHog session replay requires privacy-safe autocapture configuration to mask sensitive data elements. Implementing strict allowlists and server-side canonical revenue event tracking ensures compliance while capturing actionable product analytics insights.

How do I set up ad-blocker-resistant PostHog event tracking for a SaaS application?

Ad-blocker-resistant PostHog tracking requires reverse-proxy setup to route client-side SDK delivery through your own domain. This bypasses common ad-blockers, ensuring reliable event capture for product analytics, funnel analysis, and feature flag evaluation.

Can I use PostHog feature flags and A/B testing for free-to-paid conversion funnels?

Yes, PostHog supports feature flags and A/B/n experiments to test checkout optimizations within free-to-paid funnels. By combining client-side event capture with server-side canonical revenue tracking, teams accurately measure subscription rate improvements without data loss.

Why does PostHog event taxonomy drift and how do I enforce naming conventions?

PostHog taxonomy drift occurs when teams inconsistently name events across client and server codebases. Enforce event naming conventions and apply strict allowlists to eliminate taxonomy drift, ensuring accurate product analytics and reliable funnel analysis.

Does PostHog analytics instrumentation work for both client-side and server-side SaaS codebases?

Yes, PostHog instrumentation spans both client-side and server-side SaaS codebases for end-to-end event capture. This ensures reliable product analytics, feature flag evaluation, and server-side canonical revenue tracking aligned with 2026 privacy compliance best practices.