Title: Cloudflare
Last modified: September 27, 2025

---

# Cloudflare

 *  Resolved [tomoffinlandfoundation](https://wordpress.org/support/users/tomoffinlandfoundation/)
 * (@tomoffinlandfoundation)
 * [8 months, 2 weeks ago](https://wordpress.org/support/topic/cloudflare-63/)
 * Can Statify work when using Cloudflare?

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Support [Torsten Landsiedel](https://wordpress.org/support/users/zodiac1978/)
 * (@zodiac1978)
 * [8 months, 1 week ago](https://wordpress.org/support/topic/cloudflare-63/#post-18665080)
 * Hi [@tomoffinlandfoundation](https://wordpress.org/support/users/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
 *  Thread Starter [tomoffinlandfoundation](https://wordpress.org/support/users/tomoffinlandfoundation/)
 * (@tomoffinlandfoundation)
 * [8 months, 1 week ago](https://wordpress.org/support/topic/cloudflare-63/#post-18665987)
 * 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.
    -  This reply was modified 8 months, 1 week ago by [tomoffinlandfoundation](https://wordpress.org/support/users/tomoffinlandfoundation/).
 *  Plugin Support [Torsten Landsiedel](https://wordpress.org/support/users/zodiac1978/)
 * (@zodiac1978)
 * [8 months, 1 week ago](https://wordpress.org/support/topic/cloudflare-63/#post-18666532)
 * Hi [@tomoffinlandfoundation](https://wordpress.org/support/users/tomoffinlandfoundation/)
 * if you use site caching, the tracking method of Statify needs to be set to JavaScript:
   
   [https://statify.pluginkollektiv.org/documentation/settings/](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](https://wordpress.org/plugins/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()`](https://developer.wordpress.org/reference/functions/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](https://codex.wordpress.org/WordPress_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](https://codex.wordpress.org/WordPress_Nonces#Modifying_the_nonce_lifetime),
   > decrease the caching time, or deactivate the nonce check.
   >  [https://statify.pluginkollektiv.org/documentation/settings/](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

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Cloudflare’ is closed to new replies.

 * ![](https://ps.w.org/statify/assets/icon-256x256.png?rev=2355063)
 * [Statify](https://wordpress.org/plugins/statify/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/statify/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/statify/)
 * [Active Topics](https://wordpress.org/support/plugin/statify/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/statify/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/statify/reviews/)

## Tags

 * [cache](https://wordpress.org/support/topic-tag/cache/)

 * 3 replies
 * 2 participants
 * Last reply from: [Torsten Landsiedel](https://wordpress.org/support/users/zodiac1978/)
 * Last activity: [8 months, 1 week ago](https://wordpress.org/support/topic/cloudflare-63/#post-18666532)
 * Status: resolved