Kantan Analytics -- WordPress 插件

开发者	inglewood
更新时间	2026年10月30日 04:00
PHP版本:	7.0 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

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

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.

2.36.2

Fixed: the AEO scan on the SEO tab now reads all the JSON-LD on a page, including @graph blocks and @type lists, so BlogPosting and other Article types count as Article. The entity check reads the first real paragraph after the title instead of a byline, and also accepts the names in your Organization schema. The answer length check counts characters, not bytes.
New: GET /kantan/v1/crawlers and the MCP tool get-ai-crawlers take crawler, type, page, since and until filters. include_hits returns the individual hits, newest first, with limit and offset. Now you can see which pages ChatGPT fetched before a lead arrived.
New: when your own IP address is excluded from tracking, the Kantan dashboard tells you. Tracking requests from an excluded address now answer "recorded": false with the reason, instead of a plain success.

2.36.1

Fixed: a bot that runs a real browser with a square screen (for example 1366x1366) counted as real visits. It reads one page for about 5 seconds, so the bot filter missed it, and the Devices report showed it as Laptop. Square screens of 1024 or more now count as bots, and the Devices report shows them as Unknown. No laptop, monitor or tablet has a square screen at that size.
Fixed: the bot filter now also applies to the Realtime view, to the session list of each visitor on the Journeys tab, and to the highest bounce page recommendation.
Fixed: the daily archive counted bot pageviews in its pageview totals. Days archived after this update leave them out.

2.36.0

New: a "New vs Returning Visits" card on the Overview tab. It compares first visits with return visits: visits and share, bounce rate, average duration and conversion rate, and shows how many new visitors came in the period.
New: a New / Returning filter on the Journeys tab. It applies to the visitor profiles, the page transitions and the entry and exit pages. Each session in a profile now shows "First visit" or "Return visit".
New: the REST API and the MCP tools accept visit=new or visit=returning on journeys and visitor profiles, and the overview returns the new fields.
Fixed: a visitor who came back after their old visits were deleted by the data retention setting (90 days by default) counted as new. With a 90-day period, almost every visitor counted as new. Kantan now also uses the time saved in the visitor ID.
Fixed: "First seen" on a visitor profile showed the first visit in the selected period. It now shows the first visit ever.

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-404s and REST route GET /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-sources and get-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.js and assets/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.

2.31.3

Changed: the request for a WordPress.org review is now a standard notice at the top of the Kantan screen, not a card on the Settings tab. It appears once your site has tracked 100 visitors over at least 14 days (it was 500), only on Kantan's own screen, and only to administrators. Close it once and it does not come back.
Tested with WordPress 7.1.

2.31.2

Security: visitor IDs sent by the tracker are now checked, so a crafted ID can no longer change a request made from your dashboard. Bad IDs that are already stored are removed on upgrade.
Security: every tracking endpoint (visits, clicks, campaign tags and video) now has a flood limit, set well above real traffic. The limits use fixed time windows, so a busy shared network such as an office is not blocked by mistake.
Security: behind a proxy, the visitor's IP now comes from the entry that the proxy added. A visitor can no longer choose an IP to get around IP exclusions or the flood limits.
Security: the attribution webhook only sends to public web addresses.
Security: the Heatmaps preview only loads public pages of your site.
The downloadable AI agent now asks you before it installs an update, and it treats tracked text (page titles, referrers, visitor names) as data, never as instructions. Agents that are already installed get this version at their next update check.
Read-only dashboard viewers can see the Settings tab again, so the AI agent download works for them. Owner-only details stay hidden: excluded IPs, notes on excluded date ranges, CRM passthrough IDs and version details.
Privacy: AI-crawler hits no longer store IP addresses, and the ones already stored are removed. The suggested privacy-policy text now lists everything that is kept after the retention window.
The analytics database folder is now protected on Apache 2.4 as well as Apache 2.2.
One-time data updates no longer run during visitor requests, and the page-address cleanup now always finishes.
Very large limit and days values on the REST API are reduced to safe maximums, and only administrators and dashboard viewers can connect to the MCP server.

2.31.1

Security: conversion tracking now filters bots and caps how many conversions one visitor or one session can record. This stops a script from flooding your conversion data — and, if you use the attribution webhook, your CRM.
Security: the Settings tab is now shown to administrators only. Read-only dashboard viewers no longer see excluded IP addresses or conversion links.

