Meta Ads Library Scraper - Facebook & Instagram Ads API

Search Meta Ad Library by keyword or Facebook page ID and export structured Facebook/Instagram ad data from the official Meta Graph API.

Use cases

• Track competitor Facebook and Instagram ads
• Monitor brand, political, and issue ad activity
• Build ad creative swipe files
• Collect ad copy, platforms, dates, countries, and snapshot URLs
• Schedule recurring paid-media monitoring through Apify API

Requirements

This Actor uses Meta's official Ad Library API. You need a valid Meta access token with access to the Ad Library API. Some fields are only available for political/social issue ads or EU/UK transparency data.

What you get

• Ad archive ID and snapshot URL
• Page name and page ID
• Creative body text, title, caption, and description
• Delivery start/stop dates
• Publisher platforms, including Facebook and Instagram when returned
• Reached countries
• Spend, impressions, and currency when Meta makes those fields available
• Raw API payload preserved for advanced workflows

Input example

{
  "accessToken": "YOUR_META_ACCESS_TOKEN",
  "searchTerms": ["nike", "crm software"],
  "countries": ["US"],
  "adType": "ALL",
  "activeStatus": "ALL",
  "maxAdsPerQuery": 100
}

Page ID example

{
  "accessToken": "YOUR_META_ACCESS_TOKEN",
  "pageIds": ["15087023444"],
  "countries": ["US", "GB"],
  "activeStatus": "ACTIVE",
  "maxAdsPerQuery": 200
}

Recommended saved tasks

• Competitor Facebook ads monitor
• Active Instagram ads tracker
• Political and issue ads research
• Brand ad creative swipe file
• SaaS competitor ad intelligence

Input reference

Field	Description
accessToken	Secret Meta access token with Ad Library API access
searchTerms	Keywords or advertiser terms
pageIds	Facebook Page IDs for advertiser-specific searches
countries	Countries reached by the ads
adType	All ads or political and issue ads
activeStatus	All, active, or inactive ads
maxAdsPerQuery	Maximum ads returned for each term or Page ID
dedupe	Remove duplicate archive IDs across queries

Output structure

Each row represents an ad returned by Meta and can include its archive ID, advertiser Page, creative text, delivery dates, publishing platforms, countries, snapshot URL, spend range, impression range, currency, and the original Graph API payload. Availability depends on ad type and transparency rules.

Run with the Apify API

curl -X POST \
  "https://api.apify.com/v2/acts/groupoject~meta-ads-library-monitor/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "accessToken":"YOUR_META_ACCESS_TOKEN",
    "searchTerms":["running shoes"],
    "countries":["US"],
    "activeStatus":"ACTIVE",
    "maxAdsPerQuery":100
  }'

Competitor ad monitoring workflow

1. Find the advertiser's Facebook Page ID or choose a stable brand keyword.
2. Select the countries and active status relevant to the campaign.
3. Save the configuration as an Apify task.
4. Schedule the task daily or weekly.
5. Connect the resulting dataset to a warehouse, spreadsheet, webhook, or creative-analysis workflow.

FAQ

Why is a Meta token required?

This Actor uses Meta's official Ad Library API. Meta controls access, permissions, rate limits, and the fields available to each token.

Does it return ad images and videos?

The dataset preserves creative and snapshot links returned by Meta. Direct media fields vary by API response and ad category.

Why are spend and impressions missing?

Meta exposes these transparency fields only for eligible ad categories and regions. The Actor does not invent unavailable values.

Is the token stored in output?

No. The input schema marks the token as secret, and it should never be included in datasets or logs.

Use the data in line with Meta's platform terms, applicable advertising rules, and privacy law.