From 4d196847d6f49df2fbda0c1fc60122b4e8f63ea2 Mon Sep 17 00:00:00 2001 From: Achilleas Pipinellis Date: Thu, 20 Apr 2017 10:30:56 +0200 Subject: [PATCH] Small refactoring of the user cohorts docs --- doc/user/admin_area/user_cohorts.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/doc/user/admin_area/user_cohorts.md b/doc/user/admin_area/user_cohorts.md index 1671487bc8c0c3..c17c6e8103c088 100644 --- a/doc/user/admin_area/user_cohorts.md +++ b/doc/user/admin_area/user_cohorts.md @@ -1,13 +1,14 @@ # Cohorts -> **Notes:** -- [Introduced][ce-23361] in GitLab 9.1. +> [Introduced][ce-23361] in GitLab 9.1. As a benefit of having the [usage ping active](settings/usage_statistics.md), GitLab lets you analyze the users' activities of your GitLab installation. Under `/admin/cohorts`, when the usage ping is active, GitLab will show the monthly cohorts of new users and their activities over time. +## Overview + How do we read the user cohorts table? Let's take an example with the following user cohorts. @@ -19,12 +20,13 @@ active. Two months later, 139 users (or 85%) are still active. 9 months later, we can see that only 6% of this cohort are still active. How do we measure the activity of users? GitLab considers a user active if: + * the user signs in * the user has Git activity (whether push or pull). -### Setup +## Setup -1. Activate the usage ping as defined [in the documentation](settings/usage_statistics.md) +1. [Activate the usage ping](settings/usage_statistics.md) 2. Go to `/admin/cohorts` to see the user cohorts of the server [ce-23361]: https://gitlab.com/gitlab-org/gitlab-ce/issues/23361 -- GitLab