Optimize Job Search by Company Domain to Avoid Duplicates | Clay

Optimize Job Search by Company Domain to Avoid Duplicates

I have a list of contacts with company data such as website and company name. I want to search for open job positions for these companies, but I only want to search each company once. Since I have multiple contacts from the same company, searching for each contact would result in duplicate searches for the same domain. How can I optimize the search to be performed only once per company or domain?

4 comments

Channeled
APP
·
·
You can efficiently search for job openings across your contact list companies using our "Job Openings" waterfall enrichment approach. Here's how: 1. Start with your existing list of companies in Clay 2. Apply the "Job Openings" waterfall enrichment, which combines data from multiple sources 3. Use the company domain as your search parameter 4. Add any relevant keywords to filter for specific positions you're interested inThe waterfall automatically handles duplicate prevention since it runs against your specific company list, ensuring each domain is only searched once. Source: Find Jobs Source + Enrichment [Clay 101] - Clay University
David L.
·
·
It isn't a company list it's a lead list so I have more than 1 contact per company
Channeled
APP
·
·
You can enrich your existing company list with job openings using our Job Openings waterfall. Here's how to do it: 1. Start with your list of companies in Clay 2. Use the "Job Openings" waterfall enrichment 3. Set the company domain as a parameter 4. Add any relevant keywords for the positions you want to find 5. Run the waterfall to see matching job openingsThis approach is efficient as it will search for jobs once per company rather than for each contact, and you can specify exactly what types of positions you're looking for by using keywords in your search parameters. Sources: Find Jobs Source + Enrichment [Clay 101] - Clay University Find Active Job Openings with Companies, People, Jobs
Channeled
APP
·
·
Hi David L.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: