{"meta":{"title":"Tracking license activation and initial usage with Copilot usage metrics","intro":"Identify and act on GitHub Copilot adoption signals and activation with usage metrics.","product":"GitHub Copilot","breadcrumbs":[{"href":"/en/copilot","title":"GitHub Copilot"},{"href":"/en/copilot/tutorials","title":"Tutorials"},{"href":"/en/copilot/tutorials/roll-out-at-scale","title":"Roll out at scale"},{"href":"/en/copilot/tutorials/roll-out-at-scale/assign-licenses","title":"Assign licenses"},{"href":"/en/copilot/tutorials/roll-out-at-scale/assign-licenses/track-usage-and-adoption","title":"Track usage and adoption"}],"documentType":"article"},"body":"# Tracking license activation and initial usage with Copilot usage metrics\n\nIdentify and act on GitHub Copilot adoption signals and activation with usage metrics.\n\nAfter you assign Copilot licenses across your enterprise, you can use the Copilot usage metrics dashboard and APIs to verify that licenses are active and monitor early usage trends. This helps you evaluate whether your rollout is reaching the right people and take quick action if adoption is slower than expected.\n\nTo get a wider view of adoption, you can combine dashboard insights with qualitative feedback, for example, short pulse surveys or team check-ins.\n\n## Prerequisite\n\nTo access Copilot usage metrics, the **\"Copilot usage metrics\"** policy must be enabled:\n\n* [Managing policies and features for GitHub Copilot in your enterprise](/en/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies#defining-policies-for-your-enterprise)\n* [Managing policies and features for GitHub Copilot in your organization](/en/copilot/how-tos/administer-copilot/manage-for-organization/manage-policies#enabling-copilot-features-and-models-in-your-organization)\n\n## Step 1: Access the usage metrics dashboard\n\n1. Navigate to your enterprise. For example, from the [Enterprises](https://github.com/settings/enterprises?ref_product=ghec\\&ref_type=engagement\\&ref_style=text) page on GitHub.com.\n2. Click the **Insights** tab.\n\nThe dashboard displays aggregated telemetry from developer IDEs and updates daily, though data may be up to 3 days behind UTC.\n\n## Step 2: Track license activation\n\nUse the \"IDE active users\" and \"IDE daily active users\" charts to confirm that developers are starting to use their assigned licenses.\n\n| Metric | What it tells you | How to act |\n| :---------------------- | :-------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------- |\n| IDE active users | How many licensed developers have used Copilot at least once this calendar month. | Compare to your total assigned licenses. If the number is much lower, verify IDE configuration or communicate activation steps to your teams. |\n| IDE daily active users | How many unique users are using Copilot each day. | Look for an upward trend in the first two weeks after rollout. A flat line may signal that users need additional enablement or setup guidance. |\n| IDE weekly active users | Rolling 7-day total of active users. | Use this to track consistency. Steady or increasing WAU indicates successful activation and recurring use. |\n\n> \\[!NOTE]\n> Copilot usage metrics primarily reflect activity in supported IDEs. Server-side telemetry supplements client-side IDE telemetry to surface additional active users. Usage in Copilot Chat on GitHub.com, GitHub Mobile, Copilot code review, or Copilot CLI is not included in dashboard data.\n\n## Step 3: Identify early adoption signals\n\nOnce licenses are active, focus on the metrics that indicate healthy early adoption.\n\n| Signal | Where to find it in the dashboard | What to look for |\n| :-------------------- | :-------------------------------- | :------------------------------------------------------------------------------------------------ |\n| Consistent DAU growth | “IDE daily active users” graph | Steady increase in daily users over the first month. |\n| Feature variety | “Requests per chat mode” graph | Developers trying multiple chat modes (Ask, Edit, Plan, Agent) suggests curiosity and engagement. |\n| Initial agent usage | “Agent adoption” card | Even small agent adoption (5–10%) early on is a positive signal of experimentation. |\n\nHealthy early adoption usually looks like 60–80% of assigned users showing activity within the first month.\n\n> \\[!TIP]\n> These signals show whether developers are trying Copilot, but not whether that usage is deepening into agent-driven workflows. For a cohort-based view of adoption depth, see [Viewing the Copilot impact dashboard](/en/copilot/how-tos/administer-copilot/view-impact-dashboard).\n\n## Step 4: Act on limited adoption signals\n\nIf your metrics show limited adoption, try one of the following strategies.\n\n| Symptom | Possible cause | What to do |\n| :--------------------- | :------------------------------------------------------------------- | :----------------------------------------------------------------------------- |\n| Low total active users | Users haven’t activated licenses or configured Copilot in their IDE. | Re-share onboarding materials or run a short “activation check” session. |\n| Flat daily usage | Developers tried Copilot once but aren’t returning. | Provide enablement resources like Copilot prompts or internal success stories. |\n| No agent usage | Teams may not know about the Copilot agent. | Share examples of advanced use cases to encourage exploration. |\n\nYou can also use Copilot Chat to help diagnose issues. For example:\n\n```copilot copy prompt\nWhat patterns might explain low adoption across some teams in the Copilot metrics export?\n```\n\n## Step 5: Track activation programmatically\n\nNow that you have a sense of what adoption data is available to you and what the data tells you about your rollout, consider using the API to continue monitoring adoption over time.\n\n1. Use the **Enterprise Usage endpoint** to retrieve aggregated data for all organizations in your enterprise.\n2. Filter the export by `day` or `user_login` to identify newly activated users.\n3. Compare `user_initiated_interaction_count` and `code_acceptance_activity_count` to see whether users are actively engaging after license assignment.\n\n## Step 6: Export user-level data for deeper analysis\n\nIn some cases, you may need user-level activity data for deeper analysis or to integrate with internal BI tools. Exports are most useful when you want to analyze long-term trends or correlate adoption with other metrics (for example, productivity or enablement activities).\n\n1. In the dashboard, click ** Export JSON** in the top-right corner.\n2. Download the NDJSON file and use [Copilot Chat](https://github.com/copilot?ref_product=copilot\\&ref_type=engagement\\&ref_style=text) to analyze the data. For example, ask:\n\n ```copilot copy prompt\n * Summarize which organizations show the largest increase in `loc_added_sum` this month.\n * Identify users with high `user_initiated_interaction_count` but low `code_acceptance_activity_count`.\n ```\n\n## Further reading\n\n* [Viewing the Copilot impact dashboard](/en/copilot/how-tos/administer-copilot/view-impact-dashboard)\n* [Reminding inactive users to use their GitHub Copilot license](/en/copilot/tutorials/roll-out-at-scale/assign-licenses/remind-inactive-users)\n* [Driving GitHub Copilot adoption in your company](/en/copilot/tutorials/roll-out-at-scale/enable-developers/drive-adoption)"}