Hot
A number, not a profile.
A counter that stores a number and nothing else. No cookies, no identifiers, no per-visitor rows. One integer per file, incremented on delivery.
Download analytics usually arrives as a tracking product: per-visitor rows, an identifier in a cookie, and a dashboard nobody asked for.
Most sites only want to know how many times a file was fetched. This stores exactly that, one integer per file, and keeps no record of who fetched it.
Passed our privacy review in one reading.
— A compliance officer
A count, and nothing else.
One integer per file
No visitor rows, no identifiers, no cookies. The only thing stored is a count.
Bot filtering
Known crawlers and prefetch requests are excluded before the counter is touched.
Redirect delivery
Counts on a redirect so the file itself is still served by the web server rather than through PHP.
Plain export
A CSV of file names and counts, with no dashboard to learn.
The whole of it.
A short list on purpose. Anything else would mean storing something about the person downloading.
- One integer stored per file
- No cookies or identifiers
- Crawler and prefetch filtering
- Redirect-based delivery
- CSV export of counts
- Template tag for display
- Counts survive a file being replaced
- Runs without a schema change
The details
- Version
- 1.0.4
- Released
- Sep 1, 2025
- Data stored
- Count only
- Cookies
- None
- Delivery
- Redirect
- Export
- CSV
Recent releases
- 1.0.4Sep 2025 — Prefetch requests excluded from the count
- 1.0.3Jul 2025 — Counts now survive replacing the underlying file
MORE LIKE THIS
Related themes
New
Featured
