HitKeep Analytics
HitKeep Analytics connects WordPress to a self-hosted or cloud HitKeep instance. It injects the normal hk.js tracker from your HitKeep instance and keeps data flowing through the core HitKeep ingest pipeline.
The plugin does not add a separate analytics backend, database, queue, or third-party service. It only loads the tracker from the HitKeep instance you configure.
Privacy-first web analytics for WordPress
HitKeep is built for teams that want useful web analytics without adopting a heavy analytics stack. The WordPress plugin keeps setup simple: choose your HitKeep instance, save the settings, and the plugin loads the first-party tracker on public pages.
Logged-in WordPress users are skipped by default, so administrators and editors do not pollute public traffic reports. Browser Do Not Track is respected by default.
Features
- EU Cloud, US Cloud, and self-hosted HitKeep options.
- Logged-in WordPress users are skipped by default.
- Do Not Track is respected by default.
- Pageview tracking through HitKeep’s normal
hk.jstracker. - Built-in HitKeep automatic events for outbound links, file downloads, and form submissions.
- Optional Web Vitals reporting for LCP, INP, CLS, FCP, and TTFB.
- Optional redirect click events for supported short-link, affiliate, and
wp_redirectredirects through HitKeep’s server-side ingest API. - Settings link to the selected HitKeep instance’s API client page when redirect tracking needs a site-scoped token.
- Self-hosted URLs may include a path prefix, such as
https://www.example.net/hitkeep. - Clear opt-outs for sendBeacon delivery, route changes, outbound links, downloads, and forms.
- Shortcut to open the configured HitKeep instance from the settings page.
- Snippet preview so site owners can see which tracker attributes will be emitted.
What the plugin does not do
- It does not set analytics cookies.
- It does not create WordPress analytics tables.
- It does not require a tag manager.
- It does not load the tracker from a third-party CDN.
- It does not collect form field values, request bodies, link text, or URL query strings through automatic events.
- It does not print server-side ingest API tokens into public page source.
Third-party service connection
This plugin connects to HitKeep. Depending on your settings, it loads JavaScript from and sends analytics data to one of these HitKeep hosts:
https://cloud.hitkeep.euhttps://cloud.hitkeep.com- Your own self-hosted HitKeep URL
Self-hosted installations are controlled by your own HitKeep instance and infrastructure.
Optional redirect link tracking sends server-side outbound click events from WordPress to your configured HitKeep instance when a supported redirect resolves to an external host. The current adapters support BetterLinks, PrettyLinks, ThirstyAffiliates, and other redirects that use wp_redirect. This requires a site-scoped HitKeep API client token with site.manage_data for the WordPress domain. The settings page links to the selected HitKeep instance’s API client page and the API client guide. Redirect source, referrer, and target query strings are stripped before delivery.
Source code
The main HitKeep project is available on GitHub.
