Meta Ad Library Ads Scraper
Pricing
Pay per usage
Meta Ad Library Ads Scraper
Fetch active Meta Ad Library ads for a Facebook page ID through Meta Ad Library GraphQL pagination.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Adside
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
1
Monthly active users
3 hours ago
Last modified
Categories
Share
Fetch active Meta Ad Library ads for a known Facebook page ID using the public Meta Ad Library GraphQL pagination endpoint.
This actor is intended as a faster internal replacement for the list-ads part
of apify/facebook-ads-scraper in Adside's Competitive Intelligence flow. It
does not fetch per-ad detail modal data in v1. It returns the ad list fields our
current product uses: creative text, CTA, landing URL, media URLs, platforms,
dates, page name, page categories, page likes, and collation count.
Input
{"page_id": "434174436675167","limit": 50,"country": "ALL","active_status": "active","batch_size": 30,"use_proxy": true,"proxy_groups": ["RESIDENTIAL"],"request_timeout_ms": 8000,"max_retries": 10}
Output
Dataset rows intentionally mirror the raw shape consumed by
metaAdsLibraryService.slimAd() in the web app, including camelCase snapshot
fields such as snapshot.displayFormat, snapshot.linkUrl,
snapshot.images[].originalImageUrl, and top-level fields like
adArchiveID, publisherPlatform, startDate, and endDate.
Notes
The actor uses impit for browser-impersonated direct HTTP requests and does
not launch a browser.
On Apify cloud, Meta rate-limits the standard Apify proxy pool for this
GraphQL endpoint. RESIDENTIAL is therefore the default proxy group. For
country-specific runs such as US, FR, or IN, the actor also asks Apify
Proxy for the same country.
Each GraphQL page uses a short request timeout and retries with a fresh proxy session. This avoids spending 30 seconds on a slow residential proxy.