doc/user/group/contribution_analytics/_index.md
{{< details >}}
{{< /details >}}
Contribution analytics provide an overview of the contribution events your group's members made in the last week, month, or three months. Interactive bar charts and a detailed table show contribution events (push events, issues, and merge requests) by group member.
Use contribution analytics to get insights into team activity and individual performance, and use this information for:
Contribution analytics are based on push events, because they provide a more reliable view of contributions than unique commits. Counting unique commits may lead to duplication when commits are pushed across multiple branches. By tracking push events instead, GitLab ensures that every contribution is counted accurately.
For example, a user pushes three commits to branch A in one push. Later, the user pushes two of those commits from branch A to branch B. GitLab records five commits, though the user made three unique commits.
To view contribution analytics:
In the top bar, select Search or go to and find your group.
Select Analyze > Contribution analytics.
Optional. Filter the results:
Optional. To view a group member's contributions, either:
To retrieve metrics for user contributions, you can also use the GraphQL API.
On GitLab.com, contribution analytics run through the ClickHouse Cloud cluster.
On GitLab Self-Managed, when you configure the ClickHouse integration, the ClickHouse events table is automatically populated from the PostgreSQL events table. This process might take some time for large installations. After the table is fully synchronized, new events become available in ClickHouse with a delay of about three minutes.
For more information, see: