pluginkollektiv

<p>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.</p>
<p>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.</p>
<h3>Data Privacy</h3>
<p>In direct comparison to statistics services such as <em>Google Analytics</em>, <em>WordPress.com Stats</em> and <em>Matomo (Piwik)</em> <em>Statify</em> doesn’t process and store personal data as e.g. IP addresses – <em>Statify</em> counts site views, not visitors.</p>
<p>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.</p>
<p>Due to this tracking approach, Statify is 100% compliant with GDPR and serves as an lightweight alternative to other tracking services.</p>
<h3>Display of the widget</h3>
<p>The plugin configuration can be changed directly in the <em>Statify</em> Widget on the dashboard by clicking the <em>Configure</em> link.</p>
<p>The amount of links shown in the <em>Statify</em> 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.</p>
<p>The statistics for the dashboard widget are cached for four minutes.</p>
<h3>Period of data saving</h3>
<p><em>Statify</em> 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.</p>
<p>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).</p>
<h3>JavaScript tracking for caching compatibility</h3>
<p>For compatibility with caching plugins like <a href="http://cachify.de" rel="nofollow ugc">Cachify</a> <em>Statify</em> offers an optional switchable tracking via JavaScript. This function allows reliable count of cached blog pages.</p>
<p>For this to work correctly, the active theme has to call <code>wp_footer()</code>, typically in a file named <code>footer.php</code>.</p>
<h3>Skip tracking for spam referrers</h3>
<p>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.</p>
<h3>Support</h3>
<p>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>.</p>
<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


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.

erravi

<p>Quantely Activity is a lightweight, privacy-conscious plugin that records visitor activity (pageviews and interactions).</p>
<p>It helps site owners understand what is happening on their website for monitoring, diagnostics, performance checks, and analytics validation. It also makes this data available to downstream analytics tools.</p>
<p>Quantely Activity runs fully on-site, uses no external services, stores data only briefly, supports cookie-free operation, does not depend on JavaScript, and does not store plain IP addresses.</p>
<h3>Key features</h3>
<h4>Robust traffic monitoring</h4>
<p>Quantely Activity captures activity reliably under imperfect conditions.</p>
<ul>
<li>Server-side pageview capture (always-on baseline)</li>
<li>Optional browser signals (clicks, forms, engagement)</li>
<li>Server-side event capture from plugins, including WooCommerce</li>
<li>Server and browser alignment via <code>pv_id</code></li>
<li>Receive-order recording with preserved origin metadata</li>
<li>Lightweight deduplication of duplicate signals</li>
</ul>
<h4>Traffic context</h4>
<p>Each hit is enriched with context for interpretation and downstream use.</p>
<ul>
<li>UTM parameters (<code>utm_source</code>, <code>utm_medium</code>, etc.)</li>
<li>Click IDs (e.g. <code>gclid</code>, <code>fbclid</code>)</li>
<li>Channel classification (email, paid, social, ai, search, referral, direct, internal)</li>
<li>Visitor continuity via cookies and derived identifiers</li>
</ul>
<h4>Engagement signals</h4>
<p>Engagement is captured efficiently using milestone-based signals.</p>
<ul>
<li>One maximum engagement value per pageview</li>
<li>Fibonacci-based milestones (<code>2–89 seconds</code>)</li>
<li>No continuous timers or heavy scripts</li>
</ul>
<h4>Internal traffic filtering</h4>
<p>Internal or irrelevant traffic can be excluded without losing visibility.</p>
<ul>
<li>Role-based exclusions (e.g. admins)</li>
<li>IP-based exclusions</li>
<li>Path-based exclusions</li>
<li>Hits remain visible but are marked (<code>is_excluded</code>)</li>
</ul>
<h4>Bot filtering</h4>
<p>Automated traffic is detected and classified at capture time.</p>
<ul>
<li><code>is_nonhuman</code>, <code>bot_label</code>, <code>bot_reason</code></li>
<li>Detection based on patterns, endpoints, and behavior</li>
<li>Reclassification possible as patterns emerge</li>
</ul>
<h3>Privacy</h3>
<p>Designed to minimize data exposure and keep control local.</p>
<ul>
<li>No plain IP storage</li>
<li>Short retention window</li>
<li>GPC / DNT support</li>
<li>No external tracking services</li>
<li>Data stored fully on-site</li>
</ul>
<h3>Integrations</h3>
<p>Captured data is structured so other tools can use it.</p>
<ul>
<li>Activity data can feed downstream analytics tools</li>
<li>Events remain connected to their original page context</li>
<li>Compatible with analytics and processing workflows</li>
</ul>
<p>Quantely Activity exposes a small developer API for integrations and downstream processing.</p>
<ul>
<li><code>qmon_hit_before_insert</code> — Filter a normalized hit array before it is stored.</li>
<li><code>qmon_hit_recorded</code> — Action fired after a hit has been stored. This is the main integration point for forwarding or persisting captured records.</li>
<li><code>qmon_event_normalize</code> — Filter a normalized event payload before it is finalized.</li>
<li><code>qmon_event_db_dedupe_window_sec</code> — Filter the database deduplication window for events.</li>
<li><code>qmon_bot_verdict</code> — Filter the bot-classification verdict before it is finalized.</li>
</ul>


Quantely Activity

See what is really happening on your WordPress website.

Statify vs Quantely Activity