The 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.

How long is my data kept?

One to four years depending on plan, extendable to ten, set per site as a window in days that the database itself enforces. The whole subject, edges included, is retention.

Where do I buy 5, 7 or 10 years of history?

On the Billing screen in the panel, as an add-on to any plan, billed with your subscription. Prices and the one warning that matters, that longer history is never retroactive, are on the retention page.

Kehai sets no analytics cookie and writes no visitor identifier to browser storage, but the script reads page and device information. Whether that requires consent depends on your configuration and applicable law. Review it with your counsel, and the privacy page is written for exactly that conversation.

Will the script slow my site down?

The tracker is 2.5 kB gzipped - the same file on every page, no per-site additions. It loads with defer and sends with sendBeacon. Query exclusions are enforced server-side, so Settings changes never require replacing the tag. The tag.

Do ad blockers block Kehai?

Some content blockers block analytics scripts wholesale, Kehai's among them, and those browsers' pageviews are simply not counted: Kehai reports what it measured and never models the gap in. Server-side orders use a separate delivery path, so browser blockers do not block that request. They still require a working integration, accepted payloads, and successful delivery.

Can I try it before paying?

Yes, on your own site: every plan starts with 7 days free. Checkout asks for a card and takes nothing for 7 days, canceling inside the trial costs nothing, and on day 8 the card is charged the plan's price. The DNS proof still applies, so a trial runs on a domain you control.

If you would rather look before you install anything, the demo account is public and needs no card. It also shows what a first week cannot: the demo shop has two years of generated traffic behind it, so Forecast, Pacing, and the revenue reports are full there, where a site measuring its first days has too little history for any of them. Open the demo, or sign in with demo@kehai.io and northbound-demo-2026: a read-only viewer with every screen open, on a shop whose traffic is generated so that nobody in it is real.

How many sites can I add?

Per plan: Solo 1, Core 5, Growth 10, Commerce 15. A new site is created on the Sites screen in Settings and starts counting the moment its snippet is pasted. Only the first domain, at purchase, carries the DNS proof, because from then on intake refuses traffic from hostnames a site does not own. A site's subdomains ride along free, and a second address for the same shop belongs in additional domains rather than a second site. Site basics.

Can I bring my GA4 history?

Yes, along with Plausible and Umami: history imports into the same charts, every day labeled with the tool that measured it, and counted days always winning. Bring your history.

Why are my numbers different from GA4's?

Definitions, consent configuration, blockers, time zones, and delivery can all change the population and the result. Neither tool is guaranteed to report the larger number. The full dictionary and the structural reasons are Coming from GA4.

How do I track sales and revenue?

Two ways: one line of JavaScript on the thank-you page for a conversion rate in minutes, or one request from your server for revenue your accountant would sign. Which, when, and the code for both: Ecommerce.

Yes: a share link is a read-only live page you compose, revocable at any moment, with every opening counted. Share links.

What happens if I stop paying?

Fourteen days of grace with everything working, then reports pause while measuring continues and nothing is deleted. After an ended subscription you get 30 days to export everything. The whole timeline.

Can I delete something that was measured?

An exclusion hides it from reports at once and reversibly, the Danger screen erases a site's measurements entirely, and for anything narrower the operator handles it through the audited path. Your half of the bargain.

Is there an API?

Every report over REST behind one key, raw export as newline-delimited JSON, MCP for assistants, and an OpenAPI schema generated from the same registry the panel runs on. REST API and MCP.

How is this different from Matomo, Plausible, Fathom, Umami, or Google Analytics?

Every visit is counted with the rule printed beside the number, measured, imported, and modeled figures never share a column, history from the tool you leave arrives labeled with its source, and revenue comes from the shop's server rather than a browser pixel. There is no free plan, no session replay, no heatmap, and no cross-day visitor profile, because each of those needs a fingerprint or a cookie this product refuses to set. The definitions are How counting works, and the translation of the other tool's terms is Coming from GA4.

Asked in your words, answered in three sentences.