Measure Time to Value in PostHog
Use a defined start event and a meaningful value event, then inspect elapsed conversion time alongside the conversion rate. Fast success among a small survivor group does not mean most users reach value quickly.
Before you start: Have validated start/value events, aligned identities and a cohort old enough to complete the observation window.
Worked example: Compare signup to first report shared within seven days. If only a few users share, report that conversion rate beside their time to value rather than presenting speed alone as improvement.
Step-by-step guide
Define the clock
Choose signup, first workspace creation or another meaningful entry. Explain why that moment starts the user’s opportunity to receive value.
Validate the endpoint
Use confirmed completion of the value action. Exclude background initialization or repeated retries that resemble progress without delivering the intended result.
Build the bounded funnel
Place the events in order and set a documented conversion window. Keep internal-user exclusions and the counting unit consistent.
Inspect elapsed time
Use the funnel’s conversion-time analysis to see whether slow users form a distinct group. Compare cohorts under the same window instead of mixing mature and recent signups.
Review non-converters
Inspect where users who never reach the endpoint stop. Their absence from the successful users’ time distribution is a limitation, not evidence that they were fast.
Record a decision
Save the rate, time measure and cohort maturity together. Investigate one slow transition before changing the entire onboarding flow.
Common mistakes
Only reporting successful users
Time-to-convert omits people who never finish. Include the conversion rate.
Different starting events
Changing the clock can create an apparent improvement without changing user experience.
Immature cohorts
New users have had less time to complete. Wait for comparable exposure.
Tips
Use one written definition of value across reports.
Compare acquisition segments only when sample sizes support it.
Keep the no-conversion population visible in the readout.
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.