Analytics changedgovernment/org-admin/analytics
Nearest release: v2.1.319, published 15 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 6 Nov 2026 16:05 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 6 Nov 2026 16:07 UTC.
Upstream edited
Recorded here
Lines+21added
Lines−53removed
From line
1
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits9to this page, all time
## How the data is gathered ## Things to know
The whole hunk
from line 1, old and new numbered
/
from line 1
11# Analytics
22
3> Use this page to review requests, tokens, spend, top users, and credit balance over time across your organization, and to download the data as CSV files for offline reporting.
3> Review your organization's requests, tokens, spend, active users, top users, and credit balance over time, and download the data as CSV files for reporting.
44
55> **Who this is for:** Organization owners who need to understand how their organization is using Claude and how quickly it is consuming credits.
66
7Use this page to review requests, tokens, spend, top users, and credit balance over time across your organization, and to download the data as CSV files for offline reporting.
7The **Analytics** page shows requests, tokens, spend, top users, and credit balance over time across your organization. Usage figures on this page are compiled from the same metering that enforces your users' spend limits. All times are shown in your browser's time zone.
88
9Because this data takes a moment to compute, the page starts with a **Load analytics** button. After the data loads, the results are cached for the rest of your session. You can click **Refresh** to fetch the latest numbers, and this button becomes available again 30 seconds after the previous load.
9> [!NOTE]
10>
11> These cases are covered on other pages:
12>
13> * **How close each user is to their 5-hour and 7-day limits**: use the **Usage** bars on the [Users](https://claude.com/docs/government/org-admin/users.md#reset-usage-limits) page
14> * **Usage records sent to your own collector**: see [Compliance and telemetry](https://claude.com/docs/government/config/settings.md#compliance-and-telemetry)
1015
11A **Download** menu next to **Refresh** saves what the page shows as CSV files, described in [CSV exports](#csv-exports).
12
13## How the data is gathered
14
15Usage figures on this page are compiled from the same metering that enforces your users' rate limits, so the request, token, and spend numbers here will closely match what your users experienced. All times are shown in your browser's time zone; if your browser reports a time zone the service does not recognize, times fall back to UTC.
16
1716## Managed and self-managed views
1817
19A control at the top switches between **Anthropic-managed tiers** and **Self-managed tiers**. The two are shown separately because their economics differ: managed-tier seats are purchased as seats, while **self-managed tiers** (tiers your organization created itself on the [Tiers](https://claude.com/docs/government/org-admin/seat-tiers.md) page) draw down the billing account's balance. Spend figures and the credit panel are therefore shown only in the **Self-managed** view.
18**Anthropic-managed tiers** and **Self-managed tiers** are shown separately because their economics differ: managed-tier seats are purchased as seats, while self-managed tiers (tiers your organization created itself on the [Tiers](https://claude.com/docs/government/org-admin/seat-tiers.md) page) draw down the billing account's balance. Spend figures and the credit panel are shown only in the **Self-managed** view. If your organization has only one kind of tier, the page shows only the matching view.
2019
21If your organization has only one kind of tier, the control does not appear and the page shows only the matching view. If all of your seat tiers are Anthropic-managed, you see only the managed view, with no spend figures, credit panel, or burndown chart.
22
2320## Credits (self-managed view only)
2421
25> [!NOTE]
26>
27> The credit panel and burndown chart only appear in the **Self-managed tiers** view, and only once credit data is available for your organization. The runway estimate within the panel only appears once there has been enough recent activity to compute a burn rate.
22When credit data is available, the credit panel displays the **Credits remaining** for the account your organization draws from. It also shows a runway estimate that tells you roughly how many days remain at your organization's own trailing 7-day burn rate. A **Low balance** badge appears as the balance runs low, and a **Depleted** badge replaces it when no credits remain.
2823
29When credit data is available, the credit panel shows the current position of the account your organization draws from as of right now. It displays the **Credits remaining** out of the total added to the account, with a progress bar marked at the 70 percent and 90 percent warning thresholds. It also shows a runway estimate that tells you roughly how many days remain at your trailing 7-day burn rate. A **Low balance** badge appears once 70 percent of the total has been used, and a **Depleted** badge replaces it when no credits remain.
24The **Credit burndown** chart plots your balance, with markers on the days credits were added, and projects forward at that rate to the date you are estimated to reach \$0.
3025
31The runway figure divides your remaining balance by your average daily spend over the last seven complete days. It is shown as "less than 1 day" when the balance is nearly exhausted and as "more than 180 days" when spend is low enough that a longer projection would not be meaningful. If there has been no spend at all in the last seven days, no runway is shown.
32
33Below the panel, the **Credit burndown** chart plots your balance, with markers on the days credits were added, and projects forward to the date you are estimated to reach \$0. The chart reaches back 30 days, or 90 days when you set the time-window selector described below to **90 days**.
34
35> [!TIP]
36>
37> The credit panel always reflects the current position and is not affected by the time-window selector. The 7-day lookback used for the burn rate is also fixed and does not change when you switch the usage window.
38
3926## Active users
4027
41The **Active users** section shows how many distinct people used Claude over fixed periods: the average number of daily active users over the last 7 days, the number of weekly active users over the last 7 days, and the number of monthly active users over the last 30 days. These figures always use the same fixed lookbacks and are not affected by the time-window selector below.
28The **Active users** section shows how many distinct people used Claude over fixed periods, as daily, weekly, and monthly active users. A user counts as **active** if Claude answered them at least once in the period.
4229
4330## Usage
4431
45Everything below the **Usage** divider is scoped to a time window that you choose with the **24 hours**, **7 days**, **30 days**, or **90 days** selector.
32Everything below the **Usage** divider is scoped to a time window that you choose, from **24 hours** to **90 days**. The figures are requests, input tokens, output tokens, and, in the self-managed view, estimated spend. Estimated spend includes input stored or reused through prompt caching. Input tokens do not, so token counts alone understate cost.
4633
47The summary tiles show the number of requests, the input and output token counts (a token is roughly a piece of a word, and it is the unit that Claude's usage is measured in), and, in the self-managed view, the estimated spend for the selected window.
34* The **By product** table breaks usage down by which Claude product it came from (for example, Claude Desktop or Claude Code). Chat and Cowork activity in Claude Desktop is counted together in a single Claude Desktop row. Code sessions in Claude Desktop run on Claude Code, so they are counted in the Claude Code row along with any use of the standalone Claude Code command-line tool.
35* The **By model** table lists each model used in the window.
36* The **Top users** table lists the users with the most tokens in the window, and each user's figures combine their usage across all products. Up to 100 users are listed individually, and beyond that a note tells you how many more are not listed. Usage from before a person's move stays with the organization they left.
4837
49The **Token usage** chart plots input and output tokens over the window. It shows hourly data when you select the 24-hour window and daily data for the longer windows.
50
51The **Active users over time** chart plots the number of distinct users who got at least one answer from Claude in each period of the window, using the same hourly or daily buckets as the token chart.
52
53The **By product** table breaks usage down by which Claude product it came from (for example, Claude Desktop or Claude Code), with the same request, token, and spend columns as the other tables. Chat and Cowork activity in Claude Desktop is counted together in a single Claude Desktop row. Code sessions in Claude Desktop run on Claude Code, so they are counted in the Claude Code row along with any use of the standalone Claude Code command-line tool. This table only appears once your deployment has recorded usage from at least one product.
54
55The **By model** table lists each model used in the window along with its request count, input tokens, output tokens, and, in the self-managed view, its spend.
56
57The **Top users** table lists the users with the most usage in the window with the same columns, and each user's figures combine their usage across all products. The table starts with ten rows, and you can click **Show more** to reveal additional users. Up to 100 users are listed individually, and beyond that a note tells you how many more are not listed.
58
5938## CSV exports
6039
61The **Download** menu at the top of the page, next to **Refresh**, saves what the page shows as CSV files. **All** downloads a ZIP archive of the current view, one CSV file per table. The other entries download one table each: **Summary**, **Usage over time**, **By product**, **By model**, and **Top users**, with **Credit burndown** and **Credit top-ups** added in the self-managed view. The menu becomes available again 30 seconds after the previous download.
40The **Download** menu saves what the page shows as CSV files. **All** downloads a ZIP archive of the current view, one CSV file per table. The other entries download one table each.
6241
63Exports follow the view and the time window you have selected. The credit files match the burndown chart, reaching back 30 days, or 90 days when you select the **90 days** window. In the summary file, the credit figures are the account's position at the time of the export, not spend within the window.
42* **What an export covers.** Exports follow the view and the time window you have selected. The credit files match the burndown chart, reaching back 30 days, or 90 days when you select the **90 days** window. In the summary file, the credit figures are the account's position at the time of the export, not spend within the window.
43* **Export context.** The ZIP archive includes an `export_info.csv` file recording the export's context, including when it was made, the organization, the view, the window and its date range, and the time zone the dates are in.
44* **Per-user data.** The top users file lists the same users as the **Top users** table, up to 100, and adds each user's ID and account status to the columns shown on screen.
6445
65The ZIP archive includes an `export_info.csv` file recording the export's context, including when it was made, the organization, the view, the window and its date range, and the time zone the dates are in. In the self-managed view it also records the date range the credit files cover.
66
67File names state the view, the time span, and the dates covered, and single-table files also name their table.
68
69The top users file lists every user the **Top users** table can show, whether or not you have expanded the table with **Show more**, and adds each user's ID and account status to the columns shown on screen.
70
71## Things to know
72
73* Claude for Government does not currently offer a programmatic usage or analytics API. Usage data is available through this admin portal page. The [Compliance API](https://claude.com/docs/government/org-admin/compliance-api.md) returns governance and audit events, not usage metrics.
74* A user counts as **active** in the selected window if Claude answered at least one of their requests in it, regardless of which seat tier they were on at the time. Opening Claude Desktop or another Claude app without sending a message does not count, and neither does a request that failed before Claude answered.
75* The **spend** column appears only in the self-managed view and is the amount debited from your billing account's balance. The managed view has no spend column because managed-tier usage is covered by the seat price rather than by credit drawdown.
76* To see how close each user is to their 5-hour and 7-day limits, use the **Usage** bars on the [Users](https://claude.com/docs/government/org-admin/users.md) page. The **Top users** table on this page shows how much each listed user consumed in the window, not how close they are to a limit.
77* If the credit panel is missing from the self-managed view, credit data for your organization's billing account is unavailable. The rest of the page will still load.
78* Usage that was cleared with **Reset usage limits** on the [Users](https://claude.com/docs/government/org-admin/users.md) page still appears here. The reset only clears the counter that enforces a user's limit; it does not remove the activity from analytics.
46Claude for Government does not offer a programmatic usage or analytics API. Usage data is available through this admin portal page. The [Compliance API](https://claude.com/docs/government/org-admin/compliance-api.md) returns governance and audit events, not usage metrics.
7947
No line in this hunk matches that.