Kantan Analytics – Cookieless Self-Hosted Analytics & Heatmaps
Cookieless, self-hosted WordPress analytics with heatmaps, scroll depth, user journeys and conversions. A private Google Analytics alternative.
Solid choice
Kantan Analytics is a solid plugin choice in 2026, with a few things worth checking first. It runs on 10+ sites, is rated 5/5 and was last updated 4 days ago, and scores 73/100 on our health check.
- Actively developed — last update 4 days ago
- Tested with the latest WordPress (7.1)
- Momentum — downloads up 82.5% vs the previous 30 days
- Small user base (10+ active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Kantan Analytics stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| cookieless analytics | #12 |
| google analytics alternative | #44 |
| heatmap | #34 |
| scroll depth | #39 |
| self-hosted analytics | #12 |
Version adoption
Share of active sites per release.
Rating breakdown
★★★★★★★★★★ 5 from 1 reviews
About Kantan Analytics
From the official readme · v2.35.1Description
Kantan Analytics is a self-hosted WordPress analytics plugin that tracks visitors, sessions, journeys, and conversions — without cookies, external services, or data ever leaving your server. A private, self-hosted Google Analytics alternative: every metric lives in your own database. You own it.
Kantan keeps every metric in your own database and answers the questions you actually have: which pages convert, where visitors come from, who keeps coming back, and what changed this week. The dashboard installs in a few minutes and runs in the WordPress admin sidebar you already use.
Privacy by architecture
- No cookies. Browser localStorage only — no consent banner required in most jurisdictions, no cross-site tracking possible.
- No IP storage. The visitor’s country is resolved from a bundled offline database at tracking time (region is optional — bring your own city database); the raw IP is used only for that lookup plus the exclusion/rate-limit checks, and is never written to disk.
- Nothing phoned home. Every metric stays in your WordPress database and Kantan never sends your data to us. One optional integration — the Attribution Webhook, off by default — can forward conversions to a webhook URL you choose (e.g. your own CRM); see the Privacy section.
- Configurable retention. Raw session detail purges on the schedule you set (default 90 days). Daily aggregates live in a local SQLite file forever.
- Bots and admins filtered. Logged-in admins, common bots, and IPs you specify are excluded before anything is recorded — your numbers reflect actual humans.
What it tracks
- Sessions, pageviews, bounce, duration — trended across any date range, with device, browser, OS, and screen-resolution breakdowns
- Traffic sources & UTM tracking — organic, direct, referral, social, paid; UTM parameters captured on first touch and attached to every conversion in the session
- Click, scroll, rage-click & dead-click heatmaps — drawn over a live preview of every page, per-device, no external script
- User journeys with named visitors — every visitor gets a persistent ID and a generated three-part name (e.g. “Roaming Copper Wren”) so long journeys are actually legible across return visits
- Page-to-page flow — see exactly which path your best visitors walk, and where the rest drop off
- Conversion tracking — phone, email, directions, bookings, plus auto-detection of form submissions from Contact Form 7, WPForms, Gravity Forms, Formidable, Ninja Forms, Forminator, and others
- 404 monitor — every missing page visitors hit, with the page that sent them, so you can fix the broken link or add a redirect
- Long-term aggregate storage — daily totals kept indefinitely in a local SQLite file even when raw rows are purged on schedule, so five-year trend lines don’t require holding five years of personal data
AI-readable analytics
Kantan ships with a downloadable AI agent that reads your data through the WordPress REST API using an application password you generate. Ask it questions in plain English — “Which conversions came from organic traffic last month?”, “Who are my five most engaged returning visitors?”, “Draft me a paragraph about this week’s biggest spike.” It reads; you approve. Nothing it sees leaves your terminal unless you ask.
Kantan is also an MCP server: with the MCP Adapter plugin active, one claude mcp add command connects Claude Code (or any MCP client) to 19 read-only, typed analytics tools at /wp-json/kantan/mcp — built on the WordPress Abilities API, no separate credential scheme, nothing writable by an agent.
Built for self-hosting
- Free forever, GPL v2
- No accounts, no signups, no SaaS dashboard
- Runs on any standard WordPress install (6.9+, PHP 7.0+)
- ~2 MB plugin, 5–50 MB/year of data depending on traffic
- Extensible sidebar tab system — companion plugins like Kantan SEO snap in alongside the analytics tabs
Privacy
Kantan Analytics is built to collect the minimum needed to give you useful visitor insight, and to keep all of it on your own server.
What is recorded: page views, click positions (as percentages, not pixels), scroll depth, in-session navigation paths, traffic source and referrer, UTM parameters, conversions (form submissions, phone/email/directions clicks), and approximate device, browser, operating system, and screen resolution parsed from the request.
What is not recorded: Kantan does not set cookies and does not store visitor IP addresses. The visitor’s country is resolved from a bundled offline database at the moment of the visit, after which the raw IP is discarded — no geolocation lookup ever leaves your server. Region-level data is optional and requires you to add your own city database. No data is ever transmitted to Kantan or the plugin author.
Country data: country resolution uses the free DB-IP Lite database (“IP Geolocation by DB-IP”, https://db-ip.com/), licensed under CC-BY-4.0.
Optional data sharing (off by default): The Attribution Webhook is the only feature that can send data off your server, and it is disabled until you turn it on. When you enable it and provide a destination URL, Kantan forwards each conversion event — with any UTM/campaign and passthrough parameters you’ve allow-listed — to that endpoint, which is typically your own CRM or marketing-automation tool. You choose whether to enable it and where the data goes; nothing is sent until you do.
Retention: detailed session records are deleted automatically after a configurable window (default 90 days). Beyond that, a local SQLite file keeps daily totals, a summary per random visitor ID (first and last visit, visit counts, first traffic source) and the conversions recorded against it.
Disclosure helper: Kantan registers suggested text with WordPress’ built-in Privacy Policy tool (Settings → Privacy), so you can add an accurate disclosure to your site’s policy in one click.
Support
Questions, bugs, or feature requests? Email hello@trykantan.com — or use the Support & Bug Reports card in the dashboard’s Settings tab, which pre-fills your plugin, WordPress, and PHP versions plus your site URL so we can help faster. We read every message.
Installation
- Upload the plugin folder to the
/wp-content/plugins/directory, or install it through the Plugins screen in WordPress. - Activate the plugin through the ‘Plugins’ menu in WordPress.
- The database tables are created automatically on activation.
- View your analytics at Analytics in the admin menu.
Frequently asked questions
Does this use cookies?
No. Kantan uses browser localStorage to recognise returning visitors, never cookies. No consent banner is required in most jurisdictions, and no cross-site tracking is possible.
Where is the data stored?
All data is stored in your WordPress database in wp_kantan_* tables, with daily aggregates in a local SQLite file under wp-content/uploads/kantan/. Nothing is sent to external servers.
How is traffic source detected?
The tracking script categorizes referrers automatically: Organic: Google, Bing, Yahoo, DuckDuckGo, Baidu Social: Facebook, Twitter, Instagram, LinkedIn, Pinterest, TikTok Referral: Other external sites Direct: No referrer or same domain UTM parameters override referrer-based detection when present, and they stay attached to the visitor through every page and conversion in the session.
Does this slow down my site?
No. The tracking script loads asynchronously after page content and uses sendBeacon for exit tracking. There are no blocking requests, no third-party domains, and no external CDNs. Performance impact is well under 10ms.
Is this GDPR / CCPA / ePrivacy compliant?
Kantan is designed for privacy-first compliance under modern privacy law: no cookies, no IP storage, no cross-site tracking, and — unless you switch on the optional Attribution Webhook — no data leaves your server. In most jurisdictions you do not need a consent banner to use it. We’re not lawyers — confirm with yours — but architecturally the tool is built for privacy-first compliance rather than retrofitting it.
Will this work with caching plugins (WP Rocket, W3 Total Cache, etc.)?
Yes. The tracking script is loaded via standard wp_enqueue_script and runs client-side, so cached pages still record visits correctly. The only thing to watch for is plugins that delay or defer JavaScript so aggressively that visitors leave before the script fires — exclude kantan-analytics/assets/tracking.js from any “delay JS until interaction” rule and you’ll be fine.
Can I import data from Google Analytics?
Not currently. Kantan starts tracking the moment you activate it, and historical GA data has a different structure that doesn’t map cleanly. If GA→Kantan import is something you need, drop us a note at https://trykantan.com.
What happens to my data if I deactivate the plugin?
Nothing — your data stays in the database. Deactivating just stops new tracking and hides the dashboard. If you uninstall (delete) the plugin, the tables remain unless you explicitly drop them; this is standard WordPress behavior and lets you reactivate without losing history.
How do I exclude my own visits, or specific staff IPs?
Logged-in admins are excluded by default. The Settings tab also lets you exclude specific IP addresses (one per line). Common bot user-agents are filtered automatically.
What’s the AI agent?
A downloadable .md file from the dashboard that turns any AI coding agent (Claude Code, Gemini CLI, and compatible tools) into a read-only analyst for your site. It uses a WordPress application password you generate, calls the REST API, and answers questions in plain English. It only reads — nothing it sees leaves your terminal unless you ask.
Does this work with WordPress multisite?
Yes — install at the network level or per-site. Each site gets its own tables and its own dashboard. There’s no aggregated network-wide view yet; that’s on the roadmap.
Changelog
Fixes the AI answer readiness scan on themes that use role="main" without a main tag. Run the scan again after you update.
2.35.1
- Fixed: on themes that mark the content with
role="main"and have no<main>tag, the AI answer readiness scan on the SEO tab read only the first few lines of each page. It missed the headings, questions and answers below them. The scan now reads the whole content area. Run the scan again to update your scores.
2.35.0
- New: SEO tab. It shows the visits from search engines, the conversions they made, and their estimated $ value for each landing page. You set the value of each conversion type on the tab.
- New: AI answer readiness scan on the SEO tab. It reads each published page and post the way an AI crawler does, gives a score out of 100, and lists the pages to improve first. It was part of Kantan SEO before.
- New: the SEO tab shows a sample of the Kantan SEO Keywords tab. The tab is not shown when Kantan SEO is active, and Kantan SEO uses the values and scan results from it.
2.34.0
- New: 404 Monitor tab. It lists the pages visitors asked for that do not exist, with the page that sent them. “Your own link” marks a broken link on your site, with a link to the page to fix. Bots and logged-in editors are not counted, and vulnerability scans (.php, .env and backup files) are counted but not listed. No IP address or user agent is stored.
- New: MCP tool
get-404sand REST routeGET /kantan/v1/404s. - New: a modal opened from another modal now shows on top of it as a stack, and closing it goes back to the one below.
- Fixed: a click on an email or phone link counted as two conversions when any conversion link was set in Settings. Earlier double counts stay in the data.
- Fixed: MCP clients rejected the results of
get-analytics-overview,get-traffic-sourcesandget-conversions, because counts were sent as text. They are now numbers.
2.33.1
- Faster: the tracker is now one minified file of about 4 KB (gzipped). Before, it was three files of about 17 KB. It loads with
defer. - Faster: the video tracker loads only on pages that have a video, including players that open later in a popup. It adds about 4 KB.
- Faster: a page in a background tab no longer sends a report every 30 seconds. It reports when it is hidden and again when the visitor comes back.
- Fixed: Realtime no longer shows a tab that is open in the background as a live visitor.
- Faster: the server looks up the visitor’s country once for each visit, not on every report.
- The readable source of the minified files is in
assets/tracking.jsandassets/js/.
2.33.0
- Fixed: Kantan now stores every time in UTC. Before, it used three clocks: the database server’s time zone for most data, UTC for clicks and date windows, and the WordPress time zone for page exits. On a server that is not set to UTC, date windows were off by hours and daily charts followed the server’s day.
- Changed: daily charts, the nightly archive and excluded date ranges now follow the time zone in Settings → General, including daylight-saving changes. If it still says UTC, set it to your city.
- Changed: times on the dashboard show in your site’s time zone. The REST API and the MCP server return UTC.
- Data from earlier versions is converted to UTC once after the update, in small batches.
2.32.0
- Fixed: Top Pages now counts page views. It used to count each visit once, on the last page the visitor opened, so the home page and other pages that visitors pass through showed too few views.
- Fixed: visit time now covers the whole visit. It used to count only the time on the last page.
- Fixed: a real visit is no longer removed as a bot when the browser does not send its exit report. The Instagram and Facebook in-app browsers often do not send it. The tracker now also reports at 5 seconds, and on
pagehide, which iOS Safari and in-app browsers send more reliably. - Fixed: each visit now keeps the page where it started. The landing pages for a referrer, the page named in the bounce-rate recommendation, and the page bounce rate in Kantan SEO now use that page, not the last one.
- The tracker no longer listens for
beforeunload, so Firefox can keep your pages in its back/forward cache. - After this update, Top Pages and visit times are higher than before. Kantan does not recalculate data from before the update.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Kantan Analytics alternatives
All cookieless analytics plugins →FAQ
Kantan Analytics: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 18, 2026
Is Kantan Analytics free?
Yes. Kantan Analytics is free to download and use from the official WordPress.org plugin directory.
Is Kantan Analytics safe to use in 2026?
Kantan Analytics is a solid plugin choice in 2026, with a few things worth checking first. It runs on 10+ sites, is rated 5/5 and was last updated 4 days ago, and scores 73/100 on our health check.
How many websites use Kantan Analytics?
Kantan Analytics is active on 10+ WordPress websites and has been downloaded 2,183 times since it launched in June 2026. It was downloaded 763 times in the last 30 days.
Does Kantan Analytics work with WordPress 7.1?
Yes. The developer has tested Kantan Analytics up to WordPress 7.1.3, the latest release. It requires WordPress 6.9 or newer.
What PHP version does Kantan Analytics need?
Kantan Analytics requires PHP 7.0 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Kantan Analytics last updated?
The latest version, 2.35.1, was released on October 14, 2026 (4 days ago).
Who makes Kantan Analytics?
Kantan Analytics is developed and maintained by Try Kantan.
What are the best alternatives to Kantan Analytics?
The most popular alternatives to Kantan Analytics are Burst Statistics (200K+ installs), ezStats Analytics (30+ installs) and Vireo Analytics (10+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card