Analytics: Measure engaged sessions and post-card retention

[sajeetharan]

Problem

Page views and card requests do not explain whether users find ongoing value. DevGlobe needs a privacy-conscious event model to measure which journeys increase useful session depth and repeat visits.

Proposed solution

Define and implement a small engagement funnel around discovery, card generation, comparison, recommendations, and return visits.

Acceptance criteria

• Document event names, trigger semantics, allowed properties, and data retention
• Track card_generated, profile_viewed, comparison_started, recommendation_opened, next_action_selected, and session_restored
• Distinguish intentional user actions from image requests, bots, previews, and social crawlers
• Define engaged session and returning-user metrics before building dashboards
• Avoid sending private profile fields, search text, OAuth data, or raw identifiers not needed for analysis
• Prevent duplicate events caused by rerenders and retries
• Add funnel reporting for card generation to a second meaningful action
• Compare 7-day and 30-day return rates by entry journey
• Add analytics verification tests and a development debug mode

Initial success metrics

• Percentage of card generators who take another meaningful action
• Profiles viewed per engaged session
• Comparison or recommendation activation rate
• 7-day return rate for claimed users

Related issues

• Post-card journey: Feature: Post-card next-action journey #117
• Impact history: Feature: Developer impact history and rank movement dashboard #111
• Contribution opportunities: Feature: Personalized open-source contribution opportunities #112
• Watchlists: Feature: Developer and project watchlists with update notifications #113