Define an Activation Event in PostHog
Choose an event that indicates a user received the product’s core value, then validate its instrumentation and relationship to later use. Signup is an entry point, not automatically activation.
Before you start: Have event access, a stable user identifier and a written definition of the eligible new-user population.
Worked example: For a collaborative reporting app, a first report shared with a teammate may represent value better than opening the editor. Compare that candidate with later repeat use before adopting it.
Step-by-step guide
Write the value moment
Describe what the user accomplishes without naming an analytics event. Decide whether the unit is a person or an account before counting successful outcomes.
Map it to an event
Find the event closest to confirmed success. Check its properties and distinguish a button click from the completed operation it initiates.
Inspect sample journeys
Review several known users and confirm the candidate fires at the intended moment. Look for retries, duplicates and server/client identity mismatches.
Define the activation window
Build a funnel from the agreed entry event to the candidate value event. State the allowed interval and exclude internal users consistently.
Challenge the candidate
Compare later behavior for activated and non-activated users with equal observation time. Treat association as supporting evidence rather than proof of causation.
Publish the definition
Save the insight with its owner, event meaning and exclusions. Record limitations and a review trigger if product behavior or instrumentation changes.
Common mistakes
Activity mistaken for value
A page view may indicate curiosity rather than success. Choose a meaningful completed outcome.
Wrong denominator
Invited teammates and self-serve owners may have different opportunities to activate. Define eligibility.
Unlimited conversion window
A lifetime conversion rate hides how quickly value arrives. State a useful observation window.
Tips
Keep a rejected candidate and its reason in the metric notes.
Check the event against one manually verified user journey.
Review activation when the product’s core task changes.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.