Klant vraagt om Google Analytics te koppelen aan haar website. Ik vraag wat ze er mee van plan is en installeer #KokoAnalytics, om te kijken of dat ook voldoet.
Reactie:
"Dankjewel voor het installeren van Koko Analytics!
Dit is eigenlijk precies wat ik nodig heb/wou doen bedankt."
@dvk Goed gewerkt Danny! đ
Which version of the Koko Analytics dashboard do you prefer?
Left (current) or right (concept)?
Using Cloudronâs IP Firewall
This site is hosted on the same server as The New Leaf Journal, and I use Cloudron to manage the server. Beginning around early spring last year, The New Leaf Journal began to crash once every few days when Cloudron health checks failed (I have not had any similar issues with this site, which is much lower traffic). I attributed the problems to bot traffic, and I think I was correct to do so. I tried many fixes, some of which worked for a time before the downtime problems returned. After [âŠ]https://social.emucafe.org/naferrell/using-cloudrons-ip-firewall-01-30-26/
Koko Analytics Pro 2.2.0 just went out, introducing browser/operating system/device stats! đ
The new version also comes with a filter hook that allows you to completely disable any feature you don't want to use, stopping all related code from being loaded.
As always, let me know in case of any hiccups.
Beta testing a new and much requested feature for Koko Analytics: browser/os/device counting!
May be stating the obvious, but just to make sure everyone knows how privacy is preserved:
- No specifics, only the general browser/os/device family are stored.
- The User Agent itself is never stored.
- Everything happens locally.
- The feature will be opt-in and for users of Koko Analytics Pro only.
Die Blogstatistik 2025
Also eigentlich bin ich ja schon mitten im Jahr drin. Die SteuererklĂ€rung ist angefangen. Allerlei rechtliches Zeugs ist auf dem neuesten Stand, Sicherungen sind durch, usw. Und so ganz nebenbei ist es nun natĂŒrlich auch ganz interessant auf die Statistiken fĂŒr den Blog hier zu schauen. Ende Oktober hatte ich schon mal ausfĂŒhrlicher erklĂ€rt und gezeigt wie ich was an Zahlen verfolge und was fĂŒr Auswirkungen das auf den Blog hat. Daran hat sich nicht viel verĂ€ndert. Die Zahlen verfolge [âŠ]
https://social.emucafe.org/naferrell/returning-to-statify-from-koko-09-09-2025/
I briefly returned to Koko Analytics but noticed two things that made me leave it for the second time for Statify. Firstly, Koko was also recording hits for random tags which did not follow from any of the posts it recorded, which suggests it has a similar issue to Statify (Koko Analytics did not show taxonomy hits prior to version 2.0.0). Secondly, speed testing shows that NLJ is a little bit faster with Statify. Thirdly, Statify has one database table while Koko Analytics has six (granting Statifyâs database grows at a quick clip due to how it saves data). Iâll look into seeing if there are some ways to make Statify a little bit more accurate (note that those ways do not include enabling async JS with ful page caching, that makes it record very little).
https://social.emucafe.org/naferrell/returning-to-koko-analytics-from-statify-09-09-2025/
Upon close inspection, Statify was over-counting in two obvious ways. First, relative to Google Search Console stats (by about ~40%), and second it was picking up things like âpage 2 of tag archive Xâ when it didnât obviously follow from the articles that had been visited before. This may have to do with my page caching (WP Super Cache, advanced caching enabled, preload enabled), albeit that wouldnât have explained the strange archive hits (tag and category archives are not cached). In any event, I saw there is a new Koko Analytics version, so I am giving it another go and not trying to re-import my old stats, which I salvaged in a Koko Analytics export in any event.
Jos Klever Web Support
Danny van Kooten
Nicholas A. Ferrell
Bunte KĂŒchenabenteuer
Blogwerk - Oliver HĂŒbner