| 开发者 | adrianincode |
|---|---|
| 更新时间 | 2026年9月28日 02:15 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
navigator.sendBeacon to a REST endpoint on
your own site. Coordinates are stored resolution-independently, so a map recorded on a 4K
monitor lines up with one recorded on a laptop. Nothing is computed on the visitor's page
beyond collecting the events; rendering happens only when an administrator opens a map.
incode-heatmap folder to /wp-content/plugins/, or install the ZIP from
Plugins → Add New → Upload Plugin.No. Everything is stored in your WordPress database and never leaves your server.
The front-end tracker is a few KB, loads deferred after everything else and sends batched events. All aggregation and rendering happens in the administrator's browser, on demand, so regular visitors do not pay for it.
It is built to respect consent: it can require analytics consent (Complianz, Cookiebot, Consent Mode v2), honours Do-Not-Track, masks form input, stores no personal identifiers and deletes data after a retention period you choose. Compliance also depends on how you configure and disclose it on your own site.
Administrators and editors are excluded on purpose, so your own browsing does not pollute the data. Open the page in a private window to test it.
Excluded roles (administrators and editors by default) are never tracked, and you can list URL patterns to include or exclude from the settings screen.
As many days as you set under Retention (60 by default). A daily task deletes anything older on its own.
incode-heatmap).