2.31.0

New: once the plugin has tracked 500 visitors on your site, the Settings tab asks whether you would like to leave a review on WordPress.org. It appears on that one tab only — never as an admin notice, never on the dashboard, and never in your way. Dismiss it and it is gone permanently. A support link sits beside it, so if something is wrong there is somewhere better to go than the review form.

2.30.1

Listing only: clearer plugin title and description on WordPress.org, and directory tags that match what the plugin actually does best — cookieless tracking, self-hosted storage, heatmaps and scroll depth. No functional changes; nothing in your install behaves differently.

2.30.0

New: Heatmaps tab. Click maps drawn over a live preview of the actual page — pick any page with click data, switch between desktop, tablet and mobile, and see what gets clicked, element by element. Clicks are anchored to the elements themselves, so a button tapped on a phone lights up in the right place on the desktop preview too.
New: rage-click detection. Rapid repeated clicks in one spot — the classic "why isn't this working" signal — get their own map layer, so you can find broken links and unresponsive elements before visitors give up.
New: dead-click detection. Clicks on things that aren't interactive get flagged and mapped, and the recommendations engine now names the exact element and page visitors keep trying to click.
New: scroll maps. See how far down each page visitors actually get, as a color overlay on the page itself with depth lines and the average fold marked.
New: the agent can see friction now — rage-click and dead-click totals (and the worst offenders) are included in the interactions data over REST and MCP.
Improved: clicks recorded before this update (which lack element and device detail) are re-anchored onto the element with the same label where possible, their device is estimated from the visitor's screen size so they still appear under the device filters, and the Heatmaps tab shows a temporary notice explaining why older click maps can look offset. The notice retires by itself after 90 days.
Improved: click batches are stored in one query instead of one per click, and clicks from mobile visitors are no longer undercounted when a tab closes without warning.

2.29.0

Fixed: bot filtering now applies to every metric. It was only reaching your visit count, bounce rate and duration — device breakdown, visitor counts, top pages, journeys and campaigns were all still counting bots. That's why the same 30 days could report 29 visits and 78 device sessions. All figures now describe the same set of visitors.
Fixed: bot detection now catches two kinds it used to miss — sessions that view several pages while accruing no time at all (these never bounce, so the old rule never saw them, yet they dominate the journey and page-flow reports), and traffic reporting an 800x600 viewport, which is the headless-browser default rather than a real screen.
Fixed: 800x600 traffic is no longer counted as a tablet. If your tablet segment showed unusually high bounce and short visits, this was why.
New: exclude specific date ranges from every metric, under Settings. For the days no rule can sensibly catch — a load test, a migration crawl, a scraper that browsed like a reader. One such day can outweigh months of real traffic in your baselines.
New: email, paid and campaign traffic sources. A visit tagged utm_medium=email was previously reported as direct, because email clicks arrive with no referrer. Any visit carrying a utm_medium is now attributed to it, for the whole visit rather than just the landing page.
Fixed: pages no longer split across multiple rows because of email and ad tracking parameters. Mautic's ct, HubSpot's _hsenc/_hsmi and newer ad click ids are now stripped, and cleanup also runs on the server so it works even when a cached script misses it. Existing split rows are merged once on upgrade.
Fixed: conversions now say when no rules are configured, instead of reporting zero. Zero conversions because nothing is being watched looked identical to zero because nobody converted. Kantan also suggests rules based on buttons your visitors already click and the paths they already take.
Fixed: the UTM report counted rows and labelled them sessions, and skipped bot filtering entirely, so it disagreed with the traffic report. Both now count the same way. For "how much traffic came from this channel", the traffic report remains the authoritative one.

2.28.2

Fixed: conversion links on your own domain now work. A rule like /checkout (or a full URL on your own site) matches by path prefix; previously a same-site rule either never matched absolute link URLs or — if it contained your own domain name — counted every internal link click as a conversion. Outbound-domain rules are unchanged.

2.28.1

New: an MCP setup card in the dashboard's AI Agent section — live status (detects your WordPress version and the MCP Adapter plugin), the exact one-command Claude Code connection for your site, and install guidance when the adapter is missing. Fully translated (Deutsch, Español, Français, Italiano, 日本語).
Fixed: the downloadable agent pointed to a wordpress.org listing for the MCP Adapter that doesn't exist — it now links the official GitHub release. Agent template is v2.0.1; installed agents update themselves automatically.

