Skip to content

docs: align publisher analytics export schema #2384

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Pierrci merged 2 commits into from
Apr 21, 2026
+6 −6
Merged

docs: align publisher analytics export schema #2384

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
420477e
docs: align publisher analytics export schema
Pierrci Apr 14, 2026
9da74a9
Apply suggestion from @Pierrci
Pierrci Apr 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions docs/hub/publisher-analytics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,20 +62,20 @@ Records are ordered chronologically and provide a daily granular view of downloa
> [!WARNING]
> This feature is an add-on for the <a href="https://huggingface.co/contact/sales?from=enterprise" target="_blank">Enterprise Plus</a> plan.

As an advanced feature, Hugging Face can export anonymized, request-level access logs for all of the models and datasets published by your organization. Each line represents a single download request (including HEAD and partial requests), giving you full granularity over your models and datasets' download data.
As an advanced feature, Hugging Face can export anonymized, request-level access logs for all of the models and datasets published by your organization. Each line represents a single download-related request, giving you full granularity over your models and datasets' download data.

Your team is responsible for ingesting these logs and running computations on them — for example, to deduplicate downloads to get unique downloader counts.
Your team is responsible for ingesting these logs and running computations on them. The export intentionally includes raw HTTP status codes and methods so you can classify `HEAD`, partial-content, redirect, and other request patterns based on your own analytics needs.
Comment thread
Pierrci marked this conversation as resolved.

| Column | Description |
| -------------- | ------------------------------------------------------- |
| `timestamp` | Request timestamp |
| `requestType` | Type of download request (`GET`, `HEAD`, partial/range) |
| `status` | HTTP status code (for example `200`, `206`, `302`, `307`, `304`) |
| `method` | HTTP method (for example `GET`, `HEAD`) |
| `repoName` | Full repo name (e.g. `nvidia/segformer-b0`) |
| `repoType` | `model` or `dataset` |
| `repoType` | Repository type: `model`, `dataset`, or `space` |
| `hashedUserId` | Non-reversible hash of user ID (if authenticated) |
| `hashedIp` | Non-reversible hash of IP address (if unauthenticated) |
| `country` | Country ISO code |
| `region` | Region name |
| `isInternal` | Whether the request comes from an HF internal service |
| `region` | Region or city name |

As it requires setting up a custom data export pipeline on our side (custom Elastic index, etc), this is only available as an add-on to Enterprise Plus.
Loading