Production readiness checklist for PostHog integrations: SDK configuration,
graceful degradation, health checks, shutdown hooks, and rollback procedures.
Trigger: "posthog production", "deploy posthog", "posthog go-live",
"posthog launch checklist", "posthog production ready".
allowed-tools
Read, Bash(kubectl:*), Bash(curl:*), Grep
version
1.12.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
["saas","posthog","deployment"]
compatibility
Designed for Claude Code, also compatible with Codex and OpenClaw
PostHog Production Checklist
Overview
Production readiness verification for PostHog integrations. Covers SDK configuration hardening, graceful degradation when PostHog is unavailable, health check endpoints, proper shutdown hooks for serverless, and rollback procedures.
Prerequisites
PostHog integration tested in staging
Production PostHog project with phc_ key
Personal API key (phx_) for server-side features
Deployment pipeline configured
Instructions
Pre-Deployment Checklist
SDK Configuration:
api_host set to correct region (us.i.posthog.com or eu.i.posthog.com)
capture_pageview: false if using SPA with manual pageview tracking
capture_pageleave: true for session duration accuracy
Reverse proxy configured to bypass ad blockers (see posthog-sdk-patterns)
posthog.debug() disabled in production (guarded by NODE_ENV)
autocapture configured to exclude noisy elements
Server-Side:
posthog.shutdown() called in SIGTERM handler and serverless function cleanup
personalApiKey set for local flag evaluation (not just project key)
flushAt and flushInterval tuned (default 20/10s is fine for most apps)
Security:
Personal API key (phx_) never in client bundles or NEXT_PUBLIC_ vars
