jinaldesai

FlareStats brings your CloudFlare web analytics data directly into the WordPress admin. No third-party tracking services, no cookies — just privacy-preserving analytics from Cloudflare.
<h4>Features</h4>
<ul>
<li>Dashboard Widget — A compact summary widget on the WordPress Dashboard.</li>
<li>Full Analytics Screen — Dedicated admin page with a 7-day daily chart, top 5 pages, and top 3 countries.</li>
<li>Last 7 Days — Data always covers the rolling last 7 days.</li>
<li>Cloudflare GraphQL API — Connects to the Cloudflare GraphQL Analytics API using your API Token.</li>
<li>Lightweight & Dependency-Free — No external JavaScript frameworks; charts are CSS-based.</li>
<li>Caching — API responses cached via WordPress transients to minimise API calls.</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>A <a href="https://cloudflare.com" rel="nofollow ugc">Cloudflare</a> account with Web Analytics enabled for your site.</li>
<li>A Cloudflare API Token with Account Analytics: Read permission.</li>
<li>Your Cloudflare Account ID.</li>
<li>Your FlareStats Site Tag (optional but recommended for multi-site accounts).</li>
</ul>
<h4>Configuration</h4>
<ol>
<li>In your Cloudflare dashboard go to My Profile → API Tokens and create a token with Account Analytics: Read permission scoped to your account.</li>
<li>Note your Account ID (visible in the Cloudflare dashboard right-hand sidebar).</li>
<li>Go to Analytics & Logs → Web Analytics, select your site, and copy the Site Tag from the site settings (optional).</li>
<li>In WordPress go to FlareStats → Settings and enter your credentials.</li>
</ol>
<h4>Privacy / Tracking Disclosure</h4>
FlareStats displays analytics data inside WordPress by requesting reports from Cloudflare Web Analytics.
What this plugin sends to external services
<ul>
<li>This plugin sends authenticated requests from your WordPress site to the Cloudflare GraphQL API (<code>api.cloudflare.com</code>) using your configured API token, account ID, and site tag (if provided).</li>
<li>Request parameters include reporting date ranges and query fields needed to fetch analytics metrics.</li>
</ul>
What this plugin receives
<ul>
<li>Aggregated analytics data such as pageviews, visits, top pages, top countries, browser/device, and referrer/source metrics.</li>
<li>This plugin displays those metrics in the WordPress admin dashboard and analytics screens.</li>
</ul>
What this plugin stores in WordPress
<ul>
<li>Plugin settings in <code>wp_options</code> (for example API token, account ID, site tag, cache duration).</li>
<li>Cached analytics responses in WordPress transients to reduce API calls.</li>
</ul>
Personal data handling
<ul>
<li>This plugin does not create its own visitor tracking cookies.</li>
<li>Visitor analytics collection is performed by Cloudflare Web Analytics on your site.</li>
<li>This plugin does not add separate per-visitor profile records in WordPress for analytics.</li>
</ul>
Data retention / access
<ul>
<li>Cached analytics data is temporary and expires according to the configured cache duration.</li>
<li>Plugin settings and analytics screens are only accessible to users with appropriate admin capabilities (for example <code>manage_options</code>).</li>
</ul>
Third-party policies
<ul>
<li>Cloudflare Privacy Policy: https://www.cloudflare.com/privacypolicy/</li>
<li>Cloudflare Terms: https://www.cloudflare.com/website-terms/</li>
</ul>
Site owners are responsible for ensuring their site’s public privacy policy accurately describes how Cloudflare Web Analytics is used.

FlareStats

Display CloudFlare Web Analytics data — pageviews, visitors, top pages and top countries — right in your WordPress admin.

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.

FlareStats vs Tinker Stats for Rybbit