Contribution analytics | GitLab Docs Skip to main content Go to GitLab Docs homepage What's new? What's new? Get free trial Toggle menu * Use GitLab * GitLab Duo * GitLab Orbit * Extend * Install * Administer * Subscribe * Contribute * Solutions Getting started Tutorials Manage your organization Organize work with projects Plan and track work Manage authentication and authorization Use Git Manage your code Use CI/CD to build your application Secure your application Deploy and release your application Manage your infrastructure Monitor your application Analyze GitLab usage Value streams dashboard Value stream analytics GitLab Duo and SDLC trends DevOps adoption by instance DevOps adoption by group Usage trends Insights Analytics dashboards Issue analytics Merge request analytics Productivity analytics Code review analytics Contribution analytics Contributor analytics Repository analytics for projects Repository analytics for groups CI/CD analytics DORA metrics DORA metrics charts Release notes Feature support Find your GitLab version * GitLab Docs / * Use GitLab / * Analyze GitLab usage / * Contribution analytics Help us learn about your current experience with the documentation. Take the survey . Contribution analytics * Tier : Premium, Ultimate * Offering : GitLab.com, GitLab Self-Managed, GitLab Dedicated 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: * Workload balancing: Analyze your group s contributions over a period of time, and identify group members who are high performers or may benefit from additional support. * Team collaboration: Evaluate the balance of contributions, such as code pushes versus reviews or approvals, to ensure collaborative development practices. * Training opportunities: Identify areas where team members may benefit from mentorship or training, such as low merge request approval or issue resolution rates. * Retrospective evaluation: Incorporate contribution analytics into retrospectives to assess how effectively the team met objectives and where adjustments may be needed. Tracking 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. View contribution analytics To view contribution analytics: * In the top bar, select Search or go to and find your group. * In the left sidebar, select Analyze > Contribution analytics . * Optional. Filter the results: * To view contribution analytics for last week, month, or three months, select one of the three tabs. The selected time period applies to all charts and the table. * To zoom in on a bar chart to display only a subset of group members, select the sliders ( ) below the chart and slide them along the axis. * To sort the contributions table by a column, select the column header or the chevron ( for descending order, for ascending order). * Optional. To view a group member s contributions, either: * On the Contribution analytics bar charts, hover over the bar with the member s name. * In the Contributions per group member table, select the member s name. The member s GitLab profile is displayed, and you can explore their contributions calendar . To retrieve metrics for user contributions, you can also use the GraphQL API . Contribution analytics with ClickHouse 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: * ClickHouse integration guidelines * ClickHouse usage at GitLab * Tracking * View contribution analytics * Contribution analytics with ClickHouse * Facebook * LinkedIn * Twitter * YouTube Company * About GitLab * View pricing * Try GitLab for free Feedback * View page source * Edit in Web IDE * Contribute to GitLab * Suggest updates Help & Community * Get certified * Get support * Post on the GitLab forum Resources * Terms * Privacy statement * Use of generative AI * Acceptable use of user licenses *