Tim Boulley

BT Visitor Insights is a privacy-friendly, self-hosted analytics plugin. Everything stays on your server — no Google Analytics, no third-party tracking scripts, no data sent to any external analytics platform.
Activate it and your dashboard starts filling with real visitor data: where they’re from, what pages they viewed, what device they’re on, and how long they’ve been around.
<h4>Why use it?</h4>
<ul>
<li>No third-party tracking. All visitor data stays in your WordPress database.</li>
<li>Zero configuration. Activate the plugin and data starts collecting immediately.</li>
<li>Lightweight. No bulky frontend tracking script — tracking happens server-side, so it works alongside any caching plugin.</li>
<li>Real-time. See who’s on your site right now (last 15 minutes).</li>
<li>Respectful. Honors the Do Not Track browser header and skips logged-in administrators.</li>
</ul>
<h4>Features</h4>
<ul>
<li>Real-time active-visitor count</li>
<li>IP geolocation — city, region, country, country flag</li>
<li>Page view tracking with titles and referrers</li>
<li>Device detection — desktop, mobile, tablet</li>
<li>Browser and operating system breakdown</li>
<li>Top pages, top referrers, top countries</li>
<li>30-day visual bar chart</li>
<li>Per-visitor history — click any IP to see every page they viewed</li>
<li>Date-range filters — today, 7 days, 30 days, 90 days, all time</li>
<li>Auto-cleanup — old data is purged based on your configurable retention period (default 90 days)</li>
<li>IP exclusion list and IP anonymization (in Settings)</li>
<li>CSV export of visitors and page views</li>
<li>Dashboard widget on the WP admin home screen</li>
<li>Admin bar badge with live visitor count</li>
<li>Skips bots, crawlers, and logged-in admins</li>
<li>Respects the Do Not Track header</li>
</ul>
<h4>Pro version</h4>
A <a href="https://boulleytechnology.ca/bt-visitor-insights.php" rel="nofollow ugc">Pro version</a> adds:
<ul>
<li>Email digests — daily or weekly HTML report with stats, top pages, and trend comparisons</li>
<li>Traffic-spike alerts — get an email when page views exceed your normal baseline</li>
<li>Geo-blocking — block or redirect visitors from specific countries</li>
<li>Scheduled CSV exports — weekly or monthly automated email exports</li>
<li>Goals & conversions — track URL-based goals and unique converters</li>
<li>REST API access — query stats, visitors, and page views via /wp-json/btvi/v1/</li>
<li>Multi-site rollup — aggregate stats from multiple WordPress sites in one dashboard</li>
<li>White-label dashboard — customize the menu label and page title for client sites</li>
<li>Unlimited data retention — keep visitor history forever</li>
</ul>
The Pro version is sold separately and is not required to use this free plugin.
<h3>External Services</h3>
This plugin uses the ip-api.com geolocation API to look up the city, region, and country for each new visitor IP address. This request is made server-side from your WordPress installation when a visitor is first seen.
<ul>
<li>Service: ip-api.com</li>
<li>What is sent: the visitor’s IP address</li>
<li>When: once per unique visitor IP, server-side</li>
<li>Privacy policy: https://ip-api.com/docs/legal</li>
<li>Terms of service: https://ip-api.com/docs/legal</li>
</ul>
No data is sent to Boulley Technology or any other third party.

BT Visitor Insights

Lightweight, self-hosted visitor analytics with IP geolocation, page views, device detection, and a real-time dashboard. No third-party scripts.

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.

BT Visitor Insights vs Tinker Stats for Rybbit