2.28.0

New: MCP server — connect Claude Code (or any MCP client) to your analytics with one command. On WordPress 6.9+ with the MCP Adapter plugin, Kantan exposes 18 read-only, typed tools (visits, pages, traffic sources, conversions, visitors, journeys, clicks & scroll, videos, AI crawlers, Business Profile) at /wp-json/kantan/mcp, built on the WordPress Abilities API. Kantan SEO's tools join the same server automatically.
New: the downloadable AI agent (v2.0.0) is now MCP-first with automatic REST fallback — installed agents update themselves within a week.
The MCP surface is read-only by design: no settings, no writes, and nothing that spends money can be reached by an agent through it.
Requires WordPress 6.9 or newer (the Abilities API). Existing installs on older WordPress keep working on 2.27.x.

2.27.1

Fix: after updating to 2.27.0, the Realtime view could briefly show a burst of long-running "visitors" that were actually old sessions. The one-time IP purge was nudging each cleaned row's last-activity time to the moment of the update, so historical sessions looked active for a few minutes. Corrected — no analytics data was affected (visit counts, duration, bounce and sources were never touched) and the view now stays accurate.

2.27.0

Security: the visit-tracking endpoint could be forged. Added per-IP flood limiting on new sessions and a read-time filter that keeps zero-engagement bot sessions (sub-two-second bounces) out of your visit counts, bounce rate, duration and sources — nothing is deleted, and it cleans up existing junk automatically. Toggle in Settings.
Security: client IPs are now resolved only from trusted reverse proxies (Cloudflare, and local/private proxies), so a forged X-Forwarded-For can no longer spoof a visitor's IP or bypass IP exclusion. IP exclusion now supports IPv6.
Privacy: the tracker no longer stores the visitor IP at all — it is used only for the exclusion and rate-limit checks, then discarded, so "no IP stored" is now true end to end. Any IPs written by earlier versions are purged automatically on update.
New: visitor profiles expose the user agent so you can identify the source of suspicious traffic.
New: visitor countries — a "Top Countries" breakdown resolved from a bundled offline database (no external calls, no IP stored). Region is optional via a bring-your-own city database. Country data by DB-IP (CC-BY).

2.26.0

New: "View all" on Top Referrers — the dashboard block lists the top 10, and this opens every referrer in the period, with a filter box to find one quickly. Each row still opens the referrer detail view.
New: /referrers REST endpoint returns the full referrer list with a total count.
i18n: new strings translated for German, French, Spanish, Italian, and Japanese.

2.25.0

New: "Ask the agent" prompts on the Video and AI Crawlers tabs — one click surfaces copy-paste, data-specific questions for your Claude Code / Gemini CLI agent.
New: /crawlers REST endpoint exposes AI-crawler activity to the agent, so it can report which AI bots hit your site, how often, and the split between live fetches and training crawls.
Improved: the downloadable Analytics agent (v1.3.0) now understands video engagement and AI-crawler data — new /videos and /crawlers endpoints, workflows, and starter prompts.
i18n: new strings translated for German, French, Spanish, Italian, and Japanese.

2.24.0

New: Video analytics — engagement tracking for the YouTube, Vimeo, and self-hosted videos your pages already embed. No setup: embeds are detected automatically (including lazy-loaded and popup embeds).
New: Video dashboard tab with plays, play rate, average watch time, and completion rate, per video.
New: click any video for a detail view — plays by day, the pages it was watched on, and autoplay share.
New: video settings — master switch, per-provider toggles, privacy-enhanced youtube-nocookie.com rewrite (on by default), and muted-autoplay exclusion so background hero loops don't inflate play rate.
New: all video features fully translated in German, French, Spanish, Italian, and Japanese.
Privacy: provider player scripts load only on pages that actually embed them; engagement is stored as anonymous aggregates in your own database. Privacy-policy suggestion text updated.

2.23.1

Improved: dashboard dates now follow your site language (localized month names and AM/PM) instead of always showing English.
New: the AI Crawlers tab is now fully translated in German, French, Spanish, Italian, and Japanese.
Fixed: the Conversions and AI Crawlers tabs now group correctly under the localized "Analytics" heading in non-English languages.

2.23.0

