← Claude Docs

Track team usage with analytics - Claude Code Docs

Claude Docs · April 30, 2026
Claude Code provides analytics dashboards for Teams, Enterprise, and API customers to track developer usage patterns, contribution metrics, and engineering velocity impact. The dashboards display metrics including lines of code accepted, suggestion acceptance rates, daily active users, and pull request data, with Teams and Enterprise plans also offering GitHub integration for contribution tracking and a leaderboard of top contributors. Organizations can use the analytics to demonstrate ROI, monitor adoption trends, identify power users, and access attribution data that determines which code was written with Claude Code assistance.

Detailed Analysis

Anthropic has introduced a dedicated analytics dashboard for Claude Code, its AI-powered coding assistant, designed to give engineering organizations granular visibility into how their teams interact with the tool and how it affects development output. Available at `claude.ai/analytics/claude-code` for Teams and Enterprise subscribers, and at `platform.claude.com/claude-code` for API Console users, the dashboard surfaces a range of metrics spanning adoption, productivity, and code contribution — all accessible to admins and owners without requiring custom instrumentation. Core measurements include daily active users, session counts, suggestion accept rates, and lines of code accepted, providing a baseline portrait of engagement that teams can monitor over time.

The more sophisticated layer of the dashboard involves contribution metrics, which require integration with a GitHub organization and offer a direct link between Claude Code usage and shipping activity. Once the GitHub app is installed, the system retroactively analyzes merged pull requests by extracting added lines from PR diffs, matching them against Claude Code session outputs using file-level and content-level comparison, and labeling qualifying PRs as `claude-code-assisted` directly in GitHub. Attribution follows conservative standards — only lines with high-confidence Claude Code involvement are counted, and code that has been substantially rewritten (more than 20% divergence) is excluded from attribution. Auto-generated files such as lock files, build artifacts, and minified outputs are also filtered out, ensuring that reported metrics reflect genuine developer productivity rather than machine-generated boilerplate. The 21-day attribution window — spanning from three weeks before to two days after a PR merge — accommodates realistic development timelines where AI-assisted code may sit in feature branches for extended periods before landing.

The leaderboard and data export capabilities signal that Anthropic is positioning Claude Code analytics not merely as a passive monitoring tool but as an active lever for engineering management. The leaderboard ranks the top 10 contributors by PR count or lines of code with Claude Code assistance, enabling organizations to identify power users who can serve as internal advocates or trainers. The full-team CSV export extends this capability beyond the dashboard's visual constraints, allowing engineering leaders to pipe data into existing BI systems, correlate it with sprint velocity, or build custom ROI models. The PRs-per-user chart — which divides merged PRs by daily active users — is a deliberate nod to DORA-style productivity frameworks, framing Claude Code's impact in the language of engineering performance that resonates with CTOs and VPs of Engineering rather than individual developers.

This release reflects a broader industry pattern in which AI coding tools are moving from individual productivity experiments to organization-wide managed deployments with accountability mechanisms. GitHub Copilot introduced similar enterprise analytics in 2023, and JetBrains AI Assistant has followed with comparable instrumentation, establishing analytics as a baseline expectation for any enterprise-grade AI development tool. Anthropic's approach is notable for its integration depth — embedding attribution labels directly into GitHub, supporting GitHub Enterprise Server alongside GitHub Cloud, and offering OpenTelemetry export for teams that need per-user token costs piped into observability platforms like Datadog. This interoperability signals that Anthropic is targeting organizations with mature DevOps practices that will resist siloed analytics portals in favor of consolidated observability stacks.

The feature set also underscores the growing importance of justifying AI tooling expenditure at the organizational level, particularly as multi-seat Claude for Teams and Enterprise contracts represent meaningful recurring costs. By surfacing metrics that can be mapped to concrete engineering outputs — merged PRs, lines of code shipped, acceptance rates — Anthropic provides procurement and finance stakeholders with the inputs needed for ROI calculations, reducing the ambiguity that has historically made AI tooling difficult to defend in budget reviews. The conservative attribution methodology, while potentially undercounting Claude Code's actual contribution, reflects a deliberate decision to prioritize credibility over inflated metrics, a posture that serves long-term enterprise trust even if it understates short-term impact figures.

Read original article →