Visitor Intelligence · Capability
Known-visitor identification with Lumi Links
Known-visitor identification means knowing when a specific CRM person is the one on your website. Lumi Links carry the CRM’s own recipient ID into the click, resolve that exact record on a genuine visit, and stitch the identity to the visitor — without letting email scanners masquerade as the person.
Exact person, not a company guess
CRM-native identity links
Provider-specific link templates for HubSpot, Salesforce, Close, and Attio carry the provider plus the contact, lead, or member identifier in Lumitra identity parameters — the CRM personalizes the merge field per recipient.
First-touch resolution
The recipient is resolved inline so the visitor record can show the person immediately. A local provider-link cache means a cache hit needs zero CRM calls; a miss dispatches to the right CRM adapter and hydrates name and email from that exact record.
Shared identity
The resolved person is deduped against existing Company Intelligence contacts and identity profiles, so website identity ties to the same person instead of creating another parallel contact layer.
Scanner-safe
Bot detection gates identity resolution, so security-scanner prefetches never become fake known-person visits.
How it works
- Build. Create the CRM-specific tracked-link template for the destination — the destination URL is preserved, identity travels in Lumitra parameters.
- Personalize. The CRM replaces its merge field with the actual recipient record ID at send time, so Lumitra receives a provider-native identifier rather than a fuzzy person hint.
- Gate & resolve. The first touch is recorded, scanner traffic is filtered, then the exact provider record is resolved — or served from cache. A confirmed not-found ID is negatively cached; transient provider failures stay retryable with the original observation retained.
- Stitch. The identity attaches to the visitor and is reused across later sessions — and everything they do next is interpreted by session intelligence.
What happens on first touch
| Event | Outcome |
|---|---|
| Real recipient click | Resolve and identify the person. |
| Known scanner / prefetch | Record the observation, flag it as a bot, do not resolve. |
| Record not found | Store a negative cache entry so the same bad ID is not retried. |
| Provider unavailable | Keep the signal and retry resolution on a later visit. |
Frequently asked questions
How is this different from IP-based visitor identification?
IP-based identification infers a company from a network address and can never reliably name a person. Known-visitor identification is deterministic: the CRM itself personalizes a Lumi Link with its own record identifier, so when the recipient clicks, Lumitra resolves that exact provider record — the contact, lead, or member — rather than guessing from firmographics.
Which CRMs does it work with?
Lumitra builds provider-specific tracked-link templates for HubSpot, Salesforce, Close, and Attio using each system's merge fields. The CRM replaces the merge field with the real recipient record ID at send time, and Lumitra receives the provider-native identifier while the destination URL is preserved.
What stops an email security scanner from becoming a fake visit?
Known email scanners and link-preview bots are flagged before CRM resolution runs, so a Proofpoint- or Mimecast-style prefetch stays anonymous instead of impersonating the recipient. The scanner observation is still written for audit, and the real recipient's later click becomes the first identity-resolving event.
Does identification overwrite campaign attribution?
No. Identity parameters stay separate from UTM, referrer, and campaign context — who the person is never overwrites how the visit was sourced. Both live on the same visitor and session context, so you can answer identity questions and attribution questions from the same record.
What happens to the visitor's earlier anonymous sessions?
They stay connected. A visitor maps to one identity link, and re-identification updates that relationship instead of creating parallel identities. The resolved email is deduped against existing Company Intelligence contacts so the same person is reused rather than duplicated — and later sessions from the same browser remain attached to them.
See a known prospect return to your site
Book a demo and watch a CRM contact’s click resolve into an identified visitor with their full session history attached.