Visitor statistics for WordPress with focus on data protection, transparency and clarity. Perfect as a widget in your WordPress Dashboard.
Statify provides a straightforward and compact access to the number of site views. It is privacy-friendly as it uses neither cookies nor a third party.
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.
In direct comparison to statistics services such as Google Analytics, WordPress.com Stats and Matomo (Piwik)Statify doesn’t process and store personal data as e.g. IP addresses – Statify counts site views, not visitors.
Absolute privacy compliance coupled with transparent procedures: A locally in WordPress created database table consists of only four fields (ID, date, source, target) and can be viewed at any time, cleaned up and cleared by the administrator.
Due to this tracking approach, Statify is 100% compliant with GDPR and serves as an lightweight alternative to other tracking services.
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.
Statify stores the data only for a limited period (default: two weeks), longer intervals can be selected as option in the widget. Data which is older than the selected period is deleted by a daily cron job.
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).
For compatibility with caching plugins like CachifyStatify 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
.
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.
Statify does not count the following views:
This behavior can be modified with the statify__skip_tracking
hook.
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.
Per default only administrators can see the widget. This can be changed with the statify__user_can_see_stats
hook.
Example:
add_filter( 'statify__user_can_see_stats', '__return_true' );
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.
The conditions for tracking views can be customized according to page type and user capabilities by using the hook statify__skip_tracking
.
Example:
add_filter( '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.
You can find the full changelog in our GitHub repository.
wp_die()
instead of header and exit for AJAX requests (#160)For the complete changelog, check out our GitHub repository.