GitHub Copilot Integration Guide

Last updated: February 4, 2026

Overview

Span's GitHub Copilot integration provides comprehensive insights into your organization's AI-assisted coding activity. By connecting GitHub Copilot to Span, you can track adoption rates, measure engagement, and understand how developers use AI coding assistance across your teams.

What Data Does Span Collect?

The GitHub Copilot integration tracks two primary data streams:

Copilot Seat Assignments

  • Which developers have been assigned Copilot licenses

  • When each seat was created and last updated

  • Last activity date for each user

  • Seat assignment status

Copilot Usage Metrics

Daily aggregated metrics including:

  • Active vs. Engaged Users: Distinguish between users with assigned seats and those actively using Copilot

  • Code Completions: Lines of code accepted from Copilot suggestions, broken down by:

    • Editor (VS Code, JetBrains, Visual Studio, etc.)

    • Programming language (Python, JavaScript, TypeScript, etc.)

    • AI model used

  • Copilot Chat: Chat interactions across different editors

  • PR Summaries: Copilot-generated pull request summaries via GitHub.com

  • Dotcom Chat: GitHub.com Copilot chat usage by model

Prerequisites

Before connecting GitHub Copilot to Span, ensure you have:

  1. GitHub App Integration: Your GitHub organization must already be connected to Span 

  2. GitHub Copilot Business or Enterprise: The integration requires GitHub Copilot Business or Enterprise subscription 

  3. Required Permissions: The Span GitHub App needs GitHub Copilot Business organization permissions (read) 

Setup Instructions

Step 1: Navigate to Integrations Settings

  1. Go to Settings > Integrations in Span

  2. Locate the GitHub Copilot card among your AI Tools integrations

Step 2: Enable the Copilot Integration

  1. Click Connect on the GitHub Copilot card

  2. A dialog will appear confirming you want to enable GitHub Copilot tracking

  3. Important: Before clicking "Connect," verify that your Span GitHub App has the required permission:

    • GitHub Copilot Business organization permissions (read)

  4. Click Connect to enable the integration

Step 3: Update GitHub App Permissions (if needed)

If you haven't already granted Copilot permissions to the Span GitHub App:

  1. Go to your GitHub organization settings

  2. Navigate to Third-party Access > GitHub Apps

  3. Find the Span app and click Configure

  4. Under Organization permissions, find Copilot

  5. Set the permission to Read-only

  6. Save your changes

Step 4: Wait for Initial Data Sync

After enabling the integration:

  • Span will begin syncing your Copilot seat assignments and usage metrics

  • Initial sync may take up to 6 hours to complete

  • Historical data will be backfilled automatically (up to your organization's data retention settings)

What Metrics Are Available?

Once connected, Span provides insights across several dimensions:

Adoption Metrics

  • Weekly/Monthly Active Users: Developers using Copilot each week or month 

  • Active User Ratio: Percentage of developers using Copilot vs. total active developers

  • Seat Utilization: Assigned seats vs. actively engaged users

Usage Metrics

  • Total Active AI Days: Days with active Copilot usage per developer

  • Coding Days per Active Developer: AI-assisted coding frequency 

  • Active Users: Count of developers using Copilot within a time period

Viewing Your Copilot Data

AI Tools Dashboard

Navigate to Insights > AI Transformation > Adoption to see:

  • Overview charts showing adoption trends over time

  • Breakdown tables by team, individual, or developer tool

  • Comparative analytics between Copilot and other AI coding tools (Cursor, Claude Code, etc.)

Key Features

  1. Time-based Analysis: View metrics across custom date ranges

  2. Team Breakdown: Understand Copilot adoption by team or department

  3. Individual Insights: Drill down to see individual developer engagement

  4. Benchmarking: Compare your teams against organizational benchmarks (when available)

  5. CSV Export: Download detailed metrics for external analysis

Data Freshness and Sync Schedule

  • Sync Frequency: Copilot data syncs every 4 hours

  • Freshness SLA: Data should be no more than 6 hours old

  • Incremental Updates: Only new or changed data is synced after initial backfill

Important Notes

Code Lines Metrics Limitation

GitHub Copilot seat assignment data does not include detailed lines-of-code metrics at the individual developer level. The integration tracks:

  • ✅ Who has Copilot and when they last used it

  • ✅ Organization-wide code completion totals by editor and language

  • ❌ Not available: Individual developer's lines of code accepted from Copilot

For more granular per-developer code contribution tracking, consider the Span Events API or OpenTelemetry integration for tools that support it.

GitHub API Limitations

  • Copilot Metrics API provides data in 28-day windows maximum

  • Historical data before enabling the integration may be limited to GitHub's retention policies

  • Metrics are aggregated at the organization level, not per-repository (except for PR summaries)

Troubleshooting

"GitHub Copilot not enabled" Error

Cause: Your organization doesn't have GitHub Copilot Business or Enterprise, or the feature is disabled.

Solution:

  1. Verify your GitHub subscription includes Copilot Business/Enterprise

  2. Ensure Copilot is enabled in your GitHub organization settings

  3. Contact your GitHub account administrator

Missing Data or "No users found"

Cause: No developers in Span are mapped to GitHub Copilot users.

Solution:

  1. Ensure GitHub user emails match the email addresses in Span

  2. Check that developers are properly synced from your HRIS or Identity Provider

  3. Verify the GitHub integration is syncing user data correctly

Permission Denied Errors

Cause: The Span GitHub App lacks the required Copilot read permissions.

Solution:

  1. Re-authorize the Span GitHub App with updated permissions

  2. Follow the steps in Step 3: Update GitHub App Permissions above

  3. Contact Span support if issues persist

Disconnecting the Integration

To disable Copilot tracking:

  1. Navigate to Settings > Integrations

  2. Click on the GitHub Copilot card

  3. Click Disconnect in the dialog

  4. Confirm your action

Note: Historical data will be retained according to your data retention settings, but no new Copilot data will be synced.

Privacy and Security

  • Data Encryption: All Copilot metrics are encrypted in transit and at rest

  • Access Control: Only users with appropriate permissions can view Copilot analytics

  • No Code Content: Span does not collect the actual code written or suggested by Copilot

  • User Mapping: GitHub usernames are mapped to Span user accounts via verified email addresses

Getting Help

If you need assistance with the GitHub Copilot integration:

  • In-app Support: Click the help icon in Span to contact support

  • Contact: Reach out to your Customer Success Manager

Frequently Asked Questions

Q: Can I see which specific code was generated by Copilot?
A: No, Span tracks usage metrics and aggregated statistics, but does not collect or analyze the actual code content.

Q: How does Span calculate "engaged users" vs. "active users"?
A: Active users have assigned Copilot seats, while engaged users actively used Copilot features (completions, chat, etc.) during the measured period.

Q: Can I compare Copilot to other AI tools?
A: Yes! Span's AI Tools dashboard provides side-by-side comparisons of Copilot, Cursor, Claude Code, and other integrated AI coding assistants.

Q: What happens to my data if I disconnect the integration?
A: Historical metrics are retained according to your organization's data retention policy, but no new data will be collected after disconnection.

Q: Does this integration affect my GitHub Copilot performance?
A: No, Span reads usage data through GitHub's APIs and has no impact on Copilot's functionality or performance.

Last Updated: February 2026