by TinkerCoded
0 (0 reviews)
Tinker Stats for Rybbit
Rybbit Analytics integration — tracking script management, admin content stats, and postmeta sync for self-hosted Rybbit.
Tested up to WP 6.9.5 (Current: 7.0.2)
v1.4.1.3
Current Version v1.4.1.3
Updated 2 months ago
Last Update on 10 May, 2026
Refreshed 13 hours ago
Last Refreshed on
Rank
#53,026
—
No change
Active Installs
0+
—
No change
KW Avg Position
35.5
—
No change
Downloads
147
+2 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
16,274
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 6 more installs to reach 10+
Rank Changes
Current
#53,026
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 2 of 2Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.4.1.3
- Last Updated
- May 10, 2026
- Requires WP
- 6.3+
- Tested Up To
- 6.9.5
- PHP Version
- 7.4 or higher
- Author
- TinkerCoded
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
7K+ installs
#2,730
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#988
Site Kit by Google - Analytics, Search Console, AdSense, Speed
5M+ installs
#8
MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy)
2M+ installs
#24
ManageWP Worker
1M+ installs
#53
Frequently Asked Questions
Common questions about Tinker Stats for Rybbit
Rybbit is an open-source, privacy-friendly web analytics platform — a modern alternative to Google Analytics. It supports self-hosting and tracks visitors without cookies.
Yes, if you enable it. The Tracking section lets you inject the Rybbit tracking script on your frontend with one toggle. You can also configure role exclusion, user identification, and custom events. If tracking is disabled, the plugin only reads existing analytics data from your Rybbit instance via its API.
Every hour, the plugin fetches lifetime cumulative metrics from Rybbit and saves them as post meta (_tinker_stats_views). This makes view counts available to themes, page builders, and sorting queries. The stored value is a running total from the date your Rybbit site was first created — it doesn't reset at month boundaries. The plugin auto-detects this start date from your Rybbit instance the first time it syncs; if the connection details change (different Rybbit instance or different Site ID), the start date is re-detected on the next sync.
Yes. Go to Tinker Stats → Settings and click "Sync Postmeta Now" in the Tools section.
Yes. The API key is encrypted using AES-256-CBC with keys derived from your WordPress salts before being stored in the database.
The most common cause is ad blockers (uBlock Origin, Brave's built-in blocker, etc.) blocking the Rybbit tracking script. Even though Rybbit is privacy-friendly and cookieless, some blocklist maintainers block all analytics scripts indiscriminately. Estimates put the impact between 6% and 60% of visitors depending on your audience's technical level. A common gotcha: ad blocker filter lists also match on URL keywords. Words like "stats", "analytics", "tracking", "metrics", or "telemetry" anywhere in the script URL will trigger blockers regardless of the actual script content. If your Script URL contains any of these, expect blocking even before the request reaches your server. The fix is to proxy the tracking script through your own domain so it loads as a first-party request. The plugin includes a built-in proxy that handles this for you: go to Tinker Stats → Settings → Tracking and enable the "Bypass Ad Blockers" toggle. The plugin will fetch and cache the Rybbit script, generate a randomized first-party path, and forward all tracking events through your own domain. No webserver config required. If you'd rather configure the proxy yourself at the webserver or CDN level, see Rybbit's proxy guide and enter the relative path (e.g. /api/script.js) in the Script URL field. To verify your tracking is actually firing, open your Rybbit dashboard, go to Site Settings → Tracking Script, and click "Verify Installation". Rybbit will check whether the script is loading on your site and confirm the connection. Other less common causes: tracking is disabled in the plugin settings, your role is in the Exclude Roles list, or the tracking ID isn't populated yet.
When enabled, the plugin generates a randomized 8-character hex prefix (e.g. k3p9m2qr) and serves the Rybbit tracking script and tracking endpoints through https://yoursite.com/[hash]/.... Static script files are cached locally and refreshed daily; tracking POSTs are forwarded to your Rybbit instance in real time, with the visitor's real IP address preserved via X-Forwarded-For. The randomized prefix breaks ad blocker rules that anchor on the platform-pattern /api/ path used by analytics services. You can regenerate paths anytime, refresh the script cache manually, and verify proxy reachability with the Test Proxy button. The proxy works on most hosts without webserver-level changes. On WordPress Multisite, each subsite gets its own proxy paths (subdirectory subsites can share the parent domain's Rybbit Site ID; subdomain and mapped-domain subsites have their own).
The tracking script is injected into your page HTML via wp_enqueue_script(), so it becomes part of the cached HTML output. This is normally desirable: once cached, the script tag is served on every page hit without any per-request PHP work. The trade-off: if you enable, disable, or change tracking settings, your cached HTML still reflects the previous state. You'll need to purge your page cache (FastCGI, Cloudflare, Varnish, etc.) for the change to take effect on the frontend. The built-in proxy's cached script files (/tsr-{hash}/script.js etc.) are static files at WordPress root, served directly by your webserver. They're independent of WordPress page caching: they refresh on their own daily-cron schedule and aren't affected by page cache purges.