# Changelog of 📢 LinkedIn Ads Library Scraper (`data_minds/linkedin-ads-library-scraper`) Actor

- **URL**: https://apify.com/data\_minds/linkedin-ads-library-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/data\_minds/linkedin-ads-library-scraper.md

## Changelog

### v1.0 — 2026-08-30

First release.

- LinkedIn Ad Library scraping from any search link — company, payer, keyword or fully filtered URL — with bulk paste, file upload and remote list support.
- Built-in search builder: company, payer, keyword, 249 countries, date range, sort order, impressions range and targeting categories, all as form fields instead of hand-written URLs.
- Complete ad record per result — advertiser, logo, company page, payer, headline, full untruncated ad copy, CTA button, landing page and the image/video/document creative URL for every ad format.
- Impressions intelligence: the published impressions band, a derived sortable numeric floor, the per-country percentage split and the top country.
- Targeting disclosure (language and location) plus exact run dates with a derived ACTIVE / INACTIVE status.
- Run-wide date and country overrides applied on top of every link and search in one place.
- `skipDetails` fast mode for broad, cheap first-pass sweeps.
- Automatic network fallback: no proxy → datacenter proxy → residential proxy (3 retries, sticky), with every route change written to the log.
- Enforced request pacing between request starts, so the actual request rate stays under control rather than just the parallelism.
- Nine live dataset views: Overview, Advertiser, Creative, Ad copy & CTA, Impressions, Targeting, Schedule, Source, Errors.
- Run summary written to the key-value store with per-run totals and the network route used.
- Accepts `startUrls` / `searchUrls` and `maxResults` / `maxItems` as input aliases, so inputs saved for other ad-library scrapers run here unchanged.
- Detects and corrects the ad library's custom-date-range rule: a range whose end date is today or later matches no ads at all, so a today/future end date is pulled back to yesterday and reported in the log instead of returning a silently empty run.
- Accepts an explicitly supplied `maxResults` / `maxItems` even though `resultsLimit` carries a schema default, so a ported input's limit is honoured rather than overridden.