Usage metrics API flags telemetry and version gaps

GitHub's Copilot usage metrics API now reports which users are missing client telemetry or running IDEs and Copilot extensions below the minimum supported versions, adding the per-user fields client_telemetry_present and usage_metrics_requirements plus the daily counts missing_client_telemetry_user_count and below_usage_metrics_minimum_user_count. The fields appear in enterprise and organization user reports (1-day and 28-day) and in each day_totals entry of 28-day reports, and are available to enterprise owners, enterprise billing managers, organization owners and custom roles granting the View Copilot Metrics permission, with the Copilot usage metrics policy enabled. GitHub warns that a user can appear in both daily counts and that null or omitted values mean data is unavailable rather than false or zero, so administrators can identify affected users and close reporting gaps without opening a support ticket.

Usage metrics API flags telemetry and version gaps The Copilot usage metrics API now shows which users are missing client telemetry or are running IDE or extension versions below the usage metrics minimums. New per-user fields appear in enterprise and organization user reports, and daily affected-user counts appear in enterprise and organization reports. What’s new whats-new - client telemetry present : Whether client telemetry was received for the user that day. false means Copilot saw the user’s activity, but no usage events arrived from their editor. - usage metrics requirements : Lists each of the user’s IDEs and Copilot extensions as met , unmet , or unknown against the minimum supported versions https://docs.github.com/copilot/concepts/billing-and-usage/copilot-usage-metrics/copilot-metrics supported-ides . - missing client telemetry user count : The number of users that day with client telemetry present set to false . - below usage metrics minimum user count : The number of users that day with at least one IDE or extension below the minimum version. Why this matters why-this-matters Users without client telemetry still count as active, but their reports lack detail such as lines of code, feature breakdowns, and model breakdowns. Common causes include outdated editors or extensions, disabled IDE telemetry, and proxies or firewalls that block events. These fields show how many users are affected and who to follow up with. This way you can close gaps without opening a support ticket. Important notes important-notes - Scope: User fields appear in enterprise and organization user reports 1-day and 28-day . Counts appear in enterprise and organization 1-day reports and in each day totals entry of 28-day reports. - Access: These fields are available to enterprise owners, enterprise billing managers, organization owners, and anyone with a custom organization or enterprise role that grants the View Copilot Metrics permission. The Copilot usage metrics policy must be enabled. - Daily counts: Each count covers a single day. A user can be counted in both missing client telemetry user count and below usage metrics minimum user count , so don’t add the two counts together. Don’t add counts across days to count unique users. - Independent signals: A user can meet every version minimum and still be missing telemetry e.g., they’re behind a proxy . - Unavailable values: Null or omitted values mean the data is unavailable, not false or zero. Days before this release have no values. Visit the Copilot usage metrics API documentation https://docs.github.com/rest/copilot/copilot-usage-metrics to get started.