Author and download analytics
Two analytics surfaces ship with the add-on:
- Per-download analytics: traffic and engagement for a single download.
- Author analytics: rolled-up totals across every download a user owns.
Both read from the same daily aggregate, so the numbers tie out.
Per-download analytics
Open the download view page and click Analytics in the toolbar. The URL is /downloads/<id>/analytics.
The page shows four daily series for the selected window:
| Series | Counts |
|---|---|
| Downloads | Successful file deliveries (gates passed, file streamed). |
| Reactions | Reactions added during the window. |
| Reviews | Reviews posted during the window. |
| Comments | Native comments posted during the window. Thread replies are not counted here. |
Above the chart, a totals strip shows the sum of each series across the window.
The window selector at the top right offers 7 days, 30 days (default), and 90 days.
Author analytics
Author analytics is self-only. Open your own author page (/downloads/authors/<your-username>.<id>/) and click Analytics in the page header. The URL is /downloads/authors/<your-username>.<id>/analytics. There is no link to view another user's author analytics; the page is gated to the owner.
The chart and totals show the same four series, summed across every download you currently own. The same 7 / 30 / 90 day windows apply.
If a download is reassigned to you during the window, only post-reassignment events count toward your totals. If one of your downloads is reassigned away, your totals stop accruing on the reassign date.
How traffic is counted
A "download" event is a successful file delivery: the visitor passed every gate, the file streamed (not aborted before the headers), and there was a recognisable response. Aborted downloads, blocked downloads, and gate-fail challenges are not counted as successful deliveries.
Bot traffic is filtered using the standard user agent classifier. Logged-in users count; not-logged-in humans count; identified bots do not.
Each visitor has a short de-duplication window so refreshing the same file in quick succession registers as one event.
Permissions
| Permission | Effect |
|---|---|
| View own analytics | See the analytics tab on your own downloads and on your own author page. |
| View any analytics | See the analytics tab on any download. Typically reserved for moderators and admins. Author analytics remains self-only and is not exposed by this permission. |
Co-owners do not get analytics access through team flags. Grant View own analytics at the user-group level if you want every author to read their numbers.
What is not on the analytics page
The analytics page does not show:
- IP addresses or user agents. Use the audit log if you need attribution.
- Per-version split. The window combines events across every served version of the download.
- Geography or referrer breakdowns. Add a stats consumer (Plausible, Matomo, GA4) if you need those.
Audit log overlap
The audit log records moderator-side state changes (publish, restore, hard-delete, dependency change). It does not record viewer-side events such as downloads, reactions, reviews, or comments. Use analytics for those, the audit log for state changes.