Sorry again for the late reply! This is likely an issue on our end where the number presented mismatches the actual final results, but the engineering team is aware and addressing it. Another thing that could affect the final result is how many title variations you have since people may have quite a few ways to show themselves on Linkedin, so maybe including a few more variations could get you a bit more results too.
Finally, this is also likely because our LinkedIn integrations don't use your active session or cookies to find data on LinkedIn. The tradeoff is that it could miss some information here and there, especially if there are privacy restrictions in their profiles, meaning that you need to be logged into an account to see all the data, that could be a limitation set by LinkedIn or the person themselves.We're continuously working on these tools to improve coverage though!
Great question! The best way to get more real-time and extended results is by using a scraping tool/extension, such as Phantombuster. Just keep in mind that LI likes to prevent scraping so I'd follow Phantombuster's daily scraping limits to prevent any account ban or warnings.
Ok got it, so there's no internal function yet to Clay to sync the LI session cookie , similar to phantombuster. 😅 This makes sense! Thanks, will explore integrating phantom on our steps with Clay to improve our internal actions with the platform.