Original announcement: GitHub · 2026-11-06. Read the official announcement.
Summary of GitHub Copilot Metrics API Update
On November 6, 2026, GitHub announced an update to its Copilot usage metrics API. The new features enable identification of users whose client telemetry is missing or whose IDE or Copilot extension versions fall below required minimums. This enhancement targets enterprise and organization reports, providing more detailed insights into usage data quality and version compliance.
What Has Changed?
The update introduces new per-user fields and daily user counts in the metrics API:
client_telemetry_present: Indicates whether telemetry was received from the user’s client on a given day. If false, Copilot activity was detected but without telemetry events arriving from the editor.usage_metrics_requirements: Details each user’s IDEs and Copilot extensions, marking them as met, unmet, or unknown against minimum supported versions.missing_client_telemetry_user_count: Counts daily users lacking telemetry data.below_usage_metrics_minimum_user_count: Counts daily users running an IDE or extension version below the supported minimum.
Who Should Care?
Enterprise owners, billing managers, organization owners, and roles with permission to view Copilot metrics should find this update valuable. It helps them understand why some users, while active, lack detailed usage insights such as lines of code or feature usage breakdowns. This is crucial for accurate reporting, auditing, and proactive troubleshooting.
Developers and teams will also benefit indirectly by ensuring their IDEs and Copilot extensions remain updated and telemetry is enabled, thereby improving feature insights and support.
Why This Matters
Users without client telemetry still count as active but generate incomplete reports. Common reasons include:
- Outdated IDEs or Copilot extensions.
- Disabled IDE telemetry settings.
- Network configurations like proxies or firewalls blocking telemetry events.
The new metrics provide actionable signals identifying how many users are impacted and which need follow-up, allowing enterprises to address gaps without submitting support tickets.
Next Steps for Developers and Organizations
To leverage the new data, organizations and enterprises should:
- Verify that the Copilot usage metrics policy is enabled.
- Examine daily reports focusing on the new telemetry and version minimum fields.
- Identify users with
client_telemetry_presentset to false or those below version minimums. - Communicate with affected users to update IDEs and extensions and ensure telemetry is enabled.
- Understand that counts are daily snapshots; do not sum counts across days or combine different counts indiscriminately.
- Refer to the Copilot usage metrics API documentation for detailed integration and interpretation guidance.
Important Considerations
- Null or missing field values indicate unavailable data, not negative results.
- A user may have compliant versions yet still miss telemetry due to network or configuration issues.
- Users can be counted in both missing telemetry and version gap categories simultaneously.
