Bouzin Download Stats Manager
by bouzin 5 (1 reviews)

Bouzin Download Stats Manager

Tracks downloads from a chosen folder and displays secure, sortable statistics in the WordPress administration.

Bouzin Download Stats Manager ranks #67,255 among WordPress.org plugins with 1+ active installations, is #1,146 of 1,990 in the Analytics category, a 5/5 rating from 1 reviews, and was last updated Jul 21, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7 (Current: 7.1.1)
v1.8.7 Current Version v1.8.7
Updated 1 month ago Last Update on 21 Jul, 2026
Refreshed 16 hours ago Last Refreshed on
#1,146 of 1,990 in Analytics
View on WordPress.org
Rank
#67,255
No change
Active Installs
1+
No change
KW Avg Position
N/A
No change
Downloads
171
Total downloads
Support Resolved
0%
No change
Rating
100%
Review 5 out of 5
5 (1 reviews)

Next Milestone 10

Total Progress 10%
0+ 10+
66,552
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 9 more installs to reach 10+

Rank Changes

47,066 52,771 58,477 64,183 69,888 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026
47,066 52,771 58,477 64,183 69,888 05-09-2026 06-09-2026 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026
Current #67,255
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026
0 10 05-09-2026 06-09-2026 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

5.0
1 reviews
Overall 100%
5
1 (100%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Bouzin Download Stats Manager

No. Matching anchor links are rewritten dynamically on front-end HTML responses. The stored post, page, widget, or menu content is not modified in the database.
The settings page offers a simple WordPress Media Library mode and a button that opens the native Media screen in a new tab. This mode monitors the real WordPress uploads directory and its year/month subfolders. For a custom relative folder, the plugin tries to create the missing directory when settings are saved. It does not include an arbitrary server file manager and never moves existing files.
No. The download handler rejects invalid paths, . and .. segments, files outside the configured folder, disallowed extensions, directories, unreadable files, and symbolic links that resolve outside the monitored folder.
Document and archive extensions made of 1 to 16 alphanumeric characters can be configured. Executable, script, server-configuration, key, and database extensions are always rejected, even if entered in the settings.
New installations store statistics directly in the per-site tables {prefix}fdsb_files and {prefix}fdsb_download_events. The prefix is obtained from WordPress and is not assumed to be wp_. Sites upgrading from a legacy CSV version may still have the historical journal in: wp-content/uploads/bouzin-download-stats-manager/journal.csv The actual uploads base directory is obtained from WordPress, so custom uploads paths and multisite installations are supported. The controlled migration is displayed only when this legacy storage remains active.
This applies only to sites upgrading with historical CSV data. The CSV stays active during import. Each imported row is identified by its original byte offset, making retries idempotent. Downloads received while migration is running are written to both stores under the CSV lock. The plugin then compares the event count and a progressive SHA-256 checksum before it changes the active storage mode. If any database write or verification fails, the switch is refused and CSV mode remains active. The historical CSV is not moved or deleted by migration.
Yes. The administrator export action streams the database in bounded batches through fputcsv() and sends it with CSV attachment headers. It does not display the export as an HTML or text page.
The plugin does not store IP addresses, full user-agent strings, account identifiers, or cookies. By default, the journal contains only the download date/time and relative file path. If an administrator enables the optional settings, the journal may additionally contain a server-provided two-letter country code and the broad category desktop, mobile, or unknown. Headers are processed only for the current request and are not saved.
Country collection is disabled by default. When enabled, the plugin reads only a validated two-letter code already supplied locally by a supported server or CDN value. Supported sources include Cloudflare, CloudFront, Vercel, 20i, WP Engine GeoTarget, Kinsta/WordPress VIP GeoIP variables, Fastly origin headers, bunny.net, Akamai EdgeScape, and common local GeoIP server variables. It never performs a remote geolocation request and never stores the visitor IP. If the host or CDN does not expose a local country value, the country remains unknown. Developers can integrate another trusted local source with the fdsb_download_country_code filter. Device collection is also disabled by default. When enabled, the plugin prefers a low-detail mobile client hint or a server-provided CloudFront device category, then temporarily examines the user-agent string as a fallback. Only desktop, mobile, or unknown is stored. Detection is approximate and can be affected by browser privacy settings, VPNs, or proxy services.
Known browser and proxy prefetch headers are always excluded from the journal. Standard mode filters known bot signatures. Enhanced mode, enabled by default, also detects automation clients and suspicious browser-header combinations. Strict mode requests a fresh, short-lived signed token from the local WordPress server after a trusted JavaScript click. The request uses no cookie or personal identifier and is explicitly excluded from caches. A direct link or browser without JavaScript still receives the file but is not counted in strict mode. After first enabling strict mode, purge any existing full-page or CDN cache once so pages include the helper script. No method can identify every automated request, including bots that fully control a real browser.

Sign In / Register

You need to sign in or register to use this feature.