Koko Analytics version 2.0 is here!
Posted on by Danny van Kooten.
We’re excited to announce the release of Koko Analytics 2.0, a major milestone in making website analytics for WordPress even more flexible while staying true to our principles of simplicity and privacy.
Path based tracking
Until now, Koko Analytics tracked visits based on WordPress post types. Internally we were using the post ID, allowing for tight integration with WordPress and saving on storage because we only had to store a number vs. a piece of text.
This approach works well for many sites, but had one limitation: it didn’t cover everything. Category archives, search result pages and 404 pages were not counted on an individual basis.
With version 2.0, Koko Analytics switches to path-based tracking.
This means the plugin now records statistics for any URL on your site — whether it’s a blog post, a product page, a category archive, or even a non-existing page. If it can be visited, it’s now counted on an individual basis (and not just towards the total visitors or pageviews across all pages).
How we kept it efficient
Tracking URL paths means storing pieces of text in the database.
One of the challenges for this release was doing this without bloating your database and also properly migrating any existing data to the new storage format. We’ve carefully redesigned how paths are stored so you get the extra flexibility without a big increase in storage requirements.
At the same time, we made sure to keep storing the internal WordPress post ID whenever possible. This means features like “most viewed posts” (through the widget or the shortcode) retain their current functionality.
Improved dashboard styles
We’ve also revamped the dashboard CSS styles so that it is now more uniformly styled whether you’re viewing the standalone version or the one embedded into the WordPress admin area.
The same Koko Analytics you love
- Still lightweight and fast — less than 500 bytes of JavaScript, no impact on page speed.
- Still privacy-friendly — no personal data, no third-party services.
- Still your data — fully stored on your own server.
Update today
Koko Analytics 2.0 is available now on WordPress.org and through automatic updates in your WordPress dashboard.
We recommend updating soon to start benefiting from the new, more complete tracking model.
If you’d like even more powerful insights, don’t forget to check out Koko Analytics Pro
Hello!
I recently updated to version 2 and it seems to have wiped out all my previous stats for the year. When setting it to display for this year, or even this month, I get the exact same data showing there have only been 19 visits to even the main page of my site, when previously that was in the thousands and many individual pages in the hundreds. As best I can figure, it seems the update reset all of my stats. Is all of that old data just gone now? If so I’m really upset to have lost it, it was so useful in tracking what my audience was most interested in.
Hi, daily visitors in the dashboard have dropped significantly after the update, even in Google Analytics everything looks fine. I have sent an email about this to you.
Hey guys, since upgrading to 2.0 the stats being recorded have reduced to almost zero – any clue, why this happened?
E.g. before upgrading we had ~2k visitors with ~4k pageviews every day. Now after upgrading we have e.g. ~20 visitors with ~80 pageviews, which is pretty unrealistic.
Hello Elias and H,
This is probably due to your site serving an outdated version of our client-side tracking script due to very aggressive caching. Please clear your site’s caches and/or whitelist the /wp-content/plugins/koko-analytics/assets/dist/js/script.js so that it is no longer included in the cache.
Dear Koko Analytucs support and Danny van Kooten,
I had also the same issue with previous users, and my site has drooped on views that Koko analytics reports.
I have put on Cloudflare and Litespeed cache the exclusion of script.js and i will report if the problem was solved.
I also installed the optimized tracking endpoint. Do you think it will be a issue with this also? Should i exclude it from cache (if yes can you say the exact url to exclude?) ?
Thaks in advance