Meta Ads Library Scraper

An Apify Actor that collects public advertisements from Meta Ads Library. It accepts existing Ads Library URLs, keyword searches, and advertiser Page IDs. Results are normalized into one record per ad and include the advertiser identity, ad copy, creative media, delivery status, destination, and change metadata available on the results page.

Features

• Search by URL, one keyword query per run, or advertiser Page ID
• Country, status, category, platform, media, and date filters
• Images and videos with optional file downloads
• Runs without login cookies; residential proxy support is optional for fuller coverage
• Anonymous Meta warm-up, headful stealth Chrome, and human-paced navigation
• Persistent firstSeenAt, lastSeenAt, and change detection
• Incremental onlyNewOrChanged runs for scheduled monitoring
• Automatic retries and persistent request queues
• JSON, JSONL, CSV, XML, Excel, and API output through Apify Dataset

Only information publicly displayed by Meta on the Ads Library results page is collected.

Use searchQuery for a keyword or phrase. The Actor accepts one search query per run to keep execution time predictable and reduce timeout risk. Run separate Actor tasks for separate queries.

Run locally

Install the Apify CLI and sign in if you want to use Apify Proxy locally:

npm install
npm run build
apify login
apify run

The example input runs without Apify Proxy. Add a residential proxy for larger or more reliable production runs.

Deploy

apify login
apify push

The Actor Console creates its input form from .actor/input_schema.json. The default runs without a proxy; production users can enable an Apify residential or external proxy from the same field.

Monitoring

Set a stable monitoringKey, enable onlyNewOrChanged, and schedule the Actor. Runs that use the same key share a named key-value store. Every ad is fingerprinted from its status, content, destination, and creatives. The Dataset then receives only new or changed ads.

Output

The default Dataset contains flat fields for convenient CSV/Excel exports and a media array for structured integrations. PROGRESS and OUTPUT records are written to the default key-value store during each run.

Notes

Meta changes Ads Library markup regularly. The extractor deliberately relies on visible labels, links, media dimensions, and Library IDs instead of generated CSS class names. Fixtures should be added whenever a changed Meta layout is encountered.