Hi @amrevnc,
Browsing around your website, things are looking OK to me. I’m seeing the correct data being sent to the collection endpoint for every page I visit.
Can you elaborate on the drop you’re seeing? Is this in the Totals component (black section at the top of the page) or in the list of Most visited pages in the bottom left?
Hi Danny,
It is in the graph of Visitors and Pageviews. Basically, the week prior to August 15, it shows Visitors ranging from 74 to 115, which had been typical all year. The weeks since, the range is 19 to 45. Pageviews has a similar drop. Again, Google Search Console shows no drop.
That’s really weird @amrevnc.
Just browsing around your site I don’t see any issues with Koko Analytics. My visits are are all resulting in a call to /koko-analytics-collect.php which in turn is returning the correct HTTP response. So that looks as if it should all be working correctly.
One thing I did notice is that the following page is only generated partially, most likely indicating a fatal error on your site while generating that page: https://amrevnc.com/military-life/
This is not related to the Koko Analytics plugin, but since the Koko Analytics <script> tag is printed in your site’s footer and this page never makes it to printing said footer, this is affecting our plugin as well. Your PHP error log should give you more details about what is going wrong and which plugin or theme is causing it.
Good luck!
Danny
Thank you for your time, Danny.
If any other site owners see similar issues, please let us know.
Will do @amrevnc!
If your webhost gives you access to your PHP error log, make sure to check it for any fatal errors. Don’t hesitate to let me know in case you find there are any and I’d be happy to evaluate whether it’s something caused by our plugin that needs fixing.
I’m also seeing a massive drop on our page https://www.augsburg-journal.de/ to almost zero after upgrading to 2.0.
I now added /wp-content/koko-analytics/assets/dist/js/script.js to the WP Rocket blacklist and checked that all caches are cleared, hope that helps.
Thank you for letting us know, pressworthammer. If your action fixes things, please update us.
I suspect my issue is related to the 2.0 upgrade as well. I did several updates (manually) around the date I mentioned, but I didn’t notice the Koko version number, so I can’t be sure. The message to run a table update appeared soon after, which I did, so I have not tried backing out the update.
Works now, was only related to aggressive caching via WP Rocket in my case.
