Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Idea: Retention leaderboard #2828

Closed
paolodamico opened this issue Dec 18, 2020 · 2 comments
Closed

Idea: Retention leaderboard #2828

paolodamico opened this issue Dec 18, 2020 · 2 comments
Labels
concept Ideas that need some shaping up still enhancement New feature or request feature/retention Feature Tag: Retention stale

Comments

@paolodamico
Copy link
Contributor

Is your feature request related to a problem?

As we were doing personas analysis (more context on https://github.com/PostHog/ops/issues/115 and this thread), we manually extracted a list of users and for how many weeks had they been retained. This helped identify the users that have retained for more periods, which is helpful to dive into these users and identify common traits, detect power usage, among other things. The inverse leaderboard is also helpful to identify problems with activation and churn.

Seems like this might be something that other people may have a use for, and we could use ourselves on a regular basis.

Describe the solution you'd like

This is still a very nascent idea, but we could have a simple leaderboard of user and number of days/weeks/months where the user has been retained. Some additional stuff that would be useful (using weeks to describe a period, but really it should work for any period:

  • Number of weeks that the user has been registered.
    • Percentage of weeks for which the user has been retained.
  • Avg. days per week for which the user has triggered the retaining event.

Describe alternatives you've considered

See above.

Additional context

SQL query we used (minus filters).

SELECT COUNT(*) as count,
     email
FROM (
          SELECT DISTINCT toStartOfWeek(e.timestamp) as event_date,
               pdi.person_id as person_id,
               JSONExtractString(person_props.properties, 'email') as email
          from events e
               JOIN (
                    SELECT person_id,
                         distinct_id
                    FROM person_distinct_id
                    WHERE team_id = 2
               ) pdi on e.distinct_id = pdi.distinct_id
               JOIN (
                    SELECT id,
                         properties
                    from person
                    where team_id = 2
               ) person_props ON pdi.person_id = person_props.id
          WHERE e.team_id = 2
          AND event = '$pageview'
)
GROUP BY email
ORDER BY count DESC

Thank you for your feature request – we love each and every one!

@paolodamico paolodamico added enhancement New feature or request concept Ideas that need some shaping up still feature/retention Feature Tag: Retention labels Dec 18, 2020
@paolodamico paolodamico mentioned this issue Dec 18, 2020
14 tasks
@paolodamico paolodamico removed the stale label Jul 19, 2021
@PostHog PostHog deleted a comment from posthog-bot Aug 2, 2021
@posthog-bot
Copy link
Contributor

This issue hasn't seen activity in two years! If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in two weeks.

@posthog-bot
Copy link
Contributor

This issue was closed due to lack of activity. Feel free to reopen if it's still relevant.

@posthog-bot posthog-bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
concept Ideas that need some shaping up still enhancement New feature or request feature/retention Feature Tag: Retention stale
Projects
None yet
Development

No branches or pull requests

2 participants