Identifying Users

Understand how Fetch Hive surfaces tracked end users as User IDs across the Users pages and run details

Use user tracking when you want Fetch Hive to group usage and cost by the end users behind your API traffic.

Overview

Fetch Hive centers user tracking around the Users section in your workspace. That section shows each tracked end user as a User ID, then lets you open that user's analytics and activity history.

When you open a user, Fetch Hive uses that same tracked identifier to load the matching analytics, logs, and activity history you see in the dashboard.

How do I see tracked users in Fetch Hive?

Open Users in the main sidebar.

Fetch Hive shows a table of tracked users for the selected date range.

Each row includes User ID, First Request, Last Request, Total Requests, Total Tokens, and Total Cost.

Use the search field if you want to quickly find a specific identifier.

How does Fetch Hive show the user identifier in the UI?

On the Users page, Fetch Hive labels the tracked identifier as User ID.

When you open a user, Fetch Hive uses that value in the user-detail URL and then loads the matching analytics and logs for that same identifier.

You see the same identifier again in places that link back to the user record, including run detail sheets and analytics charts.

That means you can treat User ID as the dashboard name for the end-user identifier Fetch Hive tracks across these pages.

How do I open a specific user from logs or analytics?

You can open a user directly from the Users table by clicking a row.

You can also open the same user from Dashboard analytics or Users analytics by clicking a user inside Top Users.

In prompt, workflow, and agent run detail sheets, Fetch Hive also shows a clickable user link when the run includes a tracked user identifier. Selecting that link opens the same user detail page in Users.

User ID across Fetch Hive

Fetch Hive uses the same tracked end-user identifier across the Users page, analytics views, logs, and run details.

In the dashboard, that identifier is presented as User ID.

If you are documenting or debugging the UI flow, treat User ID as the user-facing name for the tracked identifier shown throughout this feature area.

See also: Analytics and Filtering and drilling.