1. 1.0.14

    Coming soon
    • Counts each page of the AJAX navigation of the listings list pages (LaraClassifier and JobClass v19.2.0) as a page view. A page loaded ahead of time, when the visitor's pointer rests on a link, is only counted once it is shown
  2. 1.0.13

    Latest
    • Added sorting by column to the add-on's lists in the Admin panel (click a column header); requires core 19.1.16 or later
    • The add-on's list filters use the new filter bar of the Admin panel (active filter chips, "Clear all", "More filters")
    • Fixed: the tracker recorded the Referer header as sent by the browser, whatever its scheme, and the Referrer URLs report turned it into a link, so a forged "javascript:" referrer could run a script when an administrator clicked it. Only http(s) referrers are now recorded and linked, and the update clears the non-http(s) referrers already stored
    • The Bots report no longer reads every stored bot hit of the period on each load. Its summary (raw, bot and human views, the daily split, the visitor addresses and confirmations) is answered from indexes and shown at once; the five breakdown tables (reasons, networks, User-Agents, addresses, pages) and the bot address count are then loaded in parallel, each from at most the latest 250,000 stored bot hits of the period (stats.bot_report_sample_rows; the page says when a period was sampled). On a table of a few million rows the page went from minutes to seconds
    • The figures of the Bots report are cached for ten minutes per period and shown with their time of computation and a Refresh link; they are recomputed as soon as bot hits are deleted, purged or reclassified
    • Added "Re-check Recent Traffic Every Hour" (Settings > Privacy & Filtering, on by default): every hour, stats:auto-reclassify-bots applies the stats:reclassify-bots rules (rotating proxy pool User-Agents, request and subnet bursts, the per-row checks) to the views of the last 2 days (1 to 7), flags the bot traffic that looked human when it arrived and rebuilds the reports of those days, so a bot spike leaves the statistics within the hour. With "Store Bot Hits" off, the views it flags are moved to the daily bot counters and deleted straight away. Requires the site cron job running the Laravel scheduler
    • Added the daily bot hit counters (stats_bot_daily): bot hits are now counted per day and per detection reason in a table of their own, so the Bots report and the dashboard keep showing how many bots and crawlers hit the website after the raw rows are deleted. A hit is either a stored row or a count, never both; with "Store Bot Hits" off, hits go straight to the counters
    • Added the "Bot Hits Retention" option (Settings > Data Management, 7 days by default): the nightly purge rolls the bot rows older than this window into the counters and deletes them. Set it to "As long as page views" to keep the rows as long as the page views
    • Added "Delete stored bot hits" to the Bots report: deletes the stored bot rows on demand (all of them, or only those older than the retention window), a few seconds of work per request until done, their counts kept. Needs the admin.setting.edit permission
    • The Bots report says when the selected period reaches further back than the stored rows: its figures stay complete, only the User-Agent, network, address and page tables are limited to the rows still stored
    • stats:purge now deletes in batches of 10,000 rows, so a backlog of old page views never holds the table for minutes
    • Added browser confirmation of page views: every tracked page now carries a tiny inline script that posts a per-request token back once the page has loaded (navigator.sendBeacon, no cookie, no library, nothing external). The time of that confirmation is stored with the page view (stats_page_views.confirmed_at). Proxy pools that copy complete browser headers never run scripts, which is now the one signal that tells them apart from visitors
    • Added the "Count only views confirmed by the browser" option (Settings > Privacy & Filtering, off by default). When on, a page view only reaches the reports once its browser has confirmed it, the dashboard "Today" and "Yesterday" cards count confirmed views only, and views still unconfirmed after fifteen minutes are flagged as bots with the new "No JavaScript" reason (no_js) by a sweep that runs every ten minutes (stats:flag-unconfirmed-views). Off, nothing changes in the counting: the confirmation is recorded so the raw and confirmed figures can be compared before turning the option on
    • The Bots report summary now shows how many of the counted visits were confirmed by the browser, as a number and as a share of the visits that received the script
    • stats:reclassify-bots applies the "No JavaScript" rule too when the option is on, and --reset clears it like the other automatic classifications
    • Schema: stats_page_views.view_token (unique) and stats_page_views.confirmed_at, with an index on (is_bot, confirmed_at, viewed_at)
    • Added the "Bots" report (Statistics > Bots): raw page views against the hits flagged as bots and the visits counted, the split per day, the reason of every flag, and the top bot networks, User-Agents, addresses and pages, for any period of the period selector
    • Added two traffic burst checks to the bot detection (Settings > Privacy & Filtering): an address loading more pages than allowed within a minute ("Flag request bursts", 30 by default) and a network (IPv4 /24, IPv6 /48) sending more distinct addresses than allowed within ten minutes ("Flag subnet bursts", 40 by default). Both thresholds are editable, both checks are replayed on past traffic by stats:reclassify-bots (--ip-burst-views, --subnet-burst-ips, --skip-burst-rules)
    • The crawler-detect library (about a thousand crawler, SEO tool, monitoring and HTTP client signatures), shipped with LaraClassifier and JobClass, is now consulted after the built-in crawler list. The settings page says whether it is available
    • Only top-level page loads are counted now: HTML fragments loaded by fetch() or XMLHttpRequest and speculative prefetch/prerender requests no longer register a page view
    • The dashboard "Unique Visitors" card now links to the bot report with the number and share of bot hits filtered today
    • Fixed the dashboard "This Month" card icon reading "Aug" all year: the Bootstrap icon it used is a static drawing of that word. The card now shows the current month
    • Added the "This month" (from the 1st to today) and "Last month" (the whole previous calendar month) periods to the period selector of every statistics page, next to Today, Yesterday, Last 7 days, Last 30 days and the custom dates. Like the other periods, they are hidden when they reach beyond the data retention window.
    • Added the 'Use the GeoIP Network Type' option (Settings > Privacy & Filtering, on by default): a visit is classified as bot traffic when the GeoIP driver selected in the Localization settings reports a hosting or datacenter network ('AS type' hosting with ipinfo.io paid plans, MaxMind Insights or IP2Location, the hosting flag of ip-api.com, including its free plan), or when the AS number of the visitor's network belongs to a known hosting provider (works with every driver that returns the AS number, such as the ipinfo.io free plan).
    • Privacy relays (iCloud Private Relay, Cloudflare WARP) are never flagged: their egress addresses belong to CDN and hosting networks, but their users are real people.
    • Added a list of hosting AS numbers (Alibaba Cloud, DigitalOcean, Hetzner, Vultr, Linode, OVHcloud, Oracle Cloud, Tencent Cloud, Scaleway, Contabo, M247, Leaseweb) and the 'Additional Hosting AS Numbers' setting to add your own.
    • Every address flagged this way is saved: its later visits are classified as bot traffic at once, without a new GeoIP lookup (no API quota used). The new 'Hosting IP Addresses' page (Settings > Privacy & Filtering) lists them with their network, type, hits and last visit, and lets you forget a false positive.
    • Added the --lookup-network option to the stats:reclassify-bots command: it resolves the network of the visitors already recorded through the GeoIP driver (most viewed addresses first, limited by --max-lookups, with an optional --lookup-delay for rate-limited providers) and re-classifies their past visits.
    • The stats:purge command now forgets the flagged hosting addresses not seen for 365 days (stats.bot_ips_retention_days).
    • Added the 'Hosting network (GeoIP)' reason to the bot traffic breakdown.
    • The statistics reports search (pages, referrers, countries, cities, browsers and platforms) now uses the core search engine (smartSearch): every word typed must be found, in any order, ignoring case and accents. It follows the core "Smart search" option; with a core that does not have the engine yet, the previous search is kept.
    • The Cities report (visitor cities, with a country filter, a city search and the pages viewed from each city) had no entry in the admin menu. It is now listed under Statistics, after Countries.
    • The documentation now describes the installation, update, deactivation and removal steps exactly as the add-on manager performs them, and now covers every setting of the four settings tabs (including the Privacy & Filtering options), the STATS_QUEUE_CONNECTION / STATS_QUEUE_NAME keys and the scheduler requirement.