Tinker Stats for Rybbit

Tinker Stats for Rybbit integrates your self-hosted Rybbit Analytics 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:

• One-click setup — enter your connection details, click Test Connection, and the tracking script is ready to enable.
• 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.
• Script injection — adds the Rybbit tracking script to your frontend via wp_enqueue_script() with configurable script URL, debounce, and session replay.
• Role exclusion — exclude specific WordPress roles (e.g. administrators, editors) from being tracked.
• User identification — optionally send logged-in user ID, display name, and role to Rybbit via rybbit.identify().
• Custom events — fire per-type events (post_view, page_view, archive_view, search_view, etc.) with WordPress metadata as event properties.
• 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.

Admin Content Stats Display:

• Post list column — see view counts for every post at a glance. Click any count to open a detailed chart.
• Chart modal — daily breakdown with Year/Month/Week tabs and period navigation. Shows total count with percentage change vs previous period.
• Dashboard widget — site-wide traffic chart, total count with trend indicator, and top 10 pages.
• Publish box stat — current month view count right in the editor, clickable to open the chart modal.
• Postmeta sync — hourly cron job saves view counts to post meta for use by themes, page builders, and other plugins.
• Configurable metric — choose between Pageviews, Visits (sessions), or Users.

Security & Privacy:

• Encrypted API key — your Rybbit API key is stored encrypted in the database.
• Caching — configurable transient caching to minimize API calls to your Rybbit instance.
• API resilience — automatic backoff on errors prevents cascading failures.
• View permissions — restrict who can see stats in the admin.
• Privacy-first — Rybbit is cookieless and GDPR-friendly. No data leaves your infrastructure.

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:

• A running self-hosted Rybbit Analytics instance (tested with v2.5.0)
• A Rybbit API key (generated in Settings → Account → API Keys)
• WordPress 6.3 or later

Multisite

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.

Rybbit + Multisite URL patterns

Rybbit organizes data per registered domain or subdomain, which affects how multisite installs map to Rybbit sites:

• Subdomain subsites (e.g. sub.example.com) — each can be added as its own Rybbit site for clean separation.
• Domain-mapped subsites (e.g. example2.com) — each is added as its own Rybbit site, identical to single-site usage.
• Subdirectory subsites (e.g. example.com/sub) — 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.

If you proxy the Rybbit script through a relative path (e.g. /api/script.js), make sure the proxy is configured on each subsite’s domain.