Scoby Analytics

Scoby Analytics is a privacy-focused analytics plugin for WordPress. It is designed to provide website operators with actionable usage statistics without using cookies, device fingerprinting, or cross-site identifiers.
The WordPress integration is a lightweight, client-side integration that prioritizes visitor privacy. Scoby’s goal is to enable analytics in a way that can typically be operated under legitimate interest (Art. 6(1)(f) GDPR) and without consent banners, 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>
<h3>Privacy approach (GDPR / ePrivacy)</h3>
Scoby is designed around the following principles:
<ul>
<li>No cookies / no storage on the user device (relevant for ePrivacy / TDDDG)</li>
<li>No device fingerprinting</li>
<li>No user profiles or cross-site tracking</li>
<li>Anonymization before transmission and aggregated storage (no individual-level analytics)</li>
</ul>
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 non-identifying and aggregate.
<h3>What Scoby measures</h3>
Scoby provides aggregated statistics such as:
<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>
Scoby Analytics uses Scoby-operated servers for analytics processing.
<h3>Service Used</h3>
Service: Scoby Analytics Servers 
Purpose: Capture, process, and store website usage statistics in an anonymized and aggregated form to provide analytics reporting.
<h3>Data Handling and Privacy</h3>
– Anonymization prior to transmission: Page views and associated metrics are anonymized before being transmitted to Scoby Analytics servers. 
– Aggregation: Stored data is aggregated and not intended to relate to identifiable individuals. 
– No personal identifiers: Scoby is designed to avoid collecting or storing identifiers such as cookies, fingerprinting signals, or IP addresses.
<h3>Transparency and further information</h3>
– Service information: https://www.scoby.io/ 
– Terms of Use: https://www.scoby.io/terms 
– Privacy Policy: https://www.scoby.io/privacy

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

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.

Scoby Analytics vs Tinker Stats for Rybbit