Hopcount Click Tracking
| 开发者 | aph5 |
|---|---|
| 更新时间 | 2026年9月15日 01:26 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Hourly click counts per link. That is the whole data model: no per-click rows, no IP addresses, no user agents, no referrers, no user IDs, no cookies.
- Which post each link appeared in, the destination URL and its host, and the link text (used as an automatic label).
- When a post renders, eligible outbound links get a short server-generated token attribute. Ordinary links to your own site (and any hosts you list as internal) are skipped. A same-site link that your site answers with an off-site redirect (a cloaked affiliate link) is treated as outbound and tracked under the redirect's destination.
- A small deferred script (about 700 bytes compressed) sends a beacon to a REST endpoint when a link is activated, including middle-click and keyboard activation.
- The endpoint resolves the token and increments the hourly counter.
- Report screen with date presets or a custom range, host filter, search by post title or destination, summary cards and CSV export.
- Labels screen to give any destination URL a friendly name.
- Dashboard widget with the top links for today, yesterday, 7, 30 or 90 days.
- Status screen showing schema, cron and rate-limiter health.
- Bounded retention: hourly rows older than the configured window (default 24 months) are pruned daily.
- Layered abuse protection: the endpoint is POST-only and token-validated, an optional built-in per-IP limiter runs on your persistent object cache, and the documentation recommends a CDN or WAF rate-limiting rule.
- Uninstall keeps your data unless you opt in to deletion.
- Two filters let you grant report and label access to editors or authors.
安装:
- Upload the
hopcount-click-trackingfolder to/wp-content/plugins/, or install it from the Plugins screen. - Activate the plugin. The tables and the daily retention task are created on activation.
- Review Click Tracking > Settings (master switch, excluded roles, internal hosts, retention, rate limiting).
- If you run a page cache, purge it once so existing posts are annotated on their next render.
屏幕截图:
常见问题:
Does it work with caching plugins and CDNs?
Yes, by design. The tracking token is part of the cached HTML and the click beacon goes to a REST endpoint that bypasses page caches. WP Rocket, WP Super Cache, W3 Total Cache, Cloudflare APO and similar all work without special configuration.
Does it store IP addresses or any personal data?
No. Only hourly aggregate counts per link are stored. The optional rate limiter keeps a short-lived per-IP counter in your object cache (a few seconds to a minute) and never writes it to the database.
Is it GDPR friendly?
There are no cookies, no personal data and no per-visitor records, so no consent banner is needed for this plugin. Always check with your own adviser for your specific situation.
Does it change my links or redirect visitors?
No. Links keep their original href. The plugin only adds a data attribute at render time.
What counts as an outbound link?
Any link in post or page content whose host is not your site (including its www and non-www forms) and not in your internal-hosts list. Links elsewhere in the theme (menus, widgets, footers) are not tracked.
I use cloaked links like /go/product or /recommends/product. Are they counted?
Yes, since 1.2.0. The plugin sends a small signed request for each same-site link to your own server, with redirects disabled, and reads the answer. If the answer is a redirect to another host, the link is tracked under that destination, exactly like a link written out in full, so the host filter, labels and grouping all work. If the answer is a normal page, a 404 or an on-site redirect, the link stays untracked. Redirects made by Redirection, Pretty Links, ThirstyAffiliates, your web server or your host all look the same to this check. Answers are kept in a small table and re-checked about once a week by WP-Cron. It is best-effort: redirects that depend on cookies, geography or the request method are not seen, and redirect rules applied at a CDN in front of your origin are not visible to it.
Will the redirect check slow my site down or overload the server?
No. Work is bounded by content, not by traffic: one row per distinct same-site link, checked about once a week. An uncached page view checks at most three never-seen links with a three-second budget; everything else is done by cron in small batches. Any transport error pauses all checks for an hour, there is a daily cap of 10,000 requests, and the Status screen shows the state. Fully cached page views never touch it. To turn the feature off entirely, define the constant OCTK_DISABLE_RESOLVE as true or return false from the octk_resolve_enabled filter; behaviour then matches 1.1.x.
Which users are tracked?
Visitors and logged-in users whose role is not in the excluded-roles list (administrators and editors by default).
Can editors or authors see the report?
Yes, by adding two filters in a small site plugin or your theme's functions.php:
add_filter( 'octk_report_capability', fn() => 'edit_published_posts' );
add_filter( 'octk_label_capability', fn() => 'edit_published_posts' );
Does it support multisite?
Not yet. Activation on a multisite network is refused.
What happens on uninstall?
Data is kept by default. Tick the option on the Settings screen if you want the tables and settings removed when the plugin is deleted.
更新日志:
- Cloaked links on your own site (for example /go/product or /recommends/product created by Redirection, Pretty Links, ThirstyAffiliates or a server rule) are now tracked under their real destination. The plugin asks your own server where the link goes, with a signed request that never renders a page, and records the answer in two new tables (schema version 3). Answers are refreshed weekly by WP-Cron and are bounded by a per-render budget, a per-run budget, a daily cap and a circuit breaker.
- Status screen: new rows for the resolution state, counts, probes today, the probe route and the cron, plus a "Clear resolution cache" button.
- New filters
octk_resolve_enabled,octk_pre_resolve_same_site,octk_resolve_ttl,octk_resolve_daily_cap,octk_resolve_probe_origin,octk_resolve_probe_sslverify; new actionoctk_resolution_changed; new constantOCTK_DISABLE_RESOLVE. - Frontend output changes on pages that contain cloaked links, so purge your page cache after updating.
- Every database query now passes table names through wpdb::prepare() (%i placeholders) and the report sort clause is chosen from a fixed list of complete ORDER BY strings. No behaviour change; addresses the WordPress.org plugin review feedback.
- Renamed to Hopcount Click Tracking (slug and text domain
hopcount-click-tracking). Code prefix, hooks, tables, options and the REST route are unchanged, so existing data and site code carry over.
- Legacy data adoption now verifies every copied option and user preference before removing the source, checks that the old cron hook was cleared, and records the schema version only after the migrated tables pass the structure probe.
- Plugin URI points at the public GitHub repository.
- First WordPress.org release. Pre-1.0 installs are migrated automatically on first load.
- Breaking: all hooks, the REST route and the link attribute now use the
octkprefix. - All strings are translatable.
- Admin styles and scripts use the WordPress enqueue API.
- Dashboard widget lists the top 10 links.
- De-branded for general use; CSV export filename includes the date range; documentation added.
- Report search rework, per-post link pinning, security hardening.
- Initial private releases: token annotation, beacon listener, REST endpoint, hourly aggregates, Report, Labels, Settings and Status screens, dashboard widget, retention, rate limiter, CSV export.