Black Fridayfrom $34.30/yr1 site · 5 sites $83.30 · unlimited sites $139.3030% off every planNov 20–Dec 1 (UTC)

SlimStat 6.1.2: Tracking, Reports and GitHub Fixes

SlimStat 6.1.2: Tracking, Reports and GitHub Fixes

SlimStat Free 6.1.2 and Pro 3.1.1 address reported problems with tracking, consent, report loading, maps, heatmaps and database upgrades. They also add Free Copy Prompt, country-to-city drilldowns and Pro AI Analysis. The fixes below explain what changes for a site owner and link back to the original reports.

This is a review of the changes in Free 6.1.2 and Pro 3.1.1, the first public releases of the 6.1 and 3.1 lines, since Free 6.0.0 and Pro 3.0.0. It is not a claim that every GitHub issue is fixed. As checked on November 16, 2026, the Free repository had 69 open issues and Pro had 3. Several reports addressed by these branches still had an open issue status. Implementation, published availability and issue closure are separate facts. Check the release notice above and the linked issue for current status.

Which tracking and attribution problems are fixed?

ReportWhat the release changesWhat to check on your site
#120A tracker loaded in the page head captures clicks and form submissions once the page is readyOne supported interaction records once
#365Client pageviews are sent when the page is ready instead of waiting for all resources to finishShort visits reach the tracker
#396Server tracking avoids counting canonical redirects as extra pageviewsTrailing-slash redirects no longer create duplicate activity
#257Server-only tracking assigns visit IDsEligible requests that reach PHP receive sessions
#272, #364Online Users excludes bots; self-identifying headless browsers and Lighthouse are classified as botsHuman counts can decrease when these requests are excluded
#276Optional URL normalization removes selected tracking parameters after extracting campaign attributionEnable only parameters that do not identify different pages or products; old URLs are unchanged
#368WooCommerce attribution recognizes social and messaging app referrersCheck new attributed orders with the same consent and reporting scope

Server mode still cannot count full-page-cache hits that never reach PHP. Bot detection is based on available signals; it is not a guarantee of identifying every automated visitor.

ReportWhat the release changes
#366Consent withdrawal requests work again
#367Saving Tracker settings preserves consent options you did not change
#375WooCommerce attribution waits for SlimStat banner consent before writing its first attribution cookie
#181Hidden consent banners stop blocking clicks and keyboard focus on form controls
#372Heatmap sampling is spread across pageviews instead of contiguous ID blocks
#373Activity before consent is discarded instead of being sent after acceptance
#374Backdated full-capture and legacy clicks no longer overlap in the count; Pro refreshes the affected caches
#369, #370Heatmap titles display decoded text and Pro insights use readable element names while retaining selectors for navigation

Test accept, decline and withdrawal using the banner or CMP your site actually uses. Privacy settings still require configuration. These changes do not establish automatic legal compliance.

Which report problems are fixed?

ReportWhat the release changes
#361Upgraded sites recover asynchronous WordPress Dashboard widget loading
#408Dashboard widgets display when data arrives without an additional fade delay
#409Ecommerce Copy Prompt can reuse the cache populated by the report page
#158Chart refreshes preserve filters and the comparison setting
#402Audience Location shows city dots again with a legend and better layout; map assets are bundled locally
#362SQL diagnostics cover cached and network reports and show database errors safely
#388The WordPress Dashboard Access Log no longer shows a Pro promotion

Reports also defer offscreen work, limit concurrent loading and reuse historical results. Read the performance explanation and measurement limits for the difference between fewer database operations and a page-load timing claim.

What changes for database upgrades and recovery?

ReportWhat the release changes
#395Migration detects an incomplete visit-counter setup and offers a retry
#360Optional online repair covers more legacy column differences while preserving recorded values
#363Missing opted-in Browscap data recovers in the background, with a manual retry
#227Deprecated tracker and geolocation helpers return for integrations still calling them
PR #351Malformed saved filters cannot silently produce partial or unfiltered reports; the saved filter can still be deleted

Other release changes protect external-database ownership, distinguish tracking outages from maintenance warnings, preserve archive fields during retention and apply personal-data erasure to the selected analytics database. Pro’s dependency updates address known security issues, and report-access allowlists now match complete usernames.

For the retired Custom DB add-on, follow the dedicated transition guide. Pro verifies the existing connection before taking over. Do not deactivate the old provider first and assume the history will move automatically.

What else changes in 6.1.2?

  • Persian and English layouts keep arrows, dates, live metrics, notices and report controls aligned on desktop and mobile, and the SlimStat header adapts to narrow screens and right-to-left languages.
  • Scrolling a report continues onto the page at its top or bottom, and the date picker keeps your chosen preset when two presets cover the same dates.
  • SlimStat is tested with WordPress up to 7.1.4, and the WordPress.org Plugin Check passes with the bundled libraries included.

The full Free list is in the plugin changelog, and the SlimStat changelog summarizes each release.

How do I verify the update?

  1. Back up the site and analytics database, then update Free before Pro.
  2. Review SlimStat → Migration. Required steps and optional repairs are different operations; read the proposed changes before running them.
  3. Record a visit, test your consent choices, and perform an action you track as a goal.
  4. Compare an equivalent date range and filters. Correcting duplicates or bot counts can reduce totals without losing genuine activity.
  5. If you use Pro, check license activation and one Pro report. If you use an external database, confirm both old history and new visits remain in the selected database.

Still seeing one of these symptoms? Send a support request with plugin versions, the exact report, dates, filters and reproduction steps. Keep license keys, database credentials and visitor records out of public tickets.

What does Pro 3.1.1 add?

Free receives the core tracking and report corrections. Pro 3.1.1 adds AI Analysis inside WordPress, a private saved-results library and the full available country-to-city breakdown, alongside visual heatmaps, funnels, Ecommerce breakdowns and scheduled email reports.

Compare Pro plans if these tools fit your workflow. AI Analysis needs Free 6.1.2, WordPress 7.0+, a connected provider and a valid site license; provider charges may apply.

SlimStat Pro 30% off, from $34.30