Highlights
Broader LinkedIn profile coverage, even when you request pictures
The broader lookup path added to LinkedIn People Profile Scraper in August was skipped when a run requested profile or company pictures. It can now participate in those runs too, and Datablist can complete missing company details and images afterward.
For example, selecting Full Name, Current Company, Profile Picture, and Company Logo no longer reduces profile coverage just because image outputs are present. The scraper can first find the person through the broader path, then complete the requested picture fields when available.
Improvements
Easier-to-scan templates and a new customer-review workflow
Ready-to-use templates previously relied mostly on their titles and shared fallback icon. Key workflows now have their own visual identity, and Founders Finder, Employee & Talent Finder, and Trustpilot Reviews Scraper appear first in the source-template catalog.
The release also adds Analyze customer reviews, a ready-made OpenAI/ChatGPT template that turns a review and rating into a concise summary, sentiment, main topic, issue type, urgency, recommended action, and a Needs Review flag. For example, a mixed three-star review can be routed to manual review instead of being forced into a misleading positive or negative label.
No duplicate rows when Instagram scraping resumes
Long Instagram Followers/Following Scraper runs can span many pages and may need to retry or resume. When two pages overlap, the same Instagram user could previously be added more than once. Datablist now remembers the user IDs already accepted for that source run and filters repeats across pages and resumes.
If a 5,000-follower import stops at page 30 and you resume it later, followers already collected are not appended again. Duplicate-only pages still advance to the next page, the limit counts unique profiles, and usage for profile rows is based on the unique records returned.
One difficult company name no longer stops a domain search batch
Find Company domains from Company names now isolates invalid inputs and temporary search failures to the affected rows. Previously, a punctuation-only company name or one failed candidate query could interrupt useful work elsewhere in the same batch.
For example, a list containing Acme, ., and !? now marks the punctuation-only rows as empty input at no cost and continues processing Acme. If one country-specific candidate search fails, other country groups still run; a row with no verified domain returns a normal no-result outcome instead of crashing the batch.
See our guide to finding company websites from names for preparing company-name inputs.