Kitestring Analytics for Umami
| 开发者 |
nerveband
ancocodet |
|---|---|
| 更新时间 | 2026年10月25日 23:44 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
详情介绍:
An independent integration maintained by Ashraf Ali. This plugin is not affiliated with, endorsed by, or supported by Umami.
Kitestring Analytics for Umami adds your configured Umami tracking script to public WordPress pages. Tracking is disabled until you configure a script URL and Website ID and explicitly enable it.
Features:
- All Umami v3.4 tracker attributes, including performance, separate automatic pageview control, distinct IDs, and fetch credentials.
- Optional exclusion of signed-in administrators.
- Optional comment submit-button click events, without sending comment text.
- Dashboard pageviews, visitors, visits, bounces, and active visitors using an optional API connection.
- Self-hosted username/password authentication or Umami Cloud API keys.
- Migration from Integrate Umami settings.
- Settings remain saved when the plugin is deactivated.
- Opt-in recorder.js loading for heatmaps and session replay, with an optional custom recorder URL.
- Native custom events, event data, identity/session data, and revenue events through the official Umami tracker APIs.
- WordPress filters for page/consent gating, dynamic visitor IDs, future tracker attributes, and recorder exclusions.
安装:
- Upload the kitestring-analytics-for-umami directory to /wp-content/plugins/, or upload the plugin ZIP through Plugins > Add New.
- Activate Kitestring Analytics for Umami.
- Open Settings > Kitestring Analytics.
- Copy the Script URL and Website ID from your Umami website's tracking code.
- Enable analytics and save changes.
- Purge page caches, including LiteSpeed or CDN caches, after changing tracking configuration.
- Test as a signed-out visitor. Ignore Admins can intentionally suppress your own signed-in visits.
屏幕截图:
常见问题:
How do I upgrade from an earlier release?
Deactivate the previous plugin before installing and activating Kitestring Analytics for Umami. Your saved settings and API credentials are retained. Do not enable both plugins together.
Why is no tracking script present?
Check that the plugin is active, Enabled is checked, and Script URL and Website ID are filled in. Test signed out, then purge your page cache. Browser blockers, Do Not Track, domain restrictions, or disabled automatic tracking can also prevent collection after the script is present.
Does this work with the latest Umami?
Version 1.1.0 was smoke-tested against a real Umami v3.4.0 server: browser pageviews, dashboard statistics, recorded heatmap clicks/scrolls, replay chunks, performance data, a pseudonymous identity, and a revenue event. The dashboard accepts both v3 numeric statistics and the v2 value-object statistics format.
Will deactivation erase my settings?
No. Version 1.1.0 preserves settings on deactivation. Earlier versions erased settings on deactivation. An update cannot restore values that were already deleted.
What happened to the Cache option?
The obsolete data-cache tracker option was removed. It does not control the plugin's five-minute dashboard statistics cache.
更新日志:
1.1.4
- Renamed to Kitestring Analytics for Umami.
- Migrate saved settings from previous plugin names without overwriting current settings.
- Rename the plugin and clarify its independent authorship.
- Update the slug and text domain while retaining saved settings.
- Remove all remaining npm advisories by replacing wp-env with Docker Compose.
- Run dependency audits, PHP standards, and browser tests before release packaging.
- Keep the existing WP-CLI developer commands and browser regression coverage.
- Restrict the analytics dashboard widget to administrators who can manage plugin settings.
- Preserve spaces and special characters in self-hosted API passwords.
- Remove unused test tooling and update development dependencies.
- Simplify settings layout, field labels, privacy warnings, and save guidance.
- Replace hidden-checkbox accordions with native keyboard-accessible disclosure controls.
- Add a local flat icon and responsive, plugin-scoped admin styles.
- Preserve existing saved options and tracking behavior.
- Add opt-in heatmap/session replay recorder.js loading and a custom recorder URL.
- Add performance, auto-pageview, distinct-id, and fetch-credentials tracker settings.
- Add filters for tracking consent/page gating, dynamic and future data attributes, and recorder exclusions.
- Load tracker and recorder in deferred execution order.
- Preserve configuration on deactivation instead of deleting all analytics settings.
- Read current Umami v3 numeric statistics and the visitors active-count response correctly.
- Use the Umami Cloud API root at https://api.umami.is/v1.
- Include the current day in the dashboard's rolling 30-day statistics window.
- Preserve custom ports and application base paths for recorder, dashboard, and API URLs.
- Enqueue scripts through WordPress and declare the recorder's dependency on the tracker.
- Remove the obsolete data-cache tracker option and correct Do Not Track guidance.
- Replace PHP 8-only cloud detection with PHP 7.4-compatible hostname matching.
- Recover the previously deployed plugin code into its development repository and retain upstream attribution.
- Fork of Integrate Umami with independent branding.
- Add v3 tracker options, API integration, and a dashboard statistics widget.
- Add JavaScript-based comment submit-button event tracking.
- Trim copied tracking values and migrate legacy settings.