Kehai is web analytics that counts what happened on your site without identifying who it happened to. One small script, no analytics cookies, and no visitor identifier in browser storage. The script reads page and device information. Assess consent for your installation with the field inventory in the cookie and storage statement.

The name is Japanese. 気配 means sensing a presence without seeing it, and that is the entire design: you know somebody was there, what they read, where they came from, and what it led to, without ever holding who they were.

Three commitments shape every number in the panel:

Measured, imported, or modeled. A figure is measured by the snippet, imported from your old tool, or modeled by the forecast, and the three are labeled and never summed together. No sampling, no "estimated" rows quietly mixed in.
A visitor code is scoped to one UTC day. A new salt is used at midnight UTC, and visits end at that boundary too. Recorded events remain for the site's retention window. How counting works has the details.
Everything leaves. Every screen downloads, every report answers over the API, and the whole site streams out raw. Your numbers are yours, including on the day you go.

How the pieces fit

Kehai is three moving parts, and only the first is required. Everything else in these docs teaches one of them.

01The snippet counts

One deferred tag. Pageviews, visits, engaged time, outbound clicks, and file downloads, with nothing to configure, and Core Web Vitals once the performance module is on.

02You name events

A signup, a plan chosen, a quote requested: one attribute on the element, or one call from code, with properties and an optional value.

03Your server reports revenue

Orders travel server to server with the field names GA4 taught your shop, because a browser cannot be trusted with prices.

Behind all three sits one privacy model: no cookies, no browser storage, and visitor and visit codes that start fresh each UTC day. These boundaries shape the counts. They do not, on their own, settle whether your installation requires consent.

First data in two minutes

Paste the tag into the head of every page you want counted, then open your site in a browser. The first pageview appears in the panel within seconds.

every page, inside the head

<script defer src="https://stats.kehai.io/k.js?site=YOUR_SITE_ID"></script>

Copy yours from the panel

The tag above is the shape, not your tag. The panel's Install screen generates yours with your site id in its URL, then watches for the first event and tells you what arrived, or why something was refused.

The whole contract of that tag, its optional attributes, and the platform-by-platform places to paste it are on Install the snippet.

Everything in these docs

Start here

IntroductionWhat the snippet does on its own, what you can teach it, and where the numbers surface. Ten minutes of reading covers the whole product.Create your accountRegistering, proving your domain, paying, the mail that opens the panel, signing in, and bringing your team along. One pass, in the order it actually happens.Install the snippetThe script, its optional attributes, where to paste it on common platforms, and how to see the first event arrive.How counting worksThe definitions behind every number in the panel, and the privacy model that shapes them. Nothing in the reports makes sense without this page, and all of it fits on one.

Coming from another tool

Bring your historyImports from GA4, Plausible, and Umami write into the same daily layer Kehai counts into: one series, each day naming the tool that measured it, and no badge wall between your past and your present.Coming from GA4What GA4 calls users, sessions, and engagement, what Kehai calls them, and the honest reasons the numbers will not match to the decimal.

The panel

Around the panelThe sidebar, the site switcher, the date picker, the command palette, keyboard shortcuts, the bell, light mode, the five accent colors, and saved views. Ten minutes here makes every other page faster.Every setting, A to ZEvery area in the panel's own order, who can change it, what it holds, and the three things you will not find in Settings anywhere.Set up your siteTime zone, extra domains, retention, modules and the plan each needs, the two kinds of rules, and adding or restoring a site. Twenty minutes here decides what the next year of numbers means.ReportsWhat each screen answers, what every card and every screen can do, and the honesty rules the numbers follow. The map of the panel, front to back.Sharing and exportsA read-only page for somebody without an account, tagged campaign links and tracking links that count clicks, one download per screen in six formats, and the digests and alerts that arrive by mail.

Reading the reports

Overview and RealtimeKPI tiles you arrange yourself, the one rule about unfinished days that explains most red arrows, and what active right now actually means.Pages and behaviorEntry and exit pages that carry their own verdicts, the shape of a day and a week, journeys and funnels, and Core Web Vitals from real visits.Acquisition and audienceEleven channels with a strict order of proof, campaigns grouped by currency, referrers kept visible even when unknown, AI assistants as their own channel, Google's search terms beside them, and the Geo and Tech pair.Goals, pacing, and botsReading a goal's series, the difference between pacing and a forecast, when a forecast refuses to answer, and the ledger of removed bot traffic.

Count what matters

Custom eventsOne attribute where there is an element, one function call where there is not. Properties, their values read back, and the checks that keep people out of your data.GoalsA goal turns an event, a page, or an order into a daily conversion series. Three kinds, one screen, no code.

Revenue

IntegrationsConnect your commerce platform, verify payment delivery, and understand campaign attribution and refund support.EcommerceA browser can be made to say any number, so revenue travels server to server: one endpoint, one key, and the field names your shop already computes for GA4.Google Ads conversionsExport eligible commerce sales as a CSV, or let Google fetch an authenticated HTTPS feed. Set up click IDs, sale times, and stable conversion identifiers.

Machine access

REST APIThe same numbers the panel shows, from the same functions, behind one bearer key. Reports, raw export, and an OpenAPI schema that cannot drift.MCP for assistantsA read-only Model Context Protocol server on the API host. One URL, one key, and Claude, Cursor, VS Code, or any MCP client answers questions from your real reports.

The contract

Your plan and billingWhat a plan changes and what it never touches, canceling and changing plan, the 14 days after a failed card, the 30 days after an ending, visit bands as a conversation, and receipts.RetentionThe per-site window the database itself enforces, what each plan includes, where the longer add-ons are bought, and the one warning: longer history is never retroactive.Privacy, for your legal teamController and processor, assessing consent, stored data and its limits, visitor requests, and your responsibility for the data you send.

Help

Quick answersThe questions people bring from other tools, each answered short and linked to the page that owns the subject. The headings feed the search, so ask it the way you would ask a person.TroubleshootingSymptom, cause, and fix, for the situations that actually happen: nothing arrives, an event vanishes, an order is refused, or a number looks impossible.

If you are a machine

The REST contract lives at app.kehai.io/api/v1/openapi.json, generated from the same registry the panel reads, so it cannot describe a report that is not there. Assistants can read a site's reports directly over MCP.

kehai.io/llms.txt is a short index for language models. It links to the product pages, documentation, pricing, and policies.