New: AI Crawlers tab — see which AI crawlers (GPTBot, ClaudeBot, PerplexityBot, CCBot, and more) are fetching your content, how often, and which pages. Tracked server-side (crawlers don't run JavaScript) and kept completely separate from your human visitor stats, with live-fetch vs training-crawl called out.

2.22.0

New: analytics data is now tagged per property — groundwork for upcoming multi-site aggregation (Kantan Hub). No change to existing single-site dashboards; your tracking works exactly as before.

2.21.2

Change: all updates now come from WordPress.org. The self-hosted updater has been removed; if you installed from trykantan.com, this update moves you across and you will keep receiving updates as normal.

2.21.1

Improved: more of the dashboard now localizes — visitor and click detail subtitles, relative timestamps ("5 min ago"), scroll-depth tooltips, and site-scan/webhook status messages that were previously always shown in English.

2.21.0

New: bundled translations for the admin dashboard — German, French, Spanish, Italian, and Japanese. Set your site or user language and the dashboard UI follows. (Chart labels and a few dynamic strings remain English for now and will be localized in a follow-up.)

2.20.1

Security: the excluded-IPs and data-retention settings endpoints now require administrator access even for read requests.
Change: the admin dashboard's tooltip styles are now enqueued as a stylesheet instead of inlined.

2.20.0

Hardening: every visitor-tracking, UTM, conversion, and form input is now unslashed and sanitized at the point it is read, and the values forwarded to integration hooks are sanitized arrays rather than the raw request.
Security: diagnostics and configuration endpoints (status, conversion links, attribution webhook config) now require administrator access even for read requests.
Change: all admin and front-end JavaScript is enqueued through WordPress — no inline script tags remain.
Change: bundled Chart.js updated to 4.5.1.

2.19.0

Hardening: comprehensive output escaping across the admin dashboard, timezone-safe date handling, and URL parsing through WordPress core wrappers — aligning the plugin with the official WordPress.org plugin coding standards.
Change: minimum supported WordPress raised to 5.6.
Docs: clarified the privacy documentation to disclose the optional Attribution Webhook, which sends conversion data to a CRM endpoint you configure — and only when you enable it.

2.18.0

New: Business Profile — a canonical, editable record of your business facts (hours, offerings, address/phone, brand voice, claims to make or avoid) under Settings → Business Profile. The downloadable AI agents now read it as ground truth before writing or rewriting content, so generated copy uses real facts and your voice instead of guessing. Your agent can even draft it from your site ("Draft my business profile"), and it's the same source of truth for both the Analytics and SEO agents.

2.17.0

New: Attribution Webhook — send every conversion to your email/CRM platform (HubSpot, GoHighLevel, Salesforce, Zapier, Make, and more) with its first-party campaign + journey attribution, keyed by an anonymous visitor id. HMAC-signed; no personal data leaves your site. Set it up under Settings → Attribution Webhook / CRM, with a one-click "Send test".
New: passthrough parameter capture — Kantan now captures ad-click and CRM contact ids from inbound links (gclid, fbclid, msclkid, contact_id, mkt_tok and ~45 more) and includes them in the webhook, so your CRM can join the conversion to the right contact. The captured params are stripped from stored URLs.

2.16.1

Improved: the downloadable AI agent now officially documents Gemini CLI alongside Claude Code (it's the same Markdown format — drop it in ~/.claude/agents/ or ~/.gemini/agents/). The agent self-updates to this broadened version automatically.
Improved: "Ask the agent" prompts now copy with the agent name prefixed, so the pasted prompt delegates to the right Kantan agent. Wording across the agent download is now tool-neutral.
New: a "What about Codex?" explainer on the agent download covering why OpenAI Codex isn't officially supported yet (and how to use Kantan with it today).

2.16.0

New: Scroll Depth by Page — the Interactions tab now breaks scroll depth down per page (with a visual bar), so you can see which pages get read versus abandoned instead of just a site-wide average.
New: click a visitor's name on the Realtime tab (or in Visitor Profiles) to open their full visit history — every session, the pages they walked, durations, and conversions.

2.15.0

New: Interactions drill-downs — click any Click Region to see exactly which elements were clicked there and on which pages, and click any row in Top Clicked Elements for its per-page breakdown.
Improved: click tracking now records the actual link/button clicked (not the inner span or icon) with a clean, accessible-name-first label, and no longer captures whole-page text from stray clicks. Top Clicked Elements merges the same control across pages and filters out container/no-text noise — so the report finally reflects what visitors actually click.

2.14.1

New: Top Referrers detail modal — click any referrer on the Overview dashboard to see its sessions, visitors, daily trend, landing pages, the exact referring URLs, and recent visitors.
New: the Claude Code agent now keeps itself up to date — it checks for a newer version about once a week and refreshes in place, with no re-download and without ever rotating your API key. Added an "Update agent file" button and clearer "install once, use on every site" guidance.

2.14.0

New: "Ask the agent" — a sparkle icon on dashboard data blocks (referrers, traffic sources, pages, journeys, interactions, devices, conversions) opens a modal of copy-paste, data-specific prompts for the Claude agent.
New: AI-assistant referral attribution — visits are identified from utm_source as well as the referrer (catching empty-referrer ChatGPT/Perplexity/Claude links) and split per assistant; the Overview AI card shows the per-assistant breakdown.
Fixed: Overview KPI cards lay out cleanly as 3-up / 2-up on laptop screens.

2.13.1

New: an "AI Assistants" KPI card with sparkline on the Overview dashboard — shows visits referred by AI assistants and their share of total traffic at a glance.

2.13.0

New: AI assistants (ChatGPT, Perplexity, Claude, Gemini, Copilot and more) are now a first-class traffic source. Visits referred by them are tracked and shown as their own "AI Assistants" category across Traffic Sources, sessions, the realtime tab, and conversions. Existing AI-referred visits are reclassified automatically on upgrade.
New: the Claude Code agent gained an "AI Assistant Referral Traffic" workflow and an "Am I getting AI traffic yet?" starter prompt.

2.12.1

New: a "Support & Bug Reports" card in Settings — a one-click email link that pre-fills your plugin, WordPress, and PHP versions plus your site URL, so reports arrive with the diagnostics we need to help. Settings and Support links now also appear in the WordPress plugins list.

2.12.0

Fixed: the agent download dialog now caps its height and scrolls on short/laptop screens instead of overflowing off-screen.
New: starter prompts in the Claude Code agent download — copy-to-clipboard example prompts (30-day summary, best/worst content, traffic-source ROI, visitor journeys) appear in the credentials modal and are written into the generated agent .md.

2.11.5

Fixed: clicking a page row now opens the page-detail modal on every tab. The click handler was previously only present on the Overview tab, so page rows on Pages, Journeys, and the SEO tabs showed a hover state but did nothing when clicked.
Fixed: the "Visits Over Time" chart on the Overview tab could render blank — the canvas had no sized container, so Chart.js collapsed it to zero height. It now renders in a fixed-height container.
Fixed: IP exclusion and visitor IP logging now resolve the real client address through reverse-proxy/CDN headers (Cloudflare, nginx, load balancers) instead of always using the proxy's own address. On proxied sites the "Your current IP" box previously showed a private hop (e.g. 127.0.0.1 or 192.168.x.x), and excluding it had no effect. When only a local/private address is available, the box now flags it and links to an external IP lookup.

2.11.4

New: optional read-only dashboard access. A user granted the kantan_view_dashboard capability can view the dashboard and its data without manage_options — every write, scan, and sync still requires manage_options. The dashboard menu capability is filterable via kantan_dashboard_capability. Inert on normal sites; powers a public read-only demo.

2.11.3

Security/clarity: the Claude Code agent download now states plainly that the generated Application Password grants the full API access of your account (not read-only), with guidance to keep the file out of version control and how to revoke the password under Users → Profile → Application Passwords.
Added: an Update URI header so the "Enable auto-updates" toggle appears for Kantan Analytics in the Plugins list. (The WordPress.org build omits this header so wp.org continues to own updates there.)

2.11.1

Removed: Conversion Backfill tool in Settings — the underlying hostname-matching bug it patched was fixed back in 2.9.8, so the catch-up tool is no longer needed. The REST endpoint, dashboard UI, and _backfill conversion-type display shim have all been removed.

2.11.0

New: Conversions tab — see your conversions by type and by traffic source, with a recent-conversion log, right in the dashboard. Surfaces the conversion data Kantan already tracks via Settings → Conversion Links.
Dashboard assets (Tailwind CSS and Chart.js) are now bundled with the plugin instead of loaded from a CDN — the admin dashboard makes no third-party requests and works fully offline.
New: Kantan contributes suggested text to WordPress' built-in Privacy Policy generator (Settings → Privacy), reflecting your configured data-retention window.

2.10.0

New: Realtime tab — shows visitors active in the last 5 minutes with their current page, traffic source, session age, and "last seen" age. Auto-refreshes every 30 seconds with a visible countdown and a manual "Refresh now" button. Pauses polling when the browser tab is hidden.
New: Live visitor count badge next to the "Realtime" item in the dashboard nav. Visible from every tab — the same 30s poll that drives the Realtime tab also keeps the badge current, with a pulsing green dot when at least one visitor is active.
New: REST endpoint GET /kantan/v1/realtime?window=5 — returns { count, window_minutes, visitors, timestamp }. Each visitor row includes the most recent pageview (current page), generated display name, traffic source, session age, and seconds since last activity.

2.9.9

New: UTM parameters now surface on the Journeys tab alongside each named visitor's session timeline — see campaign, source, and medium for pre-conversion visits (previously only visible aggregated on the UTM tab). REST /visitors and /journeys endpoints also expose the new fields, so the Claude Code agent and recommendations engine can attribute behavior to campaigns.

2.9.8

Fix: conversion link matching corrected — hostname was being searched inside the full URL string (always -1); now checks href.startsWith(rule.domain) OR rule.domain contains hostname. Affected all conversion link click tracking since the feature launched.
New: Conversion Backfill tool added to Settings. Scans historical click data and creates approximate conversion records for sessions likely missed by the bug. Matches anchor text against each rule's label; backfilled records carry a _backfill type suffix. Idempotent — safe to run multiple times.

2.9.7

Author renamed from "Kinda Useful Plugins" to "Try Kantan" across plugin header, readme, and updater comment.
readme description and FAQ rewritten — full feature pitch with subsection structure; FAQ expanded from 4 to 10 items (caching, GDPR/CCPA, GA import, deactivation, multisite, agent, etc.).

2.9.6

Fix: conversions endpoint now returns correct visitor_id for pre-2.9.4 records; query uses COALESCE(c.visitor_id, a.visitor_id) to recover attribution from the joined session record when the conversion row has a null visitor_id.
Fix: version constant bumped to match header (was stuck at 2.9.4).

2.9.5

Sidebar nav groups now accordion — clicking a group label collapses or expands it. The active group always starts expanded; inactive groups start collapsed. Keeps the nav usable on laptops when many SEO sub-tabs are registered.

2.9.4

Persistent visitor attribution for conversions: visitor_id column added to wp_kantan_conversions so attribution survives beyond the 90-day raw-data retention window.
Form integrations now inject kantan_visitor_id alongside kantan_session_id on all detected forms (CF7, WPForms, Gravity, Formidable, Ninja, Elementor Pro, Fluent, Forminator).
Schema migration runs automatically on update — no manual action required.

2.9.3

Update channel migrated to trykantan.com. Plugin URIs, SEO upgrade link, and auto-updater endpoint now point to the new domain.

2.9.0

New: Split test tracking integration — pageviews can now record test_id and variant_id from a companion split-testing plugin.
New: kantan_pageview_tracked action hook fired after each pageview insert.
Database migration to add test_id and variant_id columns to the pageviews table.

2.8.0

New: Clickable page URLs throughout dashboard — opens SEO page detail modal or upsell.
New: Sparkline mini-charts on Overview stat cards.
Surface recommendations engine on Overview, Interactions, and Journeys tabs.

2.7.0

New: IP address exclusion for analytics filtering.
Rebuilt Journeys tab with visitor profiles and generated names.

2.6.0

New: Admin exclusion and bot filtering.
New: Interactions endpoint for click heatmap and scroll depth data.
New: Device breakdown endpoint and queries.
Switched dashboard to left sidebar nav with grouped tabs.

2.0.0

New: Click tracking, scroll depth tracking, and user journey analysis.
New: Entry/exit page tracking and top-clicked-elements report.
New: Automatic daily cleanup with configurable retention.

1.0.0

Initial release: core visitor tracking and admin dashboard.

Kantan Analytics – Cookieless Self-Hosted Analytics & Heatmaps

标签

下载

详情介绍:

安装:

屏幕截图:

升级注意事项:

常见问题:

更新日志: