5 solution docs
PostHog solution docs
Product analytics, session replay, feature flags and experiments behind one key.
Pick PostHog and all 5 land in docs/solutions/posthog/, next to the rules and skills that reference them.
Every PostHog doc in the registry
Tags: ad-blockers · after · analytics · conventions · experiments · feature-flags · funnels · identify · naming · nextjs · performance · posthog · react · reverse-proxy · route-handlers · serverless · ssr · typescript · webhooks
Ad blockers eat a third of your analytics: proxy ingestion through your own domain
Blockers match on hostnames, not behaviour. A first-party /ingest route handler forwards events to PostHog server-side and recovers most of the missing traffic.
posthog · analytics · ad-blockers · reverse-proxy
Event names that still make sense in twelve months
Why analytics projects rot into five spellings of "signup", and the object_verb convention plus a typed catalogue that stops it.
posthog · analytics · naming · conventions
Feature flags without the flicker
Client-side flags render the control experience first and swap it a beat later. Evaluate on the server, pass the decision down, and keep a bootstrap for the client hooks.
posthog · feature-flags · nextjs · ssr
The identify race that empties your signup funnel
Events fired before identify() stay on the anonymous profile forever. Here is why the merge is not retroactive, and the ordering that fixes it.
posthog · analytics · identify · funnels
Server events versus client events, and when each one lies
A browser event is a claim, a server event is a record. Which side to fire from, why serverless drops events without after(), and how to keep the two from double-counting.
posthog · analytics · nextjs · serverless