Issues with PredictLeads Job Data Accuracy for Find Open Jobs

The Find Jobs waterfall uses multiple data sources including PredictLeads, Google Jobs, and our native jobs database to provide comprehensive job data. The PredictLeads integration returns a "Total Job Count" number along with an array of actual jobs. Job counts can vary between providers due to different data collection methods, filtering criteria, and update frequencies. Each provider in the waterfall may have access to different job postings or apply different validation processes. What specific number are you seeing that appears incorrect, and how does it compare to what you expected?

Sources: Find Open Jobs with PredictLeads Find Jobs Source + Enrichment [Clay 101] - Clay University Find Jobs Source + Enrichment [Clay 101] - Clay University

The PredictLeads integration returns both a "Total Job Count" number and an array of actual jobs. The discrepancy between 8 jobs and 521 total count likely occurs because the Total Job Count represents all available positions in PredictLeads' database for that company, while the Jobs array may be limited by filters you've applied (departments, job title keywords, job description keywords, days since posted, or location requirements). Check your input filters - if you've set specific departments, job title filters, description keywords, or other criteria, these will reduce the actual jobs returned while the total count reflects all jobs before filtering. Try removing or broadening your filters to see more of the 521 jobs in your results array.

Sources: Find Open Jobs with PredictLeads Find Jobs Source + Enrichment [Clay 101] - Clay University Find Jobs Source + Enrichment [Clay 101] - Clay University

Hi Karim - thanks so much for reaching out! Happy to help you here - could you please send the Clay table link you are seeing this issue in if possible?