How to set up events in PostHog

Autocapture is great for exploration and debugging. It is a poor long-term contract for funnels — CSS and copy changes rename "events" out from under you.

Define a short list of product events you will keep for a year (signup_completed, project_created, invite_sent) and capture those explicitly.

Call identify with your user id once the session is authenticated so anonymous pre-login events merge into the person profile. Without that, retention and funnels across signup break.

Group analytics (organizations/workspaces) needs a parallel group identify pattern when you bill or report by account.

PostHog’s default web bundle is in our heavy script performance cluster. That is often acceptable inside a SaaS app. On a content marketing site that only needs pageviews, prefer Plausible/Fathom (or a thinner PostHog config) and keep PostHog for the product.

See PostHog vs Plausible for the category split.

1. Fire each custom event once in a staging project.
2. Confirm properties types (strings vs numbers).
3. Verify identify merges pre/post login.
4. Recheck quota so autocapture is not burning the bill.

Then build one funnel that matches a real weekly decision — not twelve unused insights.