Tried to leverage company identifiers (website, linkedin urls), but between Clay and Zoominfo there was about a 33% discrepancy. A lot easier to solve this problem with data from one vendor of course. They are all good at getting the data, not so easy to maintain/upkeep. The basic job change signal in Clay provided too many false positives. Still searching
folks – quick question for anyone who’s tackled contact employment validation at scale.
5 Answers
Won't be perfect but maybe better (e.g. just checked Disney resorts has it's own linkedin page ugh)
Match with company ID instead of name/domain
What probably also helps is moving from company names to Linkedin identifiers
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.
Disagree or spot an error? Submit a correction here. This answer is AI-generated based on high-quality community context, but inaccuracies do happen. Your feedback helps us maintain the best information.
Add your take
Have experience with the tools discussed here? Share your honest opinion.