GitHub Copilot Integration Guide

Last updated: October 27, 2026

Span's GitHub Copilot integration reads your organization's Copilot seat list and GitHub's per-user daily usage report, so you can see who uses Copilot, how often, and what it costs, next to your other AI tools.

Why it matters

  • Adoption in one place: compare Copilot with Cursor, Claude Code, and other tools on the same Tool utilization page.

  • Per-person and per-team views: see weekly and monthly active users, AI days per week, and accepted lines by team or person.

  • Spend: Copilot seat cost and AI credit usage feed the AI Spend report.

How it works

Once you turn on the integration, Span syncs two kinds of data for each GitHub organization:

  • Seat assignments: who holds a Copilot seat, the seat's plan type, and the seat's last activity date.

  • Per-user daily usage report: for each person and day, lines added and deleted, AI credits used, and whether they used agent mode, chat, or the CLI.

Span uses that data for these metrics:

Metric

How Copilot data feeds it

Weekly / Monthly active users and their ratio

A person counts as active on any day they appear in GitHub's per-user usage report. Span rolls those days into 7-day and 30-day windows.

AI days / week

Days the person appears in the usage report, per eligible coding day, × 7.

Accepted lines of code

Lines added plus lines deleted from the per-user usage report.

Base spend

Each active seat's plan price, prorated per day: Business $19, Enterprise $39 per developer per month.

Overage spend

AI credits used × $0.01, shown under the model "copilot".

Span matches Copilot data to people by GitHub username. There is no email fallback.

View the data under AI Effectiveness → AI insights → Tool utilization (choose Copilot in the tool selector) and AI Effectiveness → AI spend.

Setup

Before you start: your GitHub organization is connected to Span, and you have GitHub Copilot Business or Enterprise.

  1. Grant the permission in GitHub. In your GitHub organization settings, go to Third-party Access → GitHub Apps, find the Span app, and click Configure. Under Organization permissions, set Copilot to Read-only, then save.

  2. Turn on the switch in Span. Go to Settings → Integrations, open your GitHub connection, and turn on the GitHub Copilot switch. Do this for each GitHub connection whose Copilot data you want.

  3. Check usernames. Make sure each developer's GitHub username is on their Span person record.

  4. Wait for the first sync. The first sync can take up to 6 hours. After that, Copilot data syncs every 4 hours.

  5. Optional: set the billing date. Under Settings → Integrations → AI Spend Integration Settings, set the Copilot billing date. Copilot pricing comes from each seat's plan type and isn't editable.

To stop syncing, turn off the GitHub Copilot switch on the GitHub connection. Span stops collecting new Copilot data.

Things to know

  • Business and Enterprise only. Individual Copilot seats aren't visible to the organization API.

  • History starts October 10, 2025. GitHub's per-user usage report has no earlier data, and it covers days through yesterday (UTC).

  • Active means present in the report. Any appearance in GitHub's per-user report for a day counts as use that day, however small.

  • Unused seats add no base spend. Span books seat cost only for seats with activity in the billing period. Span doesn't report a count of idle seats.

  • List price only. Copilot base spend uses $19 or $39 per seat. Negotiated discounts don't apply.

  • No per-model split. GitHub reports AI credits without a model breakdown, so all Copilot overage shows as "copilot".

  • Overage won't match GitHub billing exactly. The usage report is a usage signal, not an invoicing total.

  • Copilot coding agent is tracked separately. Pull requests that carry "Co-authored-by: Copilot" are detected from your pull requests and appear as Async Copilot, with no setup.

  • No code content. This integration reads seat and usage data only, not the code Copilot wrote or suggested.

  • Worked example. Your organization has 30 Copilot Business seats with billing day 1. In June (30 days), 24 seats show activity from June 1 and 6 show none. Base spend is 24 × $19 = $456; the 6 idle seats add $0. Those 24 people used 12,000 AI credits in June, so overage is 12,000 × $0.01 = $120. Copilot total for June: $576.

Troubleshooting

  • No Copilot data for anyone: confirm the Span GitHub App has the Copilot read permission, the GitHub Copilot switch is on, and your plan is Business or Enterprise.

  • Some people missing: open the Integrations status on the Tool utilization page and select Copilot. People in Missing usually need their GitHub username added; usernames in Unknown don't match anyone in Span.

Related articles

AI Tool Adoption Report

AI Tool Spend Report

Why AI tool or Spend data might be missing for a person

Understanding Accepted AI Lines vs. All Merged Lines

Need help?

Contact your Span account team or reach out to support@span.app.