For cases like disney with multiple entities the cleanest approach is usually a combination of linkedIn based enrichment pulling current company and end dates and a fuzzy matching logic on company names/domains rather than exact matches. you can build this in Clay by mapping linkedIn data to salesforce and using rules to handle internal moves. so you don’t incorrectly mark people as no longer employed.
folks – quick question for anyone who’s tackled contact employment validation at scale.
April 2026
Quick Answer
For cases like disney with multiple entities the cleanest approach is usually a combination of linkedIn based enrichment pulling current company and end dates and a fuzzy matching logic on company names/domains rather than exact matches. you can build this in Clay by mapping linkedIn data to salesforce and using rules to handle internal moves. so you don’t incorrectly mark people as no longer employed.
○
Up to date
1 months ago1 Answer
GTM StackCommunity Insight