Hi @tomoffinlandfoundation
Cloudflare is a company with many services. You need to be more specific, otherwise no one can help you to answer this question.
I think it should work without any problems, looking at the services, but maybe I’m missing something. If you can post some details, we can better check if everything should work fine.
You can also try it out and report any issues if they arise.
All the best
Torsten
CDN site caching, the thing that 99% of sites use CloudFlare! Many stats tools that work at the webserver level cannot give accurate stats as CloudFlare is serving the content.
Hi @tomoffinlandfoundation
if you use site caching, the tracking method of Statify needs to be set to JavaScript:
https://statify.pluginkollektiv.org/documentation/settings/ (Section: “Tracking method”)
For your convenience, I quote the whole paragraph here:
Tracking method
Per default, Statify does not require JavaScript. Every view of a WordPress generated page is counted.
If a caching plugin such as Cachify is installed, Statify can not correctly log the page calls (possibly) in normal mode, because blog pages are sent directly from the plugin cache and Statify is bypassed. Therefore Statify is equipped with optional JavaScript tracking which can be activated by selecting it under “tracking method”: A prepared JavaScript snippet is injected into each blog page and triggers the tracking mechanism client side.
For the correct approach of the function, the template footer.php must have the function call wp_footer() (depending on the WordPress theme used). Requests to the WordPress Ajax endpoint (wp-admin/admin-ajax.php) must be allowed (the default).
After switching to JavaScript tracking you may clear the cache of your site to take the changes into effect for all posts immediately.
When using longer caching times, AJAX-Tracking may fail, because the cached security tokens (so called nonces) may have expired. If you are uncomfortable raising the nonce lifetime (12 to 24 hours by default) there is the option “JavaScript based tracking without nonce check” (since Statify 1.8.0) that bypasses this check and allows Statify to always track views.
You can check whether your site is affected by this problem in the server log files by looking for requests for /wp-admin/admin-ajax.php rejected with status code 403. In this case you can increase the nonce lifetime, decrease the caching time, or deactivate the nonce check.
https://statify.pluginkollektiv.org/documentation/settings/
So don’t forget to purge the cache after you set it up and look at the caching time to prevent broken nonces.
All the best
Torsten
