Claude adoption

The Claude adoption report measures daily, weekly, and monthly adoption of Claude products and feature utilization across your organization. Use this report to track rollout progress, compare product usage, and identify unused licenses.

Note: Claude adoption requires at least one connected Claude data source: Claude Code (Anthropic Console), Claude Code (Enterprise), or Claude Code (OTEL).

Claude adoption report in DX

When to use Claude adoption

Claude adoption answers the question: Who is using Claude, which products are they using, and how is adoption changing over time?

This report helps teams:

  • Track rollout progress — Measure adoption rates across your organization as you roll out Claude to more teams.
  • Compare products — See how adoption of Claude Code, Cowork, and other Claude products differs across the organization.
  • Identify power users and champions — Find active Claude users who can help others adopt best practices.
  • Optimize license spend — Spot unused licenses that can be reallocated or followed up on.
  • Understand feature utilization — See which Claude Code tools and skills teams use most and where they could expand usage.

Product filter

The report includes all Claude products reported by your connectors. Use the Product filter to scope every tab to a single product. The filter appears when product attribution is available and lists the products and categories present in your data:

  • Claude Code — Combines usage from the terminal and the Code tab in the Claude Desktop app.
  • Chat and Cowork unified — Usage from Anthropic’s combined Chat and Cowork experience, listed separately from Claude Chat and Cowork.
  • Cowork, Claude Tag, Claude Design, Claude in Chrome, Claude Chat, Office Agent — Available when your connected sources provide usage for them.
  • Claude Other — Historical OTel usage recorded before product attribution was available, plus usage with missing, blank, or unrecognized product information. These records are combined under one label and are not assigned to Claude Code.

DX uses the product information provided by each connection. Different names for the same product are combined under one label. Usage in Claude Other remains included in All products.

Product breakdowns currently come from the Claude Code (OTel) connector. The Anthropic Console and Enterprise connectors currently report imported token and cost data as Claude Code. A product appears in the filter only when your connected sources provide usage for it. For historical usage and product attribution, see How does DX report usage across Claude products?.

Metric availability by product

Acceptance rate, Lines of code, Tool usage, and Skill usage measure Claude Code activity. These cards appear only when you select Claude Code or All products. For other products, the report hides the cards and names the unavailable metrics in a note.

With All products selected, these metrics include Claude Code usage and historical OTel usage recorded before product attribution was available, labeled Claude Code + historical. Newer usage with missing, blank, or unrecognized product information is excluded from these metrics. Adoption and token metrics cover every product.

Historical usage remains attributed to Claude Other. Its feature metrics are available under All products; selecting Claude Other keeps these cards hidden. The same rules apply to lines of code in Power users and code metrics in Breakdowns.

Adoption

The Adoption tab displays adoption trends over time and provides a breakdown by team.

  • Active contributors — Adoption is measured as the percentage (or total count) of contributors actively using Claude. Toggle between Percent and Total views, and switch between two population scopes:

    • Contributors — DX users assigned to a team
    • Licensees — Claude license holders
  • DAU, WAU, MAU — Use the activity period dropdown to view daily, weekly, or monthly active users.

  • Team breakdown — A table below the main chart shows adoption metrics by team.

DX counts a contributor as active for a day if they appear in the Claude usage report with any metric greater than zero, such as lines of code added or removed. With a product selected, only activity attributed to that product counts. The denominator remains your full contributor or licensee population.

Active user counts in DX can be higher than in the Anthropic Console, which only counts users with at least one new session (num_sessions > 0) that day. Session counts increase only at startup, so a user with a multi-day session can have activity without starting a new session. DX includes that activity.

Usage

The Usage tab shows model usage and Claude Code feature utilization.

  • Acceptance rate — Tracks how often Claude Code’s suggested edits are accepted. Calculated as accepted edits divided by total suggested edits, counting the Edit, Multi-Edit, Write, and Notebook Edit tools.

  • Lines of code — Shows lines of code added and removed by Claude Code as a stacked bar chart over time.

  • Skill usage — Shows which skills are activated most often. Requires the Claude Code (OTEL) connector.

  • Model usage — Shows which AI models teams use most frequently as a stacked bar chart over time.

  • Tool usage — Shows how developers use different Claude Code tools:

    • Existing file edits — Edit and Multi-Edit tools
    • New files — Write tool
    • Jupyter notebook edits — Notebook Edit tool
  • Breakdowns — A per-team table showing acceptance rate, lines of code, and top model. The acceptance rate and lines of code columns follow the same metric availability rules as the cards.

Power users

The Power users tab identifies the most active Claude users across your organization. The table shows name, login, and total tokens, sorted by total tokens within the selected time period. Lines of code appear when Claude Code or All products is selected and are hidden for other products. Use filters to narrow results (up to 500 users shown).

Unused licenses

The Unused licenses tab shows licenses with no usage within the selected time period. The table displays name, login, and last active date (up to 500 users shown). Use it to identify licenses to reallocate or people to follow up with.

With a product selected, a license counts as unused when the person had no usage attributed to that product in the period, even if they used another Claude product.

AI cost management

To analyze Claude token cost, use the AI cost management report. It shows Claude spend alongside other connected AI tools and uses the same product grouping, including Claude Other for historical, missing, blank, or unrecognized product information. The Claude adoption report does not include spend.