Resolution
How to match signals to your existing contact and company records.
Every signal comes pre-resolved with identifiers for matching to your existing data.
What's Included
Company-level signals include:
- Company name, domain, LinkedIn URL
- Industries, employee count range
Contact-level signals include:
- Contact name, email, job title, LinkedIn URL, location
- The company object for the contact's current employer
This means you can always join on company identifiers, regardless of signal type.
Join Keys
| Priority | Contact Matching | Company Matching |
|---|---|---|
| 1st | contact.email | company.domain |
| 2nd | contact.linkedin_url | company.linkedin_url |
| 3rd | — | company.name (fuzzy) |
Example: Contact matching SQL
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'Example: Company matching SQL
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_urlCoverage
| Identifier | Coverage |
|---|---|
contact.email | 85-95% |
contact.linkedin_url | 90-98% |
company.domain | 99%+ |
company.linkedin_url | 95%+ |
Data Quality
- Email addresses are format-validated and domain-verified
- LinkedIn URLs are normalized to canonical format
- Company domains exclude generic providers (gmail.com, etc.)
- Timestamps are ISO 8601 UTC
Contact [email protected] for custom resolution requirements.
Updated 2 days ago
