How it works

From first event to full picture

Send one event and Lume does the rest, telling your humans, bots, and AI agents apart so you get a clean human count you can trust and finally see the half your analytics is blind to.

Install

Connect your CDN logs or edge for a no-code path with zero client JS and no added latency, or use one ingest token and one SDK call.

Classify

Every request is sorted into the segments that matter (real humans, the humans AI referred you, AI agents, crawlers, and ordinary bots) across 17 agent types matched against the live catalog.

Verify

Signatures, reverse DNS, and published IP ranges are checked against the 7 verified operators, so a spoofable user-agent is never taken at face value. Anything claiming to be a recognized agent but failing the checks is flagged as unverified, not hidden.

Dashboard

Your whole audience appears live and unsampled: clean human count up top, every bot and AI agent told apart beneath it, with per-operator and per-page drill-downs so you can see which agents hit which URLs and act on it.

The segments in your traffic

Each of the four steps feeds one picture. Here’s what you’re looking at, and why each segment matters.

Humans

Your clean, bot-free count.

AI-referred humans

Real people who clicked through from an AI answer, named by assistant.

AI agents

Software acting for a person: real intent, not something to filter out.

AI crawlers

Bots fetching your pages to train or ground models. Are they even reaching you?

Search & utility bots

Expected and benign, but finally told apart.

Spoofers

Claiming to be a recognized agent but failing verification. The one to actually worry about.

One call to start

Install the dependency-free SDK and send your first event with a single call.

import { Lume } from 'lumetraffic'

const lume = new Lume(process.env.LUME_INGEST_TOKEN!)
res.on('finish', () => lume.trackPageviewOrRESTCall(req, res))

Prefer no code? Drop in an edge or CDN integration and Lume reads your traffic from the request path or the logs you already emit: no client JS, no added latency, and it sees the crawlers your analytics can’t.

TypeScript SDKREST ingestCloudflare WorkerVercel middlewareWordPress pluginFastlyAkamaiAWS CloudFrontGCPCDN logs

Your first event is a minute away.

One ingest token, one SDK call. Free plan, no card required.

Start for free →