HitKeep Use Cases
HitKeep is open-source privacy-first web analytics for teams that want useful reporting without turning analytics into another infrastructure project. Start with the use case closest to your problem, then choose managed cloud or self-hosting.
How to choose
Section titled “How to choose”Use the open-source sovereign web analytics guide when the adoption question is about ownership: source availability, deployment control, region choice, privacy defaults, assistant access, and exportability.
Use HitKeep Cloud when you want a production pilot quickly, do not want to manage SMTP, backups, updates, or TLS infrastructure, and can choose EU or US hosting at signup.
Use self-hosted HitKeep when your main requirement is direct control over the runtime, data directory, network policy, and backup process.
Use the read-only MCP server for web analytics page when the adoption question is the exact MCP tool surface, token boundary, Search Console analytics access, or AI crawler analytics access.
Use the migration overview when the adoption question is how to move history, replay logs, or run HitKeep beside another analytics product. Use the Google Search Console guide when the adoption question is whether organic query data can live in HitKeep without exposing it in public share links. Use the self-hosted GA4 alternative guide when the migration question is specifically about replacing Google Analytics 4 with infrastructure you control. Use the Google Analytics alternative for WordPress guide when the site owner wants to replace GA4 on WordPress through the HitKeep plugin. Use the comparison pages when you are replacing a specific analytics product and need a side-by-side evaluation before changing tags.
Use the cookieless event tracking guide when the adoption question is how to measure clicks, downloads, forms, custom events, and conversions without analytics cookies.
Use the QR campaigns guide when the adoption question is how to connect printed material, event signage, packaging, or other offline surfaces to tracked landing pages.
Use the AI visibility analytics guide when the adoption question is how to collect server-side AI crawler analytics and connect those fetches to later AI-referred traffic.
Use the AI visibility for SEO agencies guide when the adoption question is how to package that workflow as a client pilot.