GitHub CopilotCode Review User Analytics Now in Usage API

GitHub's usage metrics API now tracks active vs. passive code review users across daily, weekly, and monthly windows. Six new fields help enterprises measure intentional adoption versus policy-driven usage.

GitHub CopilotCode Review User Analytics Now in Usage API

TL;DR

  • Six new fields track active and passive code review user counts in the usage metrics API
  • Daily, weekly, and monthly breakdowns available at enterprise and organization levels
  • Active users (manual requests/suggestions) are counted separately from passive users (policy-triggered)

New

  • Active/passive code review user fields — Six new API fields distinguish between users who manually triggered code reviews versus those auto-triggered by policy, across daily, weekly, and monthly windows
  • Time-window flexibility — Track adoption trends with daily, 7-day, and 28-day aggregations to measure rollout impact

What Changed

  • The usage metrics API now returns six new fields: daily_active_copilot_code_review_users, daily_passive_copilot_code_review_users, weekly_active_copilot_code_review_users, weekly_passive_copilot_code_review_users, monthly_active_copilot_code_review_users, and monthly_passive_copilot_code_review_users
  • Active users = those who manually requested a review or applied a suggestion. When a user has both signals, they count as active only
  • Available in both 1-day and 28-day reports at enterprise and organization levels

Update your API integrations to pull the new fields from the GitHub REST API v2026-03-10.

Source: GitHub Changelog