Statify fournit un accès simple et compact au nombre de vues du site. Il est respectueux de la vie privée car il n’utilise ni cookies ni tiers.

An interactive chart is followed by lists of the most common reference sources and target pages. The period of statistics and length of lists can be set directly in the dashboard widget.

Data Privacy

En comparaison avec les services de statistiques tels que Google Analytics, Statistiques et Matomo (ex Piwik), Statify ne traite pas et ne stocke pas les données personnelles comme par exemple l’adresses IP – Statify compte les vues du site, pas les visiteurs.

Conformité absolue à la confidentialité associée à des procédures transparentes : une table de base de données créée localement dans WordPress ne comprend que quatre champs (ID, date, source, cible) et peut être consultée à tout moment, nettoyée et effacée par l’administrateur.

En raison de cette approche de suivi, Statify est 100 % conforme au RGPD et sert d’alternative légère aux autres services de suivi.

Display of the widget

The plugin configuration can be changed directly in the Statify Widget on the dashboard by clicking the Configure link.

The amount of links shown in the Statify Widget can be set as well as the option to only count views from today. Of course, older entries are not deleted when changing this setting.

The statistics for the dashboard widget are cached for four minutes.

Période d’enregistrement des données

Statify stocke les données uniquement pour une période limitée (par défaut : deux semaines), des intervalles plus longs peuvent être sélectionnés en option dans le widget. Les données antérieures à la période sélectionnée sont supprimées par une tâche cron quotidienne.

An increase in the database volume can be expected because all statistic values are collected and managed in the local WordPress database (especially if you increase the period of data saving).

JavaScript tracking for caching compatibility

For compatibility with caching plugins like Cachify Statify offers an optional switchable tracking via JavaScript. This function allows reliable count of cached blog pages.

For this to work correctly, the active theme has to call wp_footer(), typically in a file named footer.php.

Skip tracking for spam referrers

The comment blacklist can be enabled to skip tracking for views with a referrer URL listed in comment blacklist, i. e. which considered as spam.


If you’ve problems or think you’ve found a bug (e.g. you’re experiencing unexpected behavior), please post at the support forums.


  • Active development of this plugin is handled on GitHub.
  • Pull requests for documented bugs are highly appreciated.
  • If you want to help us translate this plugin you can do so on WordPress Translate.

Captures d’écran

  • Statify dashboard widget
  • Statify dashboard widget settings
  • Statify settings page


Which areas are excluded from counting?

Statify does not count the following views:

  • feeds
  • trackbacks
  • searches
  • previews
  • views by logged in users (unless tracking is activated via the settings page)
  • error pages
  • favicon (as of WP 5.4)
  • sitemap (as of WP 5.5)

This behavior can be modified with the statify__skip_tracking hook.

Can further visitor data be recorded?

Some plugin users want to capture additional visitor data, e.g. name of the device and resolution.
Statify counts exclusively page views and no visitors, the desired data acquisition is not a question.

Comment modifier qui peut voir le widget du tableau de bord ?

Per default only administrators can see the widget. This can be changed with the statify__user_can_see_stats hook.



has to be added to the theme’s functions.php and adapted to your needs. This example would allow all users to see the widget.

Editing the configuration is still limited to users with edit_dashboard capability.

How to skip tracking for defined users or pages

Les conditions de suivi des vues peuvent être personnalisées en fonction du type de page et des capacités de l’utilisateur en utilisant le crochet Web statify__skip_tracking.


    function() {
        if ( condition ) {
            return true;

        return false;

has to be added to the theme’s functions.php. The condition has modified such that the method returns true if and only if the view should be ignored.

Comment consolider cette extension ?


24 septembre 2020
Statify ist einfach ein großartiges Statistik-Plugin ohne Schnick, Schnack. Außerdem Datenschutz konform. Was will man mehr? Nichts! Danke!
29 avril 2020
I've been using this plugins for years, now even more with the GDPR.
15 avril 2020
Free, working fine and gives you the absolute basic data for your website. The best, I think, is that it is GDPR/DSGVO conform without having to urge the website visitor to give consent to data use, tracking or cookies etc which is necessary for its big brothers Google Analytics or even PIWIK/Matomo. Love it, thanks!
13 février 2020
All I wanted was a basic stat plugin for a new site that gave me referrals and pages most viewed. That's what this does, while also not using cookies or destroying your reader's privacy. it is also a 30 second installation and then it just works. Brilliant. Love it. Thanks!!
Lire les 38 avis

Contributeurs & développeurs

« Statify » est un logiciel libre. Les personnes suivantes ont contribué à cette extension.


“Statify” a été traduit dans 19 locales. Remerciez l’équipe de traduction pour ses contributions.

Traduisez « Statify » dans votre langue.

Le développement vous intéresse ?

Parcourir le code, consulter le SVN dépôt, ou s’inscrire au journal de développement par RSS.


You can find the full changelog in our GitHub repository.


  • Update documentation links (#204)
  • Minor markup fix on settings page (#206)
  • Dashboard widget is closeable again (#208) (#209)
  • Fix static initialization on multisite with PHP 8 (#210, props @walterebert)
  • Tested up to WordPress 5.8


  • Minor adjustments for the dashboard widget (#197) (#199)
  • Tested up to WordPress 5.7


  • Fix AMP compatibility for Standard and Transitional mode (#181) (#182)
  • JavaScript is no longer embedded if request is served by AMP (#181) (#182)
  • Always register the action for the cleanup (#184)
  • Exclude sitemap calls (WP 5.5+) from tracking (#185) (#186)
  • Tested up to WordPress 5.6


  • Fix date offset in dashboard widget in WP 5.3+ environments with mixed timezones (#167)
  • Allow to deactivate the nonce check during JavaScript tracking (#168)
  • Add support for « disallowed_keys » option instead of « blacklist_keys » in WordPress 5.5 (#174)
  • Add refresh button in the dashboard, increase caching time (#157)


  • Prevent JavaScript tracking from raising 400 for logged-in users, if tracking is disabled (#159)
  • Use wp_die() instead of header and exit for AJAX requests (#160)
  • Fix 1 day offset between display range and number of days evaluated in top lists (#162)


  • Fix refresh of the dashboard widget when settings have been changed through the settings page (#147)
  • Fix Cachify cache not being flushed after changing JavaScript settings (#152)
  • Fix date inconsistency for number of total visits (#150)
  • Extend user agent filter for bot detection (#149) (#151)
  • Update tooltip library (containing a bugfix in IE 11) (#156)


  • Fix JavaScript embedding when bots visit before caching (#84) (#86)
  • Fix offset in visitor reporting due to different timezones between PHP and database (#117, props @sophiehuiberts)
  • Fix untranslatable support link (#122) (#126, props @arkonisus)
  • Add separate settings page and reduced widget backview to widget settings only (#111)
  • Add options to track logged in users (#103) (#111)
  • Add option to show total visits (#134, props @yurihs)
  • Refactored JavaScript tracking to use WP AJAX (#109) (#142)
  • Introduced new option to separate display from storage range (#72)
  • Automatically add AMP analytics trigger if official AMP PlugIn is installed (#110) (#116, props @tthemann)
  • Dashboard widget is now scrollable with dynamic point radius to keep long-term statistics readable (#71) (#101, props @manumeter)
  • Improved bot detection (#112) (#125, props @mahype)
  • Updated Chartist JS library for dashboard widget (#132)
  • Skip tracking for favicon.ico redirects (since WP 5.4) (#144)
  • Tested up to WordPress 5.4

For the complete changelog, check out our GitHub repository.