Compare New and Returning Users in PostHog
Use lifecycle categories around a meaningful repeat action, then compare new and returning groups under the same interval. A larger new-user group can reflect acquisition while established users quietly become dormant.
Before you start: Have identified activity events and a realistic usage cadence. Confirm that your definition of new matches the report’s identity behavior rather than assuming it always equals account signup.
Worked example: A reporting product used weekly should assess repeat report sharing on a weekly cadence. Daily inactivity may be normal even for healthy customers.
Step-by-step guide
Choose the activity
Select a core action that represents useful product engagement. Avoid a background event that makes everyone appear active.
Set the natural interval
Use a cadence appropriate to the product task and retain it across comparisons. Explain why daily, weekly or monthly activity answers the question.
Inspect lifecycle categories
Use the lifecycle insight to separate new, returning and other supported categories. Check how identified activity determines the start of a user’s lifecycle.
Validate sample histories
Open examples from new and returning groups. Confirm that an identity change or late instrumentation is not presenting an established person as newly active.
Compare rates and counts
Look at the size of each group alongside the eligible population. Acquisition growth can mask weak repeat use if only total activity is reported.
Choose the follow-up
Investigate the segment with a meaningful change and record the hypothesis. Use retention or a focused cohort comparison to validate a repeat-use concern.
Common mistakes
Daily cadence for weekly work
Healthy users can look dormant. Match the interval to the task.
New equals signup
Identity and first observed activity matter. Validate the report definition.
Totals hide mix
More acquisition can offset declining returning use. Inspect the groups separately.
Tips
Keep lifecycle cadence in the chart name.
Inspect one known returning user after identity changes.
Pair counts with the underlying population and exposure.
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.