looking into the issue

Thank you.

We just updated the actor

Thank you for reporting the issue (you were right, issue related to the type of url being a lead list)

We stay available if any error arise

Great service folks, appreciate you - going to test it now.

It still is giving "undefined" values.

My bad we forgot to rebuild the actor

try again

You guys are amazing. It works now, thank you. I use this to steer multi-language account-based campaigns (sales application). Finally I can just extract which languages they speak - thanks to you guys and make lists accordingly based on language spoken.

Product idea:

I get now all these deep-contact scraping output values. In my use case, I only am interested in the spoken languages. If there would or could be any way to toggle/select what fields I am interested in, that would be amazing.

I expect it then also would go much faster because automatically taking all that data, is a bit heavy and it takes seconds and seconds, per lead. The difference in speed vs not deep-contact searching is significant. I appreciate it's because it has to scrape each profile (1 by 1) vs just extracting a sales navigator lead list (less values, faster) - but still.

On apify interface, when exporting output, you can select the column name you want to download or select the column name you want to exclude from download

Thank you for the feeback !

Thank you, will check it out. That does however not increase the scraping speed. Was curious if somehow selecting what you want to deep-contact scrape on a LI profile, could potentially speed it up (combined with enabling me to only extract what I want). So rather than a full scrape, a more directed scrape. Imagined it could speed up the overall process of scraping a whole list, profile per profile.

it won't change anything about speed , for deep profile we collect the complementary data in 1 extra step all together (we don't parse HTML)