Resolution / Matching to your Data

Every signal comes pre-resolved with identifiers for matching to your existing data. This page explains how we resolve social identities to business contacts, what matching keys are included, and how to join signals to your CRM or data warehouse.

How Identity Resolution Works

Contact Database

Our resolution is powered by a proprietary contact database of 250M+ contacts and 75M+ companies, ingested monthly from multiple sources. More frequent updates happen continuously as a result of our pipeline exhaust — every signal we process feeds back into the graph, improving coverage and freshness over time.

Resolution Flow

For every contact-level signal, we resolve the social identity to a business contact record:

Social Activity Detected
        ↓
Platform Identity (profile URL, handle, channel)
        ↓
Autobound Contact Database (250M+ contacts)
        ↓
Business Contact Record (work email, LinkedIn URL, job title, company)

The contact record includes a business/work email (contact.email) and LinkedIn URL (contact.linkedin_url) as matching keys, plus firmographic data about their current employer.

Business Email — Not Personal

All emails we deliver are business/work emails. Our domain validation explicitly excludes generic providers (gmail.com, yahoo.com, outlook.com, etc.). We do not deliver personal email addresses.

This is a common concern — the assumption is that social profiles (especially Twitter/X and YouTube) naturally resolve first to personal emails. That is not how our system works. The resolution goes:

Social profile → Autobound contact database → Business email

The intermediary is our identity graph (250M+ contacts with verified work emails), not the social platform's own email field.

Platform-Specific Resolution

LinkedIn

Resolution method: Most direct path. The LinkedIn profile URL is the starting identity. We match it against our contact database to resolve the profile to a business email, job title, and company.

Step-by-step:

1. LinkedIn profile URL captured from post or comment activity
2. Profile URL matched against our contact database (250M+ contacts)
3. Business email, job title, and company resolved from the matched record
4. Company firmographic data (domain, LinkedIn URL, industries, headcount) attached

Coverage: 90-98% of contact signals include a LinkedIn URL. 85-95% include a business email.

Why it's reliable: LinkedIn profile URLs are deterministic, unique identifiers — there is no ambiguity in the match.

For signal-specific details, see LinkedIn Posts and LinkedIn Comments.

Twitter / X

Resolution method: We match Twitter handles to 4M+ contacts using multiple signals.

Step-by-step:

1. Twitter handle identified from post activity
2. Cross-reference against LinkedIn profiles that list a Twitter handle
3. Full name + job title + current company matched against Twitter profile bio, location, and post content
4. LLM-assisted models evaluate linkage probability across all available signals
5. Only matches exceeding strict confidence thresholds are accepted
6. Business email and company resolved from the matched contact record

What we expose: Each Twitter contact signal includes contact.email, contact.linkedin_url, contact.twitter_url, and contact.twitter_handle — so you can see the full resolution chain.

Coverage: 10-25% of contacts in our refresh pool have a matched Twitter profile. When a signal fires, business email is populated 85-95% of the time.

For signal-specific details, see Twitter/X Posts (Contact) and Twitter/X Posts (Company).

YouTube

Resolution method: We search YouTube for prospect names and company references, then match results against our contact database.

Step-by-step:

1. YouTube videos, channels, and comments searched for prospect full name + job title + current company name
2. Matches validated against video descriptions, channel names, and transcript content
3. Strict matching criteria applied — we require strong alignment between the YouTube identity and the known contact record
4. Business email and company resolved from the matched contact record

What we expose: Each YouTube contact signal includes contactEmail, contactLinkedinUrl, companyUrl, and companyLinkedinUrl.

Coverage: 1-5% of contacts (YouTube coverage is naturally lower than LinkedIn or Twitter, but the signals that do match are high-value).

For signal-specific details, see YouTube.

Company-Level Signals (LinkedIn, Twitter/X, Reddit, YouTube, etc.)

Company-level signals use a simpler resolution path because the identity is the company itself, not an individual:

Step-by-step:

1. Company identified from the platform (LinkedIn company page, Twitter company handle, Reddit mention, etc.)
2. Matched to our company database (75M+ companies) using company name, domain, and/or LinkedIn company URL
3. Firmographic data attached: domain, LinkedIn URL, industries, employee count range, description

What we expose: Every company signal includes company.domain and company.linkedin_url as matching keys.

Coverage: company.domain is populated on 99%+ of signals. company.linkedin_url is populated on 95%+.

Match Accuracy & Confidence

Overall Match Rate

Our identity resolution has a 99.8% accuracy rate. We are very strict — we prefer no match over a false match. If we cannot resolve a social identity to a business contact with high confidence, we do not deliver the signal.

Confidence & Quality Fields

Several signal types expose confidence and quality scores you can use for filtering:

De-duplication & False Positive Prevention

• Strict multi-signal matching: We don't match on name alone. Resolution uses full name + job title + current company, validated against profile bio, location, and content.
• LLM-assisted verification: Ambiguous cases are evaluated by language models that assess linkage probability across all available signals.
• Deterministic secondary keys: LinkedIn URLs serve as unique, deterministic identifiers — eliminating same-name collisions.
• Domain validation: Company domains exclude generic email providers. Contact emails are format-validated and domain-verified.
• Continuous feedback loop: Our pipeline exhaust feeds back into the identity graph, improving accuracy over time.

What's Included in Every Signal

Company-level signals include:

• Company name, domain, LinkedIn URL
• Industries, employee count range, description

Contact-level signals include:

• Contact name, email, job title, LinkedIn URL, location
• The full company object for the contact's current employer

This means you can always join on company identifiers, regardless of signal type.

Join Keys

SELECT
  c.id as contact_id,
  s.*
FROM signals s
LEFT JOIN contacts c
  ON LOWER(s.contact.email) = LOWER(c.email)
  OR s.contact.linkedin_url = c.linkedin_url
WHERE s.association = 'contact'

SELECT
  a.id as account_id,
  s.*
FROM signals s
LEFT JOIN accounts a
  ON LOWER(s.company.domain) = LOWER(a.domain)
  OR s.company.linkedin_url = a.linkedin_url

Coverage Summary

Contact Identifier Coverage

Company Identifier Coverage

Signal Coverage by Platform

Data Quality

• Email addresses are format-validated and domain-verified
• Generic email providers (gmail.com, yahoo.com, etc.) are excluded
• LinkedIn URLs are normalized to canonical format
• Company domains exclude generic providers
• Timestamps are ISO 8601 UTC

FAQ

Contact [email protected] for custom resolution requirements.