← AI PulseJul 28, 2026

Policy · news · Single-source brief

GitHub Expands Copilot App Usage Metrics in API Reports

GitHub has expanded the reporting of Copilot app usage metrics within its Copilot usage metrics API, attributing individual Copilot app activity to users in enterprise-user and organization-user reports.

By Illumora Editorial

Source · Jul 28, 2026, 11:35 PM · On Illumora · Jul 28, 2026, 11:47 PM

Media from the primary source — shown here so you can stay on Illumora.

Rewritten from one allowlisted primary — not independent enterprise reporting. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →GitHub Changelog (Copilot) — GitHub Copilot app usage metrics now expand across report rollups - GitHub Changelog
Save

GitHub has updated its Copilot usage metrics API to provide more granular data for Copilot app activity. This expansion means that individual Copilot app usage is now attributed to specific users within enterprise-user and organization-user reports. Previously, Copilot app usage was visible only as a standalone total at the enterprise and organization levels.

Key Points

  • Individual Copilot app activity is now attributed to users in enterprise-user and organization-user reports.
  • Copilot app coding activity is now broken out in feature, model, and language rollups alongside other Copilot surfaces.
  • The used_copilot_app metric indicates if a user was active in the Copilot app on a given day.
  • A totals_by_copilot_app section provides session_count, request_count, prompt_count, and a token usage breakdown including output_tokens_sum, prompt_tokens_sum, and avg_tokens_per_request.
  • Copilot app activity now appears in totals_by_feature, totals_by_model_feature, totals_by_language_feature, and totals_by_language_model.
  • Top-level code generation, code acceptance, lines added, and lines deleted totals now include Copilot app activity.
  • The daily_active_users metric now counts users who were active only in the Copilot app.

Context

According to GitHub, these changes build on an earlier release that integrated the Copilot app into the usage metrics API with enterprise-level totals. The expanded metrics allow administrators to identify Copilot app adopters and measure the code generated by the Copilot app. The update also enables comparison of Copilot app usage against other surfaces such as the IDE, chat, code review, and coding agent using existing fields.

Why It Matters

This update provides enterprise owners, billing managers, organization owners, and those with the View Copilot Metrics permission with more detailed insights into Copilot app adoption and impact. It allows for a more comprehensive understanding of how Copilot is utilized across different user groups and coding contexts within an organization, provided the Copilot usage metrics policy is enabled.

What To Do

  • Visit the Copilot usage metrics API documentation to understand the new data points.
  • Review enterprise-user and organization-user reports for the used_copilot_app and totals_by_copilot_app sections.
  • Examine feature, model, and language rollups to see Copilot app activity alongside other Copilot surfaces.
  • Note the inclusion of Copilot app activity in daily_active_users and code activity metrics like lines added and deleted.