Snorklee Analytics – Cookieless GDPR Web Analytics
| 开发者 | moovswell |
|---|---|
| 更新时间 | 2026年10月9日 13:38 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | MIT |
| 版权网址: | 版权信息 |
详情介绍:
- It installs the tracker on every public page, and keeps it there through theme updates.
- It counts AI robots server-side. GPTBot, ClaudeBot, PerplexityBot and their peers fetch your HTML without running JavaScript, so no JavaScript analytics can see them, Snorklee's own snippet included. The plugin recognises them on the server, from the user agent of the page request, and reports the visit.
- It lets you choose how the tracker is installed, with three modes, and says what each one costs.
- Standard. Script and measurements both come from snorklee.com. Full measurement, but blockers that filter on the domain cut everything: those visits are not counted.
- Script served by WordPress (recommended). WordPress serves the tracker from your own domain (
/js/flow.js); the measurements are sent by the visitor's browser. The script escapes blockers that filter on the filename, and you keep country, unique visitors and traffic sources. Blockers that filter on the domain still block the measurements. - Full relay (self-host). WordPress also passes the measurements through, so no blocker sees anything. The cost: Snorklee then only ever sees your server. No country, no region, and unique visitors and traffic sources stop being reliable. Snorklee shows no location and says why, rather than a false one.
- No cookie, nothing stored on or read from the visitor's device
- No persistent identifier: the visitor key changes every day
- No cross-site tracking
- No advertising data: campaign (UTM) parameters are not read
- Honours
Do Not Track, Global Privacy Control and a visitor opt-out (snorklee.optOut()) - The visitor's raw IP address is never stored
- The plugin creates no database table and stores no personal data on your WordPress server (in full-relay mode, measurements pass through without being logged)
安装:
- In wp-admin, go to Plugins › Add New, search for "Snorklee Analytics", then Install and Activate.
- If you do not have one yet, create a Snorklee account at https://snorklee.com and add your site.
- Open the Snorklee menu in wp-admin and enter your site domain (e.g.
yoursite.com, withoutwww.). The plugin suggests it from your site address. - Choose an install mode. Read what each one costs before choosing; "Script served by WordPress" is recommended.
- Save, then click "Test installation": the plugin loads your home page and checks that the tracker is there with the right domain.
屏幕截图:
常见问题:
Which domain do I enter?
The domain your site is published under, without www. and without https://. It is the data-site value of the snippet shown in Snorklee, under Settings › Installation.
Do I need a cookie banner?
Not for Snorklee. It sets no cookie and stores nothing on the visitor's device, so the ePrivacy consent requirement (article 5(3)) is not triggered. The documentation is in Snorklee, under Settings › Privacy. Your other tools (ads, embedded videos, chat) remain yours to check.
Does the plugin track admin pages?
No. The tracker is only added to public pages. wp-admin is excluded.
How does full-relay mode work?
The plugin adds WordPress rewrite rules that map /js/flow.js, /api/event and /api/ping to its own handlers. They fetch the tracker from snorklee.com, cache it for one hour (Transients API), and forward the measurements. For the visitor's browser, every request goes to your own domain.
The visitor's address is forwarded in X-Forwarded-For, but Snorklee does not use it to place the visitor: on a public endpoint without authentication, an address in a header is a claim, not an observation. So there is no country or region in this mode, and unique visitors and traffic sources become unreliable, since the visit key is derived from that same address. Choose "Script served by WordPress" if that matters more to you than the visits blocked by domain.
Will full-relay mode slow down my site?
Barely. The tracker file is cached for one hour. Each forwarded measurement adds an outbound request from your server to snorklee.com, but the browser sends it in the background (sendBeacon() or a keepalive request), without blocking the page.
What happens if snorklee.com is down?
When WordPress serves the tracker and cannot fetch it from snorklee.com, it serves an empty script so your page does not break. Measurements sent during the outage are lost: there is no offline queue.
Can I change mode later?
Yes, at any time. Pick another mode and save: the plugin refreshes its rewrite rules and the next page view uses the new mode. Nothing is migrated and nothing is lost.
Does it work with caching plugins (WP Rocket, W3 Total Cache…)?
Yes. The tracker is added through the standard WordPress script API (wp_enqueue_script) in the <head>, so caching plugins keep it like any other script. The tracker served by WordPress uses Cache-Control: public, max-age=3600.
How do I uninstall?
Deactivate and delete the plugin from Plugins. Deleting it removes the site domain, dashboard URL and AI-robot settings and the cached tracker. The plugin creates no database table.
更新日志:
- Fix: saving the settings no longer switches off the AI-robot report. The setting has no checkbox on the page, and WordPress hands an absent field to the plugin as empty: until 3.0.0 every "Save changes" turned the report off. It now keeps its value, and an installation where it was switched off this way gets it back once, on update.
- Uninstalling now also removes the install-mode setting.
- The settings page and readme now use the words of today's Snorklee: the snippet and its
data-sitevalue are under Settings › Installation, and the privacy documentation under Settings › Privacy. - Removed a promise that no longer exists: in full-relay mode Snorklee shows no location and says why; there is no "repair task".
- "Hosted in Paris" replaces "100% EU-sovereign".
- The installation test now says exactly what it checks (the tracker is on the home page with the right domain) instead of claiming that visitors are being counted or that ad-blocker bypass is active.
- French now uses « vous », like the rest of Snorklee.
- The External services section now lists every request, including the robot's IP address sent by the AI-robot report.
- Three install modes instead of a toggle, and each states its cost. The new "Script served by WordPress" mode serves the tracker from your domain while the measurements go straight from the visitor's browser: you escape blockers that filter on the filename and keep country, unique visitors and traffic sources. It is now the recommended mode.
- Correction of a false measurement claim. Earlier versions said that forwarding
X-Forwarded-Forlet Snorklee see the visitor's real IP for geolocation. It never did: Snorklee refuses to geolocate a declared address on a public endpoint, so sites in full-relay mode had all their traffic placed at their host's location. The settings page and the documentation now say what each mode really costs. - AI robots: the address sent is the one your server actually observed (the last hop of
X-Forwarded-For), no longer the first entry, which the caller writes and can forge. A private or unusable address is not sent at all. - Existing installs are migrated silently: self-host on becomes full relay, self-host off becomes standard.
- Single-page themes and headless front-ends (React, Vue, Next.js, Nuxt) are counted page by page: the tracker follows page changes made through the History API. Only the path is sent, never the query string or fragment.
- The description no longer promises features Snorklee has removed.
- AI robots: the robot's IP address is now sent in a dedicated header (
X-Snorklee-Crawler-IP). Behind a reverse proxy,X-Forwarded-Forcould be rewritten in transit and the address lost.
- Behavioural cards (scroll maps, attention zones, UX friction) were removed from Snorklee. The self-host proxy no longer maps
/api/zone; the rule is dropped automatically on update.
- The click heatmap was removed from Snorklee. The self-host proxy no longer maps
/api/click; the rule is dropped automatically on update.
- The installation test now recognises the tracker served from your own domain (
/js/flow.js). Tracking itself was unaffected, only the test verdict. Older versions: the full history is in the plugin's SVN repository on wordpress.org.