cd /news/ai-products/copilot-usage-metrics-api-adds-cohor… · home topics ai-products article
[ARTICLE · art-18123] src=github.blog pub= topic=ai-products verified=true sentiment=↑ positive

Copilot usage metrics API adds cohorts for AI adoption

GitHub's Copilot usage metrics API now classifies each engaged user into one of four AI adoption phases—Code first, Agent first, Multi-agent, or No cohort—based on their Copilot surface usage over a rolling 28-day window. The new `ai_adoption_phase` field on user-level reports and `totals_by_ai_adoption_phase` array on enterprise- and organization-level reports provide per-phase engagement and activity metrics. This update enables administrators to track cohort progression and target enablement efforts beyond simple active-user counts.

read2 min publishedMay 29, 2026

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](https://docs.github.com/copilot/concepts/copilot-usage-metrics)through the REST API. - You can use this release in combination with the
[teams filter](https://github.blog/changelog/2026-05-14-team-level-copilot-usage-metrics-now-available-via-api/)ship for greater granularity.

Join the discussion within GitHub Community.

── more in #ai-products 4 stories · sorted by recency
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/copilot-usage-metric…] indexed:0 read:2min 2026-05-29 ·