Copilot usage metrics API adds cohorts for AI adoption
GitHub's Copilot usage metrics API now classifies users into four AI adoption phases based on their feature usage over a 28-day rolling window, enabling deeper tracking of adoption maturity. The new ai_adoption_phase field and aggregated metrics per phase help administrators tailor enablement strategies.
Back to changelog
To help you tell a deeper Copilot adoption story—not just who is active, but how they’re using Copilot—the Copilot usage metrics API now classifies each engaged user into an AI adoption phase based on their Copilot product usage over a rolling 28-day window. A new ai_adoption_phase field is available on user-level reports, and a new totals_by_ai_adoption_phase array surfaces per-phase metrics on enterprise- and organization-level reports.
What’s new
Each engaged user is assigned to one of four phases based on the Copilot surfaces they’ve used on at least two days in the last 28-day window:
Phase 0 — No cohort: User did not meet the engagement criteria for any phase.
Phase 1 — Code first: User engaged with code completion and/or IDE agent mode.
Phase 2 — Agent first: User engaged with a single GitHub-based agent surface (i.e., Copilot cloud agent, Copilot code review, or Copilot CLI).
Phase 3 — Multi-agent: User engaged with two or more GitHub-based agent surfaces, or with the new GitHub Copilot app.
Each ai_adoption_phase value includes a version field (starting at v1) so the classification logic can evolve as Copilot’s product surface grows, without breaking historical context.
On the enterprise- and organization-level reports, the new totals_by_ai_adoption_phase array groups engagement and activity metrics by phase, including:
Total engaged users (2-day-in-28 engagement window)
User-initiated interaction average
Code generation and acceptance activity averages
Lines of code added and deleted averages
Pull requests created, merged, and reviewed averages
Median time-to-merge average
Aggregated metrics report the average per user within each phase rather than the sum.
Why this matters
Tell the maturity story: Move beyond simple active-user counts and show which Copilot capabilities your developers are actually adopting.
Track cohort progression: Watch users graduate from code-first usage into agent-first and multi-agent workflows over time.
Target enablement: Focus training, documentation, and rollout programs on the phases where you see the biggest opportunity.
Important notes
These metrics are available to enterprise administrators and organization owners who have access to Copilot usage metrics through the REST API.
You can use this release in combination with the teams filter ship for greater granularity.
Join the discussion within GitHub Community.
May.26 Improvement
Copilot Memory has more controls for deletion, scope, and the Copilot CLI
copilot
May.26 Release
GitHub Code Quality: Repository Enablement API
application security enterprise management tools
May.26 Improvement
Target Copilot models to organizations with model rules
copilot enterprise management tools
May.21 Release
GitHub Copilot for Eclipse is open source
copilot
May.20 Improvement
Copilot usage metrics reports now use GitHub-owned download URLs
account management copilot
May.20 Retired
Updates to available models in Copilot on web
copilot
May.20 Improvement
Auto model selection now routes based on your task in VS Code
copilot
May.20 Release
Semantic issue search in Copilot Chat
copilot projects & issues
Back to top