Our GitHub integration can also import your GitHub Copilot usage metrics: how many developers use Copilot, where they use it (IDE completion, chat, agent mode, command line, code review), which models and languages they use, and how much of the suggested code they accept.
These metrics are exposed on Keypup as the AI Usage dataset, and can be reported next to your pull request and issue metrics. For example, compare the cycle time of developers who use Copilot daily with those who do not.
We do not fetch your code or your prompts. GitHub publishes Copilot usage as daily counts - interactions, suggestions, accepted lines, tokens - and that is all Keypup retrieves.
Prerequisites
Copilot metrics are only available for GitHub organizations on GitHub Cloud. They do not exist for personal accounts, and are not available on GitHub Enterprise Server.
Two things must be true on GitHub before Keypup can import them.
1. The GitHub user connected to Keypup can read Copilot metrics
Keypup reads Copilot metrics with the GitHub account used to connect GitHub to Keypup. That account must be either:
an owner of the organization, or
a member holding a custom organization role that includes the View organization Copilot metrics permission.
The second option gives access to the metrics without making someone an organization owner. See GitHub's documentation on creating a custom organization role and the permissions a custom role can include.
Keypup must also have been granted access to the organization itself. If the organization's repositories do not appear on Keypup either, start with Grant Keypup access to specific GitHub organizations.
2. Copilot usage metrics are enabled for the organization
GitHub only records and publishes Copilot usage when the Copilot usage metrics policy is enabled. It is set in the organization settings, under Code, planning, and automation > Copilot > Policies. See GitHub's documentation on managing Copilot policies in your organization.
If your organization belongs to an enterprise, the enterprise owner may control this policy instead, and the organization cannot override it. In that case the policy must be enabled in the enterprise's Copilot policies, either everywhere or for your organization. See managing Copilot policies in your enterprise.
Developers should keep telemetry enabled in their IDE. GitHub builds most Copilot metrics from IDE telemetry, so a developer who has turned it off appears with little or no IDE activity. See GitHub's overview of Copilot usage metrics.
How the import works
Keypup detects the metrics on its own. Once a day, Keypup checks whether the Copilot metrics of each connected organization are readable. When they are, a project named Copilot Metrics (<your organization>) appears in your list of GitHub projects. Enable it like any repository to start the import.
Because the check runs once a day, the project can take up to a day to appear after you have met the prerequisites above.
Three reports are imported. GitHub publishes one Copilot report per day at three levels, and each becomes a set of records in the AI Usage dataset. The level is recorded in the Aggregation level field:
Per developer (
USER): each developer's activity, broken down by surface, model, language and IDE.Per repository (
REPOSITORY): in each repository, the pull requests Copilot created or reviewed, how many of the ones it created were merged, and how many of its code review suggestions were applied.Organization-wide (
ORGANIZATION): one total per day for the whole organization.
History. The first import retrieves up to one year of history. GitHub does not publish organization metrics from before 12 December 2025, so nothing older is available. A first import walks the history one day at a time, so it can take a few hours to complete.
Freshness. GitHub publishes each day's metrics about three days later, so the most recent three days are always missing. Keypup refreshes the metrics once a day. GitHub can still revise a day after publishing it, so every refresh also re-reads the last 35 days and updates any figure that has changed.
Do not add up several organizations. GitHub attributes a developer's Copilot usage to every organization they are a member of, not to the one where the work happened. A developer in two organizations appears in both, with the same activity. Report each organization separately, or filter on one.
For what GitHub does and does not publish - no token counts for IDE work, for example - see AI Usage provider coverage.
Troubleshooting
The Copilot Metrics project does not appear. Check both prerequisites above for the GitHub account connected to Keypup, then allow up to a day for the next check.
The Copilot Metrics project shows a warning. GitHub has stopped letting Keypup read the metrics - usually because the policy was disabled or the connected account lost its role. Keypup keeps the project and the data already imported, and tries again once a day. Restore the policy or the role and the import resumes on its own. You do not need to reconnect GitHub.