KALYDRONKalydron Pulse
Analytics that count what matters — without counting people.
One line on your site. Sessions, search performance, backlinks — and the number nobody else shows you: visitors arriving from ChatGPT, Claude, and Perplexity. Cookieless, no consent banner, nothing identifying. Ever. Built for healthcare practices first.
Live right now: sickfade.com — 1.1k visitors in 30 days, 1% from AI assistants. Measured by this tag, shown in public.
Built for healthcare first
Nothing identifying. Nothing to breach, leak, or subpoena.
Pulse exists because our first clients were therapy and counseling practices — sites where “who visited this page” must never become a stored fact. The usual fix is a consent banner bolted onto Google Analytics. Ours is a tag that can’t identify anyone in the first place.
- NO COOKIES, NO IDS
- The visitor hash is salted and rotates every day. Tuesday’s visitor can’t be linked to Wednesday’s — by anyone, including us.
- FIRST-PARTY ONLY
- Counts go from your site to our database. No ad network, no Google, no third party ever receives a byte about your visitors.
- PATHS, NOT PEOPLE
- You learn that 34 visits reached your trauma-therapy page from ChatGPT this month — never who they were.
The context that makes this matter: health practices and hospital systems have spent recent years in court over analytics pixels that shipped page-visit data to ad platforms. Pulse’s answer isn’t better paperwork — it’s collecting nothing a lawsuit could be about. We say “no personal information collected,” never “HIPAA compliant” — compliance is a property of your whole practice; our part is handing it nothing to worry about. That’s point four of the Kalydron Standard: privacy by default.
Why not just Google Analytics
Same job. Opposite philosophy.
| gtag.js (GA4) | k.js (Pulse) | |
|---|---|---|
| Weight | ~130 KB of JavaScript | 1.2 KB — about 100× smaller |
| Identity | Cookies + a persistent client ID that links your visits for months | No cookies, no ID — a daily-rotating hash; visits can’t be linked across days, even by us |
| Consent banner | Required in most serious jurisdictions | Not needed — nothing identifying is collected |
| Your data | Lives on Google’s servers, sampled, deleted after 2–14 months | Lives in our Postgres, unsampled, kept permanently |
| AI traffic | Buried under generic “Referral” | The headline metric — ChatGPT, Claude, Perplexity, counted by name |
| The dashboard | GA4 — famously impenetrable | Five numbers a business owner reads in ten seconds |
The deeper difference is intent: gtag measures people, because visitor profiles feed an ad machine. Pulse measures traffic — how many came, where from, is it growing — and deliberately can’t do the rest. Already run GA? Pulse runs alongside it; it weighs nothing and shows the AI number GA misses.
How it works
Three moving parts, all boring on purpose.
- 01
One line loads the tag
Your site loads k.js from our edge — 1.2 KB, deferred, cached for a day. If we ever went down, your site wouldn’t notice: it fails silently, never blocks a page.
- 02
A cookieless beacon counts the visit
Path, referrer, and a salted hash that rotates daily — that’s the entire payload. When the referrer is chatgpt.com or perplexity.ai, that visit is counted as AI, by name. No referrer stripped? We undercount — the AI number is a floor, never a guess.
- 03
Search data joins it nightly
Every night we merge Search Console and Bing Webmaster numbers — clicks, impressions, backlinks — into permanent history. Google deletes its own data after 16 months; we don’t.
Scale isn’t your problem to think about: the tag is served from a global edge CDN and the collector scales horizontally per request. A viral day on your site is a rounding error here — and if Pulse ever hiccups, your site doesn’t. Worst case is a gap in our chart, never a slow page of yours.
Get it on your site
Install is one line. Really.
<script defer src="https://kalydron.com/k.js" data-site="YOURSITE"></script>- 1 · Reach out — we register your site and hand you your data-site id and dashboard login.
- 2 · Paste the line into your site’s <head>. Works everywhere — WordPress, Squarespace, Wix, Webflow, or hand-written HTML all have a “custom code in header” box.
- 3 · Numbers appear within minutes. Search Console and backlinks join after we connect them — no extra code on your end.
Prefer not to touch code at all? We install it for you — most clients never open an editor. Reach out.
Measured in the open
Numbers you can show off — and check.
Opt-in sites get a public verify page and a live badge for their own site — real 30-day numbers, drawn straight from measurements, never typed in by the owner. They also appear on the public leaderboard. We say “not self-reported” and mean exactly that — no tag on the internet is tamper-proof, ours included, so where Search Console is connected we cross-check first-party counts against Google’s own numbers and mark the row verified.