Research use
Use this methodology to test company-name-to-domain matching before CRM writes, enrichment, routing, or dedupe depend on the result.
Explore productUse this framework to measure whether company-name-to-domain matching is ready for CRM cleanup, enrichment preparation, routing, or account identity workflows.
Use this methodology to test company-name-to-domain matching before CRM writes, enrichment, routing, or dedupe depend on the result.
Explore productTest company names with optional country, industry, product line, source-system, and CRM context fields.
Measure returned domain, confidence, live-domain status, supporting reasons, lowering reasons, and no-match outcomes.
This page defines a benchmark method. It does not publish private customer data or claim universal match accuracy.
The goal is to measure decisions the business can use, not only whether a domain string was returned. Keep the accepted-domain answer key separate from the API response until scoring.
Include exact legal names, brand names, subsidiaries, regional names, abbreviations, and intentionally ambiguous names.
For each row, record the accepted official domain, expected review state, or no-match state before running the API.
Send the same input fields through the Company Domain Lookup API and store the full response.
Review exact matches, accepted alternate domains, review-needed results, no matches, and unsafe false accepts.
| Confidence range | Recommended action |
|---|---|
| 90-100 | Candidate for automated write to a staging or enrichment-input field when reasons support the match. |
| 70-89 | Route to review or require a secondary rule before overwriting trusted CRM fields. |
| Below 70 | Hold the domain, store reasons, and keep the submitted company name for later review. |
| No match | Leave the domain blank and avoid enrichment or routing rules that require official domain identity. |
Create an API key, run a representative company-name sample, and compare match quality before CRM writes depend on the result.