Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'doc/user/admin_area/analytics/user_cohorts.md')
-rw-r--r--doc/user/admin_area/analytics/user_cohorts.md29
1 files changed, 14 insertions, 15 deletions
diff --git a/doc/user/admin_area/analytics/user_cohorts.md b/doc/user/admin_area/analytics/user_cohorts.md
index 1d2d0029860..7adc9ad59a5 100644
--- a/doc/user/admin_area/analytics/user_cohorts.md
+++ b/doc/user/admin_area/analytics/user_cohorts.md
@@ -6,32 +6,31 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Cohorts **(CORE)**
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/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 over time of your GitLab installation.
+you can analyze your users' GitLab activities over time.
-To see User Cohorts, go to **Admin Area > Analytics > Cohorts**.
+To see user cohorts, go to **Admin Area > Analytics > Cohorts**.
## Overview
-How do we read the user cohorts table? Let's take an example with the following
-user cohorts.
+How do you interpret the user cohorts table? Let's review an example with the
+following user cohorts:
![User cohort example](img/cohorts_v13_4.png)
-For the cohort of March 2020, three users have been added on this server and have
-been active since this month. One month later, in April 2020, two users are
-still active. Five months later (August), we can see that one user from this cohort
-is active, or 33% of the original cohort of three that joined in March.
+For the cohort of March 2020, three users were added to this server and have
+been active since this month. One month later (April 2020), two users are still
+active. Five months later (August 2020), one user from this cohort is still
+active, or 33% of the original cohort of three that joined in March.
-The Inactive users column shows the number of users who have been added during
-the month, but who have never actually had any activity in the instance.
+The **Inactive users** column shows the number of users who were added during
+the month, but who never had any activity in the instance.
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).
-- The user visits pages related to Dashboards, Projects, Issues, and Merge Requests ([introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/54947) in GitLab 11.8).
-- The user uses the API
-- The user uses the GraphQL API
+- The user visits pages related to dashboards, projects, issues, or merge
+ requests ([introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/54947) in GitLab 11.8).
+- The user uses the API.
+- The user uses the GraphQL API.