claude-code - 💡(How to fix) Fix [DOCS] Analytics docs should clarify telemetry opt-out effects on API and Enterprise usage metrics [1 participants]

Documentation Type

Unclear/confusing documentation

Documentation Location

https://code.claude.com/docs/en/analytics

Section/Topic

Usage metrics in the Team/Enterprise and API analytics dashboards, plus the telemetry opt-out variables in Data usage and Environment variables.

Current Documentation

The analytics page currently says:

Claude Code provides analytics dashboards to help organizations understand developer usage patterns, track contribution metrics, and measure how Claude Code impacts engineering velocity.

It lists usage metrics for Team and Enterprise:

Usage metrics: lines of code accepted, suggestion accept rate, daily active users and sessions

And for API customers:

API customers using the Claude Console can access analytics at platform.claude.com/claude-code.

The data usage page documents telemetry opt-out separately:

To opt out of Statsig telemetry, set the DISABLE_TELEMETRY environment variable.

It also says:

You can opt out of all non-essential traffic, including surveys, at once by setting CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC.

The environment variables page says:

CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC | Equivalent of setting DISABLE_AUTOUPDATER, DISABLE_FEEDBACK_COMMAND, DISABLE_ERROR_REPORTING, and DISABLE_TELEMETRY

and:

DISABLE_TELEMETRY | Set to 1 to opt out of Statsig telemetry

What's Wrong or Missing?

The docs do not connect the telemetry opt-out variables to the API and Enterprise usage metrics described on the analytics page.

Changelog v2.1.120 includes:

Fixed DISABLE_TELEMETRY / CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC not suppressing usage metrics telemetry for API and enterprise users

That confirms these variables are supposed to suppress usage metrics telemetry for API and Enterprise users. The current docs explain that the variables disable Statsig/non-essential telemetry, and they explain that API and Team/Enterprise dashboards show usage metrics, but they do not explain the operational effect of opting out:

• whether users with DISABLE_TELEMETRY=1 are omitted from usage metrics telemetry
• whether CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 has the same analytics impact
• what admins should expect in API or Enterprise dashboards when some users opt out
• whether metrics such as lines of code accepted, suggestion accept rate, daily active users, and sessions may be reduced or absent for opted-out users

Without this connection, admins can reasonably expect analytics dashboards to remain complete while also expecting telemetry to be disabled, even though the changelog indicates the usage-metrics telemetry is suppressed.

Suggested Improvement

Add a note to the analytics page under both Team/Enterprise and API usage metrics explaining that client-side telemetry opt-outs affect dashboard completeness.

Suggested wording:

Users who set DISABLE_TELEMETRY=1 or CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 do not emit Claude Code usage metrics telemetry. For Team, Enterprise, and API analytics dashboards, metrics such as lines of code accepted, suggestion accept rate, daily active users, and sessions may exclude opted-out users or sessions.

Also update the data usage and environment variables pages so the DISABLE_TELEMETRY and CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC entries cross-link to the analytics page and explicitly mention usage metrics telemetry, not only Statsig operational metrics.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

Total scope: 5 pages affected

Source: Changelog v2.1.120

Exact changelog entry: Fixed DISABLE_TELEMETRY / CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC not suppressing usage metrics telemetry for API and enterprise users