

HitKeep settings page with connection cards, privacy defaults, tracker coverage, server-side integration controls, and snippet preview.
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.
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.
hk.js tracker.wp_redirect redirects through HitKeep’s server-side ingest API.https://www.example.net/hitkeep.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.comSelf-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.
The main HitKeep project is available on GitHub.