Scoby Analytics

<p>Scoby Analytics is a privacy-focused analytics plugin for WordPress. It is designed to provide website operators with actionable usage statistics <strong>without using cookies, device fingerprinting, or cross-site identifiers</strong>.</p>
<p>The WordPress integration is a <strong>lightweight, client-side integration</strong> that prioritizes visitor privacy. Scoby’s goal is to enable analytics in a way that can typically be operated under <strong>legitimate interest</strong> (Art. 6(1)(f) GDPR) and <strong>without consent banners</strong>, provided it is used as intended and configured appropriately. Scoby does not provide legal advice; always assess your specific setup with your DPO/legal counsel. We’re happy to answer their questions at <a href="mailto:hello@scoby.io" rel="nofollow ugc">hello@scoby.io</a></p>
<h3>Privacy approach (GDPR / ePrivacy)</h3>
<p>Scoby is designed around the following principles:</p>
<ul>
<li><strong>No cookies / no storage on the user device</strong> (relevant for ePrivacy / TDDDG)</li>
<li><strong>No device fingerprinting</strong></li>
<li><strong>No user profiles or cross-site tracking</strong></li>
<li><strong>Anonymization before transmission</strong> and <strong>aggregated storage</strong> (no individual-level analytics)</li>
</ul>
<p>This means Scoby is not trying to “optimize consent rates”. Instead, it aims to reduce or avoid regulated processing operations in the first place by keeping analytics <strong>non-identifying</strong> and <strong>aggregate</strong>.</p>
<h3>What Scoby measures</h3>
<p>Scoby provides aggregated statistics such as:</p>
<ul>
<li>Page views and visits</li>
<li>Entry/exit pages and content performance</li>
<li>Engagement metrics (e.g., time-spent distributions/percentiles)</li>
<li>Conversion events (depending on your setup)</li>
<li>Referrers and traffic sources (without persistent identifiers)</li>
</ul>
<h3>What Scoby does not do</h3>
<ul>
<li>No cookies</li>
<li>No device fingerprinting</li>
<li>No cross-site tracking</li>
<li>No user/device profiles</li>
</ul>
<h3>Reporting & exports</h3>
<ul>
<li>WordPress dashboard reporting</li>
<li>Export to <code>.xlsx</code></li>
<li>Integrations with BI tools (e.g., Looker Studio, PowerBI, Tableau)</li>
</ul>
<h3>Third Party Services</h3>
<p>Scoby Analytics uses Scoby-operated servers for analytics processing.</p>
<h3>Service Used</h3>
<p><strong>Service:</strong> Scoby Analytics Servers<br />
<strong>Purpose:</strong> Capture, process, and store website usage statistics in an anonymized and aggregated form to provide analytics reporting.</p>
<h3>Data Handling and Privacy</h3>
<p>– <strong>Anonymization prior to transmission:</strong> Page views and associated metrics are anonymized before being transmitted to Scoby Analytics servers.<br />
– <strong>Aggregation:</strong> Stored data is aggregated and not intended to relate to identifiable individuals.<br />
– <strong>No personal identifiers:</strong> Scoby is designed to avoid collecting or storing identifiers such as cookies, fingerprinting signals, or IP addresses.</p>
<h3>Transparency and further information</h3>
<p>– Service information: https://www.scoby.io/<br />
– Terms of Use: https://www.scoby.io/terms<br />
– Privacy Policy: https://www.scoby.io/privacy</p>


Privacy-focused analytics for WordPress — designed to minimize data protection risk under EU GDPR and ePrivacy.

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.

Scoby Analytics vs Quantely Activity