pluginkollektiv

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.
<h3>Data Privacy</h3>
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.
<h3>Display of the widget</h3>
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.
<h3>Period of data saving</h3>
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).
<h3>JavaScript tracking for caching compatibility</h3>
For compatibility with caching plugins like <a href="http://cachify.de" rel="nofollow ugc">Cachify</a> 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 <code>wp_footer()</code>, typically in a file named <code>footer.php</code>.
<h3>Skip tracking for spam referrers</h3>
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.
<h3>Support</h3>
If you’ve problems or think you’ve found a bug (e.g. you’re experiencing unexpected behavior), please post at the <a href="https://wordpress.org/support/plugin/statify" rel="ugc">support forums</a>.
<h3>Contribute</h3>
<ul>
<li>Active development of this plugin is handled <a href="https://github.com/pluginkollektiv/statify" rel="nofollow ugc">on GitHub</a>.</li>
<li>Pull requests for documented bugs are highly appreciated.</li>
<li>If you want to help us translate this plugin you can do so <a href="https://translate.wordpress.org/projects/wp-plugins/statify" rel="nofollow ugc">on WordPress Translate</a>.</li>
</ul>

Statify

Great Plugin without using cookies!
Good work ;-)


Simple an clean statistic plugin. Just works.


Just simple stats.


A simple stats package that runs on your own site, so you aren't sending visitor data to some third party service just to count page views. Not as full-featured as Jetpack Stats, but much more privacy-friendly! Good for the basic use case of "where are most of my visitors coming from and what are the reading the most?" Works with ClassicPress too!


Simple, privacy-friendly stats

Visitor statistics for WordPress with focus on data protection, transparency and clarity. Perfect as a widget in your WordPress Dashboard.

TinkerCoded

Tinker Stats for Rybbit integrates your self-hosted <a href="https://rybbit.io" rel="nofollow ugc">Rybbit Analytics</a> instance with WordPress. It manages your Rybbit tracking script on the frontend and surfaces content traffic stats directly in your admin; post list columns, editor publish box, and dashboard widget.
Tracking Script Management:
<ul>
<li>One-click setup — enter your connection details, click Test Connection, and the tracking script is ready to enable.</li>
<li>Built-in proxy — bypass ad blockers with one toggle. The plugin serves the tracking script and forwards events through your own domain. No webserver config needed.</li>
<li>Script injection — adds the Rybbit tracking script to your frontend via <code>wp_enqueue_script()</code> with configurable script URL, debounce, and session replay.</li>
<li>Role exclusion — exclude specific WordPress roles (e.g. administrators, editors) from being tracked.</li>
<li>User identification — optionally send logged-in user ID, display name, and role to Rybbit via <code>rybbit.identify()</code>.</li>
<li>Custom events — fire per-type events (<code>post_view</code>, <code>page_view</code>, <code>archive_view</code>, <code>search_view</code>, etc.) with WordPress metadata as event properties.</li>
<li>Error suppression — suppress cross-origin “Script error.” messages from the tracking script. This is related to a bit of a bug in Rybbit error reporting and merely cleans up session reports.</li>
</ul>
Admin Content Stats Display:
<ul>
<li>Post list column — see view counts for every post at a glance. Click any count to open a detailed chart.</li>
<li>Chart modal — daily breakdown with Year/Month/Week tabs and period navigation. Shows total count with percentage change vs previous period.</li>
<li>Dashboard widget — site-wide traffic chart, total count with trend indicator, and top 10 pages.</li>
<li>Publish box stat — current month view count right in the editor, clickable to open the chart modal.</li>
<li>Postmeta sync — hourly cron job saves view counts to post meta for use by themes, page builders, and other plugins.</li>
<li>Configurable metric — choose between Pageviews, Visits (sessions), or Users.</li>
</ul>
Security & Privacy:
<ul>
<li>Encrypted API key — your Rybbit API key is stored encrypted in the database.</li>
<li>Caching — configurable transient caching to minimize API calls to your Rybbit instance.</li>
<li>API resilience — automatic backoff on errors prevents cascading failures.</li>
<li>View permissions — restrict who can see stats in the admin.</li>
<li>Privacy-first — Rybbit is cookieless and GDPR-friendly. No data leaves your infrastructure.</li>
</ul>
This plugin is not an official Rybbit product and is not affiliated with or endorsed by Rybbit. Rybbit trademarks, logos, and brand assets remain the property of their respective owner.
Requirements:
<ul>
<li>A running self-hosted <a href="https://rybbit.io" rel="nofollow ugc">Rybbit Analytics</a> instance (tested with v2.5.0)</li>
<li>A Rybbit API key (generated in Settings → Account → API Keys)</li>
<li>WordPress 6.3 or later</li>
</ul>
<h3>Multisite</h3>
The plugin works on WordPress Multisite networks (subdirectory, subdomain, and domain-mapped). The plugin can be activated per-subsite or network-wide; either works. Each subsite has its own Tinker Stats menu and runs its own postmeta sync.
How independently each subsite can be configured depends on Rybbit’s per-domain data model. Subdomain and domain-mapped subsites can each connect to their own Rybbit site. Subdirectory subsites must share the parent domain’s Rybbit configuration (Site ID, Tracking ID, URL, and API key), since Rybbit organizes data per registered domain or subdomain rather than by URL path. The URL patterns section below has the full breakdown.
<h4>Rybbit + Multisite URL patterns</h4>
Rybbit organizes data per registered domain or subdomain, which affects how multisite installs map to Rybbit sites:
<ul>
<li>Subdomain subsites (e.g. <code>sub.example.com</code>) — each can be added as its own Rybbit site for clean separation.</li>
<li>Domain-mapped subsites (e.g. <code>example2.com</code>) — each is added as its own Rybbit site, identical to single-site usage.</li>
<li>Subdirectory subsites (e.g. <code>example.com/sub</code>) — Rybbit doesn’t support path-based site separation, so all subdirectory subsites must be configured with the same Rybbit Site ID, Tracking ID, URL, and API key as the parent domain. In Rybbit’s dashboard, all subdirectory subsite traffic appears under the parent domain’s site; use Rybbit’s URL/path filters to view per-subsite breakdowns.</li>
</ul>
If you proxy the Rybbit script through a relative path (e.g. <code>/api/script.js</code>), make sure the proxy is configured on each subsite’s domain.

Tinker Stats for Rybbit

Rybbit Analytics integration — tracking script management, admin content stats, and postmeta sync for self-hosted Rybbit.

Statify vs Tinker Stats for Rybbit