Turf Stats
| 开发者 | freakstar |
|---|---|
| 更新时间 | 2026年7月17日 14:23 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Turf is a self-hosted, cookieless analytics plugin. No Google Analytics, no
Jetpack, no external network calls - everything is measured and stored in your
own WordPress database.
Why Turf
- Cookieless. Visitor deduplication uses a one-way hash of IP + user-agent, never a cookie and never the raw IP address.
- Self-hosted. All data lives in your own database; nothing is sent to any third party.
- Zero configuration. Every public post type and taxonomy is tracked automatically, including ones you add later.
- Page views (deduplicated and raw), unique visitors, views per visitor, and average visit duration
- Device, browser, operating system, language, and country (via Cloudflare's header when available - no GeoIP lookups)
- Referrers / traffic sources, UTM campaign parameters, and automatic outbound link tracking (full destination URL + the page clicked from)
- New vs. returning visitors, scroll depth, and reading time
- On-site search terms, including zero-result searches
- Visitor routes (page-to-page transitions), landing pages, and a bounce-rate proxy - all reconstructed from sessions
- Cache offload: how much traffic is served by a page cache (SiteGround, Cloudflare, ...) instead of hitting WordPress
- 404 hits, comments per period, editorial content activity, per-author stats
- Bots & LLM crawlers (Googlebot, GPTBot, ClaudeBot, ...) - tracked server-side and kept separate from human visitor numbers
- WooCommerce funnel (views, add to cart, checkout) and form submissions (Contact Form 7, Gravity Forms) when those plugins are active
安装:
- Install and activate the plugin.
- That's it - views start counting immediately for every public post type and taxonomy. Find the reports under the "Statistics" menu in wp-admin.
屏幕截图:
常见问题:
Does Turf set cookies or require a consent banner?
Turf sets no cookies and sends no data to any external service. Deduplication uses a one-way hash of IP + user-agent; the raw IP is never stored. It is designed to fit a "legitimate interest" basis for first-party, aggregate analytics - but that is not legal advice: check with whoever maintains your privacy policy.
What data does Turf collect, and where does it go?
Per page view Turf stores, in your own database only: a one-way visitor hash, timestamp, the page viewed, device type / browser / OS family (parsed from the user-agent), language, country code (only if Cloudflare provides it), referrer hostname, UTM parameters, scroll depth, and reading time. Raw event rows are pruned automatically after 18 months (filterable); aggregate totals are kept. Nothing is ever transmitted off your server.
Why are Turf's numbers lower than Jetpack's or a raw hit counter's?
"Views" is deduplicated: a repeat view of the same page by the same visitor within 30 minutes doesn't count again (the same default Google Analytics and Matomo use). The separate "Raw views" number counts every page load, for an apples-to-apples comparison with hit-counting tools.
Does it work with page caching?
Yes. Tracking runs client-side, so cached pages are still counted. Turf even reports how much of your traffic is served from cache.
Where is the country data coming from?
From Cloudflare's CF-IPCountry request header, if your site is behind Cloudflare. Turf deliberately does not call any geolocation API - that would mean sending visitor IPs to a third party. Without Cloudflare, country stays empty unless you hook up your own local database via the turf_visitor_country filter.
Does uninstalling remove my statistics?
By default, no - analytics history is precious, so the data survives an
uninstall/reinstall. To remove everything on uninstall, add
define( 'TURF_REMOVE_DATA_ON_UNINSTALL', true ); to wp-config.php (or set
the turf_remove_data_on_uninstall option to 1) before deleting the plugin.
Where do I suggest a feature or report a bug?
On the plugin's GitHub repository: https://github.com/fbloemhof/turf-stats/issues
更新日志:
1.21.1
- Fixed the "Formulieren" (Forms), "Top search terms" and "Most discussed" boxes on the Analysis/Statistics pages silently disappearing for any period other than "All time" - a broken date filter made the underlying query invalid SQL, so it failed silently and the box was dropped.
- New
[turf_stats]shortcode: an at-a-glance table (online now, today, yesterday, last 7 days, last 28 days) for a sidebar Text/HTML widget or Shortcode block, withmetric(views/visitors),layout(table/list) anditemsattributes to customize which rows show. - Fixed a corrupted Dutch (nl_NL) .mo file (duplicate "Online now" source string made it fail to compile, and the compiled file itself wasn't a valid sorted .mo) - Dutch translations were silently not loading.
- Screen resolution breakdown labels are now English source strings with Dutch translations in the language file (was accidentally Dutch in code).
- Daily chart window math extracted into a shared turf_day_window() helper so the single-day and 7-day windows no longer duplicate the timezone logic.
- Fixed TURF_VERSION (the cache-busting version for all enqueued JS/CSS) being stuck at 1.19.0 since the 1.20.0 release - every asset change since then was shipped under an unchanged version string.
- Fixed daily bar chart on the Today/Yesterday/fixed-date tabs: it showed only the anchor day (plus a sliver of the day before under a non-UTC site timezone) instead of the intended 7-day context window. The chart query now spans the 7 days ending on the selected day, matching the 7 bars it renders. Regression from 1.20.0 (date navigation).
- Screen resolution: fall back to viewport innerWidth/innerHeight in the tracking JS when window.screen reports 0 or is missing (in-app webviews, fingerprinting-protected browsers) so fewer views land in "unknown".
- Screen resolution breakdown now separates App/REST API views (which never run the tracking JS and legitimately have no screen size) from real browser views that failed to report one, instead of lumping both into a single "unknown" bucket.
- Added date navigation (native date picker, Yesterday tab) with fixed-date sentinel fix.
- Added top-referrers 'Toon meer' toggle (shows 10, reveals up to 50).
- Added dashboard widget (online now, today's views/visitors with % vs yesterday), reusing overview card styling.
- Added review-nudge snooze (random 30-90 days, max 3x then permanent).
- Added device-class label (Phone/Tablet/Desktop) at screen resolution.
- Fixed 90-day chart overflow (gap + horizontal scroll).
- Dutch translations for new strings.
- New "Screen resolution" breakdown box: visitor screen sizes (in CSS pixels) are recorded with each view. The new database columns are added automatically on update.
- New "Avg. load time" stat box: page load times are measured in the visitor's browser via the Navigation Timing API and averaged per period.
- The "Online now" box gains a live "Currently viewed" list of the pages current visitors are on, refreshed on the same 20-second poll.
- Hourly visitors chart reworked: a fixed 24-hour axis with a dashed "yesterday" line for direct comparison against the previous day.
- Daily views/visitors bars now show their values on the chart, with density-based label sizing on the 30- and 90-day views.
- The Caching box now explains itself when a cache layer is detected but is serving (almost) none of the tracked page views.
- Much faster legacy view-count import: a Jetpack top-posts pre-pass covers the most-viewed posts in one request, admin-page batches run concurrently, and the WP-CLI command gains --offset/--limit flags.
- Dutch (nl_NL) translation updated for all new strings.
- Added wordpress.org listing screenshots (Statistics overview, Analysis, Bots & LLMs) and the corresponding == Screenshots == section. No functional or tracking changes.
- The GitHub-based update checker is removed entirely (updater.php and its vendored library) - releases now deploy straight to WordPress.org via a GitHub Action, and updates are handled by wordpress.org like any other hosted plugin.
- Fixed postbox drag-order and collapse/expand state not actually being saved: the admin pages were missing the nonce fields WordPress core's own postbox AJAX handlers look for, so those requests silently failed. Order and collapsed state now persist correctly per user.
- The site-specific "Dorpsapp" companion-app integration is now a generic,
opt-in connector-app mechanism (
turf_connector_app_route_patterns/turf_connector_app_labelfilters) - no behavior change unless you were using the oldturf_dorpsapp_route_patternsfilter, which is renamed. - Added a GitHub issues link (bug reports / feature suggestions) to the FAQ.
- The legacy view-count import (Jetpack Stats / the old entry-views plugin) is
now also available as a "Statistics > Import" admin page, alongside the
existing
wp turf-stats import-legacy-viewsWP-CLI command - same import, run in small AJAX batches with a progress bar instead of the command line.
- Fixed a WordPress.org submission error: the Plugin URI and Author URI headers pointed at the same URL. Author URI now points at the author's GitHub profile instead of the plugin repo.
- Cleared the remaining WordPress.org Plugin Check warnings: dropped the now-redundant load_plugin_textdomain() call (translations for wp.org-hosted plugins load automatically since WP 4.6) and annotated the opt-in REST debug logger. No functional or tracking changes.
- WordPress.org compliance release: readme.txt, uninstall.php with opt-in data removal, direct-access guards on all files, and the GitHub update checker is no longer part of the WordPress.org build (updates come from wordpress.org).
- Long lists are now collapsed before first paint (CSS), eliminating the load-time jump introduced in 1.16.0.
- Cache offload insight (served-from-cache % with layer detection).
- Landing pages report with per-landing bounce rate.
- Blocks with no data for the selected period are hidden entirely.
- All lists use one in-place Show more / Show less toggle; server-side pagination removed.
- Bilingual: English source strings with a bundled Dutch (nl_NL) translation.
- Raw (non-deduplicated) view counting, views per visitor, average visit duration, an hourly visitors chart for "Today", and full-URL outbound link tracking including the source page.
- See https://github.com/fbloemhof/turf-stats/releases for the full history.