Contacts & Person-Level Identification

Identify the actual people visiting your site, not just their companies

Most visitor identification tools stop at the company level – they tell you that "someone from Acme Corp" visited your pricing page but not who. ClearView goes further. Using a multi-step identity resolution chain, ClearView can identify the specific individuals behind those visits, giving your sales team the names, emails, job titles, and LinkedIn profiles they need to reach out directly.

Company-Level vs. Person-Level Identification

Understanding the difference between these two layers is key to getting the most out of ClearView.

Company-Level

Every visitor can be resolved to a company using IP-to-company mapping. This gives you the company name, domain, industry, size, and location. Company identification works for virtually all B2B traffic and does not require any prior relationship with the visitor.

Coverage: ~95% of B2B traffic

Person-Level

When ClearView can match a visitor to a specific individual, you get the person's full profile – name, email, phone, job title, seniority, department, LinkedIn URL, and more. Person-level identification uses a resolution chain that combines multiple identity signals.

Coverage: ~25-40% of identified companies

The Identity Resolution Chain

ClearView resolves visitor identities through a multi-step chain. Each step attempts to link the anonymous visitor to a known person, and the process stops as soon as a high-confidence match is found.

IP Resolution

The visitor's IP address is mapped to a company using commercial IP-to-company databases. This establishes the company context for all subsequent steps.

Hashed Email Matching

If the visitor has previously interacted with your emails or forms, ClearView can match their hashed email identifier via ClearView's identity resolution network. This does not expose raw email addresses in transit.

Identity Graph Resolution

The hashed email or device signals are matched against an identity graph that aggregates professional identity data from public and licensed sources. When a match is found, the full contact profile is returned and linked to the visitor record.

Enrichment

Once a person is identified, ClearView enriches the record with additional data points – phone number, LinkedIn URL, seniority level, department, demographics, and work history – sourced from professional databases.

Available Contact Fields

When ClearView successfully identifies a person, the following fields are available on the contact record. Not all fields are populated for every contact – availability depends on the data sources and the individual's public profile.

Field	Type	Description
`name`	string	Full name of the contact (first and last)
`email`	string	Work email address
`phone`	string	Direct phone number or mobile
`jobTitle`	string	Current job title (e.g., "VP of Engineering")
`seniority`	string	Seniority level: entry, mid, senior, manager, director, vp, c-suite
`department`	string	Department or function: Engineering, Sales, Marketing, HR, Finance, etc.
`linkedinUrl`	string	URL to the contact's LinkedIn profile
`location`	object	City, state, and country of the contact
`demographics`	object	Age range, gender (when publicly available)
`workHistory`	array	Previous companies, titles, and date ranges from professional profile
`companyDomain`	string	The domain of the contact's current employer
`firstSeenAt`	datetime	When this contact was first identified on your site
`lastSeenAt`	datetime	Most recent visit timestamp

How Contacts Are Created and Enriched

Contacts are created automatically when the identity resolution chain produces a high-confidence match. There is nothing your team needs to do – ClearView handles the entire process in real-time as visitors browse your site.

Automatic creation

When a visitor is resolved to a person, a contact record is created and linked to the company. If the contact already exists, it is updated with the latest visit data.

Progressive enrichment

Contact records are enriched over time. If new data becomes available (e.g., a phone number or updated job title), ClearView updates the record automatically.

De-duplication

ClearView de-duplicates contacts by email address. If the same person visits from different IPs or devices, all activity is merged into a single contact record.

Activity tracking

Every page view, session, and interaction is logged against the contact record, giving your team a full timeline of engagement.

API Reference

Retrieve contacts via the API to sync with your CRM or build custom integrations.

List Contacts for a Company

GET /api/v1/companies/:domain/contacts

bash

curl -X GET "https://app.democlearview.com/api/v1/companies/acme.com/contacts" \
  -H "Authorization: Bearer YOUR_API_KEY"
# Response
{
  "data": [
    {
      "id": "ct_abc123",
      "name": "Jane Smith",
      "email": "jane@acme.com",
      "phone": "+1-555-0123",
      "jobTitle": "VP of Engineering",
      "seniority": "vp",
      "department": "Engineering",
      "linkedinUrl": "https://linkedin.com/in/janesmith",
      "location": {
        "city": "San Francisco",
        "state": "CA",
        "country": "US"
      },
      "firstSeenAt": "2026-03-20T09:15:00Z",
      "lastSeenAt": "2026-04-10T14:22:00Z",
      "pageViews": 12,
      "sessions": 4
    }
  ],
  "pagination": { "total": 3, "page": 1, "limit": 50 }
}

Search Contacts

GET /api/v1/contacts

bash

# Search contacts by seniority and department
curl -X GET "https://app.democlearview.com/api/v1/contacts?seniority=vp,c-suite&department=Engineering&limit=20" \
  -H "Authorization: Bearer YOUR_API_KEY"
# Search by recency
curl -X GET "https://app.democlearview.com/api/v1/contacts?lastSeenAfter=2026-04-01T00:00:00Z&sort=lastSeenAt&order=desc" \
  -H "Authorization: Bearer YOUR_API_KEY"

Data Handling

All hashed email matching is performed without exposing raw email addresses in transit. Contact data is stored encrypted at rest, and you can delete any contact record at any time.