RP
RevenueProven
All Help Articles

How does company matching between LinkedIn and CRM work?

Revenue Proven matches LinkedIn organizations to CRM companies using a three-phase algorithm: exact domain match, normalized URL match, and fuzzy name similarity as a fallback.

Company matching is the bridge between LinkedIn engagement signals and your CRM records. Without a reliable match, an engaged account cannot be credited to a deal. Revenue Proven runs three matching phases after each sync to connect as many accounts as possible while keeping false-positive rates low.

Phase 1: Exact domain match

Revenue Proven compares the website domain on the LinkedIn organization record directly against the company domain stored in your CRM. This is the highest-confidence match and is preferred over all other methods. For this to work well, make sure your CRM company records have accurate website fields populated.

Phase 2: Normalized URL match

If exact domain matching fails, Revenue Proven strips URL prefixes like www, protocol schemes, and trailing paths, then compares the normalized root domain. This catches mismatches caused by formatting differences, such as one system storing the full URL with https while the other stores just the bare domain.

Phase 3: Fuzzy name similarity

For companies still unmatched after the first two phases, Revenue Proven runs a bigram character-similarity comparison between the LinkedIn organization name and the CRM company name. This is limited to your top unmatched accounts to control performance and false positive risk. Matches below the configured similarity threshold are excluded. You can see match quality on each company row in the Company Insights table.

  • Keep CRM company website fields up to date for best match rates
  • Geographic brand qualifiers in names are never stripped (e.g., Bank of Singapore is not shortened)
  • Unmatched companies can be hidden from the attribution table with a dashboard setting
  • Match quality is shown per company and can be reviewed in the Company Insights view