Skip to content
This repository was archived by the owner on Dec 3, 2019. It is now read-only.
This repository was archived by the owner on Dec 3, 2019. It is now read-only.

Add metrics for user churn #356

Open

Description

@hollomancer

Feature

Why is this feature being added?

We need a way to measure user churn. Being able to measure our retention is critical, in order to know whether we're improving our ability to keep users active in Slack.

What should your feature do?

As staff, I want to see the number of inactive users per day, as well as the number of new joiners per day, so that I know “How many people joined the OC and did/did not join Slack?”

Activity

  1. hollomancer commented on Jul 10, 2018

    @hollomancer
    MemberAuthor

    What further detail can I add to this?

  2. apex-omontgomery commented on Oct 1, 2018

    @apex-omontgomery
    Member

    Per day you'd want :

    1. Number of users who logged into website
    2. Number of users who logged into slack
    3. Number of users who did not log into slack
    4. Number of users who signed up for website
    5. Number of users who signed up for slack.

    Details:

    1. first one but we only retain 2 signins which can occur on same day.
    2. This one is available using the slack api, and we can get historical data.
    3. This could be done by querying slack user count on each day and use 2 for a simple delta.
    4. This one is fairly easy to get with our current database.
    5. Again this one we can also find but we don't have the data stored.

    I'd also suggest tracking the number of slack users who went from billable = yes to billable = no, and the opposite as it would show users leaving and users returning. Additionally the slack metric for number of days active in the last 30 days.

  3. hollomancer commented on Apr 21, 2019

    @hollomancer
    MemberAuthor

    User churn statistics - We get a lot of that from Slack analytics, but unfortunately it is not exposed in the Slack API that I know of.

    I think that one should be split off into maybe a separate OC project, because I can see a lot of Slack workspaces benefiting from better usage analytics, that are exposed and not hidden behind Slack's API. Might be our first open source 'product'?

  4. apex-omontgomery commented on Aug 17, 2019

    @apex-omontgomery
    Member

    Are the above KPI still the desired goal?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions