01
Identify
Lumi Links resolve the exact CRM contact behind a click. Forms and logged-in users attach identity to the same browser history.
Visitor IntelligenceKnow who cares.
Know how much.
Real visitor behavior, narrated session by session — identity, intent, and attribution kept separate, with bots and email scanners filtered before anything is scored.
One script tag · Works with your CRM · Bot & scanner protection built in
71.5%of traffic
identified
identified
47.5%bot traffic
filtered out
filtered out
4thsession flagged
as buying intent
as buying intent
How it works
From anonymous visit
to buyer context.
One tracker captures identity, sessions, and attribution separately — then stitches them into context your team can route on.
02
Understand
Sessions become narratives: content attention, click outcomes, form progression, searches, and pricing behavior.
03
Act
High-intent, returning, and form-incomplete cohorts route into CRM, alerts, and GTM Agents — with bots already gone.
Session intelligence
What they tried.
Not just where they went.
Semantic content attention, click outcomes, form journeys with the exact stall point — interpreted into a narrative a rep can read before the call.
Explore Session Intelligence →Sections read6
Pricing time46s
Form progress3/5
Downloads1
SignalOutcomeDetailWhen
Compared plans✓annual tab · ×3 → 1 attempt09:14
Searched “SOC 2”✓opened /security09:15
Form stalled!step 3 · “Company size”09:15
AI session narration
Returning visitor compared annual plans, verified SOC 2, then stalled on company size — pricing-ready. Route to an AE with the security review as context.
Known-visitor identification
The CRM names the person.
The click proves it.
Lumi Links carry your CRM's own record ID into the click — resolved deterministically, deduped against existing contacts, with email scanners gated out before identity ever resolves.
Explore Known-Visitor Identification →DR
Identified visitor
Dana Reyes
VP RevOps · Northwind · via Lumi LinkIdentity ✓ · Attribution kept
ResolutionCRM record contact_8841
Scanner checkProofpoint prefetch gated
History4 anonymous sessions linked
Sourceutm_campaign=q3-launch
TimelineAnon · Anon · Anon · Identifiedsame browser, one identityReturned to /pricing2m ago
Kept separate
✓ Identity — who they are
✓ Attribution — how they arrived
✓ Bots — never resolve identity
Bot detection
Bots never
get a vote.
Crawlers, link previews, and email security scanners are classified at capture and kept out of intent scoring and agent triggers — preserved as an inspectable cohort, never silently deleted.
Explore Bot Detection →Bot activity
Googlebot — crawl, excluded from intent
Generic crawlers — user-agent tiers
Applebot — excluded, kept queryable
Email scanners — Proofpoint, Mimecast, Barracuda
Downstream effect
Visitor counts clean
Intent scores human-only
Known-visitor IDs scanner-safe
Agent triggers real buyers
See your real traffic
for the first time.
Drop in one script tag and watch identified companies, session narratives, and clean intent appear — bots already gone.
What is visitor intelligence?
Visitor intelligence is the practice of turning anonymous website traffic into usable buyer context: which company is visiting, what each session shows about intent, and which known person is behind a click. It differs from web analytics by resolving identity and narrating behavior per account — after bots and email scanners are filtered out.
- How is visitor intelligence different from website analytics?
- Analytics counts sessions, pages, and conversions in aggregate. Visitor intelligence resolves who the traffic belongs to and what the visit meant — the company behind the session, the content that actually held attention, the form that stalled, and the buying signal a rep can act on. Analytics tells you a pricing page was viewed eight times; visitor intelligence tells you which account viewed it.
- Can visitor intelligence identify individual people?
- For ordinary anonymous traffic, identification is company-level: the organization behind the visit, stitched into an account timeline. The exact person is resolved when they arrive through a tracked Lumi Link, which ties the click to a known CRM contact rather than guessing an identity from an IP address.
- Do bots distort visitor intelligence data?
- They do, which is why filtering happens before scoring rather than after. Crawlers, link previews, and email security scanners generate page views and clicks that look like buyer interest — including scanners that follow tracked links inside an email and can otherwise be mistaken for the recipient. Filtering them first keeps counts, intent signals, and downstream GTM actions honest.
Inside Visitor Intelligence
How the parts of Visitor Intelligence actually work — each capability explained with the real product behavior behind it.
Bot Detection
Filter crawlers, link previews, and email security scanners before they corrupt visitor counts, intent signals, and downstream GTM actions.
Session Intelligence
Understand what a buyer actually tried to do — semantic content attention, click outcomes, form progression, searches, and a narrative of the visit.
Known-Visitor Identification
Resolve the exact CRM contact behind a click with Lumi Links, stitch their identity to the visitor, and keep scanners from impersonating them.