How does DX report usage across Claude products?

DX distinguishes Claude products using the product information received from your connectors. Use this article to understand which sources provide product attribution, why usage appears as Claude Other, and how product filters affect your reports.

Note: Product-level token and cost attribution currently comes from Claude Code (OTel). The Anthropic Console and Enterprise connectors currently label their imported token and cost data as Claude Code. Connecting an Analytics API does not yet provide separate Chat, Cowork, or other product breakdowns.

How DX identifies products

DX uses the product information provided by your connected sources. OTel connections can provide any product name; DX preserves the received name. The report combines recognized names for the same product under one label and groups historical usage without product attribution and usage with missing, blank, or unrecognized product information under Claude Other.

In the Claude adoption report:

Claude Code combines usage from the terminal and the Code tab in the Claude Desktop app, along with usage reported as Claude Code by API connections.
Chat and Cowork unified is listed separately from Claude Chat and Cowork when usage is reported for Anthropic’s combined experience.
Claude Tag groups usage under one label even when connections use different names for that product.
Cowork, Claude Chat, Claude Design, Claude in Chrome, and Office Agent appear when a connected source provides usage for them.
Claude Other combines historical OTel usage recorded before product attribution was available with usage that has missing, blank, or unrecognized product information.

The available products depend on your connected sources. Setting up collection for Claude Code does not automatically enable collection for Chat, Cowork, or other Claude products.

Why historical OTel usage appears as Claude Other

Historical OTel records created before product attribution was recorded do not identify which Claude product generated them. DX groups these records under Claude Other. They may include Chat, Cowork, or Claude Code usage, so DX does not relabel them as Claude Code even if that is how they previously appeared in the report.

The historical usage remains available under All products and Claude Other. The attribution change does not mean that the usage was deleted or that those people stopped using Claude.

New OTel usage appears under the matching product when DX recognizes the product name. If product information is missing, blank, or unrecognized, that usage also appears under Claude Other. Historical records marked unknown and newer records marked ungrouped share this single reporting label. DX preserves the original stored product values.

Changing today’s telemetry configuration does not recover the product for those historical records.

How historical code metrics are shown

Acceptance rate, Lines of code, Tool usage, and Skill usage appear when Claude Code or All products is selected. Selecting Claude Other or another non-Code product hides these cards. Historical values for these metrics are available under All products.

Under All products, these metrics include Claude Code usage and historical records marked unknown, labeled Claude Code + historical. Those historical records remain attributed to Claude Other. Newer records marked ungrouped, or with missing, blank, or unrecognized product information, are excluded from these feature metrics. Adoption and token metrics under All products continue to include every product.

Use All products to review overall adoption, then select Claude Code to compare periods with known Claude Code attribution.

How product totals relate to All products

Claude Other combines historical OTel usage without product attribution and usage with missing, blank, or unrecognized product information. This combined usage remains included in All products, and you can select Claude Other to review it together.

Contributor counts also overlap: one person can use Claude Code and Cowork in the same period. Product-level active-user counts are not mutually exclusive populations and should not be added together to calculate overall adoption.

If recent usage appears under Claude Other unexpectedly, ask the administrator who manages your Claude connection to check the product information being passed through to DX. A custom product name can be preserved correctly by the connection and still appear under Claude Other if DX does not recognize it. See Centralized Claude Code OTel collection for collection setup.

Selecting a product scopes activity to that product. The adoption denominator remains the selected contributor or licensee population; it does not become a separate population of licenses for that product.

For example, someone who uses Cowork but has no Claude Code usage in the selected period counts as inactive for Claude Code and can appear under Unused licenses when that product is selected. This does not establish that their Claude license is unused across all products. Select All products before deciding whether to reallocate a license.

Where to analyze spend

Use AI cost management for Claude token cost alongside other AI tools. Claude tools use the same product grouping: Claude Other combines historical usage without product attribution and usage with missing, blank, or unrecognized product information. The Claude adoption report covers adoption and feature usage and does not include spend.

For collection setup, see Claude Code (OTel) or Centralized Claude Code OTel collection. For missing people or accounts, see Why aren’t Claude accounts showing up in DX?.