Person-level identification
In short
Person-level identification is the process of linking an online interaction, such as a website visit or email click, to a specific, named person. It goes one step beyond company-level identification, which only tells you which organization was present.
B2B teams use it to follow up with the actual person who showed interest. It depends on first-party identifiers such as form fills, email click-throughs, and logins, and it carries privacy obligations that vary by region.
Person-level vs. company-level identification
Company-level methods, such as reverse IP lookup, tell you that someone at Acme visited your pricing page. Person-level methods try to tell you who.
- Company-level: Broader coverage, lower privacy risk, but you still have to find the right contact.
- Person-level: Narrower coverage, more actionable, and subject to stricter consent rules.
How it works
Known identifiers
A visitor fills a form, clicks a tracked email link, signs in, or registers for a webinar. Their cookie or session is then tied to an email address.
Identity matching
Some tools match a hashed email or device identifier against a database of known profiles. Match rates vary widely and you should test them on your own traffic.
CRM sync
Matched activity is attached to the contact record, so reps see which pages a named person viewed.
How GTM teams use it
- Sales alerts: Notify the owner when a known contact returns to pricing or a comparison page.
- Personalized follow-up: Reference the topic they researched, without quoting their browsing history back at them.
- Ad suppression and targeting: Exclude current customers and target known contacts from open deals.
- Scoring: Add engagement from named people to lead and account scores.
Privacy and consent
Identifying individuals involves personal data. Rules such as GDPR in Europe and various state laws in the US set requirements on consent, notice, and opt-out. Have a lawful basis, disclose tracking in your privacy policy, and honor opt-outs. This is general information, not legal advice; check with counsel for your situation.
Common mistakes
- Over-personalizing: Messages that reveal exact browsing behavior feel intrusive and reduce replies.
- Trusting every match: Identity matches can be wrong. Treat them as a lead, not a fact.
- Skipping compliance review: Collection methods that are fine in one region may not be in another.
- Acting on a single visit: One page view is weak. Combine it with fit and other signals.
Person-level identification FAQs
What is person-level identification?
Person-level identification links online activity, such as a website visit or email click, to a specific named individual instead of only their company. It lets sales and marketing follow up with the actual person who showed interest.
How is person-level identification different from company-level identification?
Company-level identification tells you which organization visited, usually from network data. Person-level identification tries to name the individual, using identifiers like form fills or email clicks. It is more actionable but covers fewer visitors and faces stricter privacy rules.
Is person-level identification legal under GDPR?
It depends on your lawful basis, consent practices, and how data is collected and disclosed. GDPR treats identifiable visitor data as personal data, so notice and, often, consent are needed. This is general information and not legal advice; consult counsel.
How accurate is person-level identification?
Accuracy varies by method and by audience. Identifiers a person gave you directly, such as a form fill, are reliable. Probabilistic matching is less so. Test match quality on your own traffic and treat uncertain matches as leads to verify.
