GitHub Copilot usage metrics

Copilot usage metrics help enterprise administrators and decision-makers understand how their teams are adopting and using Copilot. By tracking usage patterns across the enterprise, you can measure engagement, identify opportunities to increase value, and make data-driven decisions about enablement and rollout.

Metrics are available through:

• The Copilot usage metrics APIs, which provide detailed, user-level data you can export for further analysis.
• The Copilot usage metrics dashboard, which visualizes 28-day usage trends across your enterprise.
• The Copilot usage metrics NDJSON export, which offers raw data for custom BI tools or long-term storage.

For a complete list of available metrics and data fields, see Data available in Copilot usage metrics.

Which usage is included?

The Copilot usage metrics are derived exclusively from telemetry sent by IDEs. In order for an end user to be counted towards these metrics, they must have telemetry enabled in their IDE.

This means the data does not include activity from other Copilot surfaces, such as:

• Copilot Chat on GitHub.com
• GitHub Mobile
• Révision du code Copilot
• Copilot CLI

License and seat management data are not included in Copilot usage metrics reports. To view or manage license assignments, use the Copilot user management API, which is the source of truth for license and seat information. See Points de terminaison d’API REST pour la gestion des utilisateurs Copilot.

Supported IDEs

To be included in the Copilot usage metrics, end users must use one of the following IDEs and Copilot Chat extension versions.

IDE	Minimum IDE version	Minimum Copilot Chat extension version
Eclipse	4.31	0.9.3.202507240902
JetBrains / IntelliJ	2024.2.6	1.5.52-241
Visual Studio	17.14.13	18.0.471.29466
VS Code	1.101	0.28.0
Xcode	13.2.1	0.40.0

Data freshness

The data in the Copilot usage metrics dashboard and API reports is updated on a regular schedule.

During the preview, you can expect data to be available within three full days. This means that data for a given day is processed and made available within three full UTC days after that day closes.

For example, all usage data for a Monday (which closes at midnight UTC) will be visible in the dashboard and API by the end of Thursday UTC. In some cases, such as processing delays over weekends, data may appear up to four calendar days behind the current date.

What does the data measure?

Copilot usage metrics can be grouped into four main categories: Adoption, Engagement, Acceptance Rate, and Lines of Code (LoC) metrics.

Adoption measures how many licensed developers are actively using Copilot within your enterprise. For example, daily active users (DAU) tells you how many unique users interacted with Copilot on a given day. Ideally, you'll see a consistent upward trend in these metrics during rollout.

Engagement measures describe how deeply developers use Copilot once they’ve adopted it. Key engagement metrics show not only frequency of use but also breadth across features. For example, average chat requests per active user measures how often users open and interact with Copilot Chat. You'd want to see regular and increasing chat use across languages and IDEs.

Acceptance rate measures how often developers accept Copilot’s suggestions. This helps you understand whether suggestions are relevant and trusted. For example, a high code completions acceptance rate indicates that suggestions are relevant and useful.

Lines of Code (LoC) metrics measure the number of lines Copilot suggested, added, or deleted in the editor, providing a directional view of Copilot’s tangible output. For example, "Lines added" shows how much code was actually accepted and inserted into the editor.

How can I use these metrics?

These metrics can be used together to answer key questions about your teams' usage of Copilot.

Question	Use these metrics
Are my teams using Copilot regularly?	Daily and weekly active users
Which features deliver the most value?	Requests per chat mode, agent adoption
Do developers trust Copilot’s output?	Acceptance rate trends
Are enablement efforts working?	Growth in adoption and engagement after training or communication campaigns

Look for patterns across these signals rather than focusing on any single number. For example, a steady DAU paired with a rising acceptance rate indicates growing trust and value.

Next steps

Now that you understand what each Copilot metric measures and how to use them, you can explore the dashboard to see these metrics in action.

To learn how to access and interpret these metrics in the Copilot usage metrics dashboard, see Viewing the Copilot usage metrics dashboard.