2.5.1

= 2.5.1 =

• tracking: more aggressive bot filter lists.
• dashboard: add new Koko Analytics logo and brand colors.

= 2.5.0 =

• import: add importers for Burst Statistics, Statify, WP Statistics, Independent Analytics, and SlimStat Analytics.
• import: fix updating existing referrer statistics during imports.
• dashboard: improve the styling of KPI metrics, charts, tables, pagination, and the Pro upsell.
• dashboard: dim the realtime component when filtering by page.
• data: run database migrations immediately after resetting tables.

2.5.0

v2.5.0

2.4.1

= 2.4.1 =

• import: fix Plausible importer compatibility with PHP 7.4.
• security: harden data import validation and output escaping.
• dashboard: fix collation mismatch when querying by path containing utf-8 characters.
• dashboard: return a 403 response and prevent indexing when visited by bots or crawlers.
• compatibility: raise the minimum supported WordPress version to 6.2.

2.4.0

= 2.4.0 =

• tracking: hook into the visibilitychange event again to ignore prerender requests.
• data: rewrite exporter and importer to use NDJSON instead of raw SQL.
• import: fix column names for the referrer stats table.
• rest: clamp date range for unauthenticated users to prevent large table scans.
• review notice: simplify the review notice to one primary action.

2.3.7

• tracking: include UTM parameters in pageview tracking requests so integrations can access campaign data.
• endpoint: harden pageview and event request validation by checking required parameters and accepted types.
• endpoint: unslash request data when running inside WordPress.
• endpoint: use exact buffer filename matching when finding existing buffer files.
• endpoint: use file locking when writing to buffer and session files.
• endpoint: handle missing upload or sessions directories more defensively.
• dashboard: fix saving component order when the page contains non-sortable dashboard columns.
• dashboard: keep an explicit group parameter when switching chart grouping back to days.
• docs: add campaign parameters to in-plugin links to Koko Analytics documentation and Pro pages.

2.3.6

= 2.3.6 =

• dashboard: group top pages by post ID when available, so changing a post slug no longer splits its analytics in the dashboard.
• dashboard: resolve titles and permalinks dynamically for posts and pages in the top pages list.
• dashboard: page-specific totals and charts now use post ID filters when available.
• tracking: ignore query parameters when pretty permalinks are enabled.
• tracking: ensure normalized paths always start with a leading slash.
• data export: improve export reliability by casting numeric values and handling missing tables defensively.
• settings: show database usage and table sizes on the data settings page.
• settings: add current and latest database migration version to debug info.
• docs: rewrite plugin readme and only show the 5 most recent changelog entries.
• release: exclude development-only files from the WordPress.org package.

2.3.5

2.3.5 - May 1, 2026

• data: ensure aggregation process does not run while database migrations are pending.
• perf: aggregation process no longer invalidates alloptions cache on every run.
• perf: process database pruning in chunks of 10K rows.
• security: add nonce verification to user-initiated action to update to v2.

2.3.4

2.3.4 - Apr 20, 2026

• fix: access to Jetpack and Plausible importer pages.
• fix: database warning because of unexisting table on fresh installs.
• ux: table rows selectable again.
• seo: remove canonical URL from public dashboard (because it is already noindex).
• database: change default database purge treshold to 3 years (down from 5).
• dashboard: don't listen to query string argument for public dashboard if pretty permalinks are enabled.

2.3.3

2.3.3 - Apr 8, 2026

• database: fix table and column value for upserting new referrer URL's.

2.3.1

2.3.1 - Apr 7, 2026

• dashboard: draggable icon now only shows up when hovering table header, not table body
• database: prevent running database migrations concurrently
• database: try to increase time limit to 300s before running database migrations
• database: re-acquire and extend acquired lock after every individual database migration step