Facebook Ads Library Scraper is a reusable BrowserAct template for collecting structured records from public Facebook Ads Library pages. Configure the run inputs, start the Bot, and receive consistent output for research, monitoring, enrichment, or downstream automation without writing selectors or scraper code.
What Does BrowserAct Facebook Ads Library Scraper Do?
The Bot starts from your configured inputs, opens the relevant public Facebook Ads Library page, loads the requested records, extracts the visible fields, and returns structured results. The default example uses Claude Code for Search Keyword, but the input can be changed before each run.
Key Features of Facebook Ads Library Scraper
- Configurable public-page inputs without rebuilding the Bot.
- Structured records returned in a consistent
resultsarray. - Public, non-login extraction path.
- Reusable runs for new keywords, URLs, locations, or limits.
- Output ready for review, export, API use, or automation.
What Data Can I Extract from Facebook Ads Library?
| Field | Description |
|---|---|
advertiser_name |
Publicly visible advertiser name value for the record, when available. |
advertiser_page_url |
Publicly visible advertiser page url value for the record, when available. |
ad_headline |
Publicly visible ad headline value for the record, when available. |
ad_description |
Publicly visible ad description value for the record, when available. |
started_running_date |
Publicly visible started running date value for the record, when available. |
ad_archive_url |
Publicly visible ad archive url value for the record, when available. |
image_urls |
Publicly visible image urls value for the record, when available. |
video_urls |
Publicly visible video urls value for the record, when available. |
platforms |
Publicly visible platforms value for the record, when available. |
active_status |
Publicly visible active status value for the record, when available. |
rank |
Record position in the collected result order. |
How to Use Facebook Ads Library Scraper
Quick Start Guide
- Click Run task.
- Keep the default inputs for a first test or enter your own public-page values.
- Click
Run. - Review the structured records after the run completes.
- Download the result or connect it to another workflow.
Input Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
Search Keyword |
Yes | Claude Code |
Controls the search keyword used for this run. |
Region |
Yes | United States |
Controls the region used for this run. |
Date Range |
Yes | past 30 days |
Controls the date range used for this run. |
Max Ad Count |
Yes | 10 |
Controls the max ad count used for this run. |
Example Output
{
"results": [
{
"advertiser_name": "Example value",
"advertiser_page_url": "https://example.com/public-record",
"ad_headline": "Example value",
"ad_description": "Example value",
"started_running_date": "Example value",
"ad_archive_url": "https://example.com/public-record",
"image_urls": [],
"video_urls": [],
"platforms": "Example value",
"active_status": "Example value",
"rank": 1
}
]
}
How Does it Work?
- Construct the public Meta Ads Library search from country, ad status, type, and keyword.
- Load ad cards until the requested Count is available.
- Read advertiser, creative text, dates, media, platforms, status, and archive URL from each card.
- Return normalized ad records in result order.
How to Build a New Scraper Bot with Agent Built
Step 1: Describe the data you need
Open BrowserAct and start Agent Built from the Home prompt box or from Create -> Build with Agent. Describe the public website, records, inputs, fields, and result limit.

Step 2: Let BrowserAct build and test the Bot
BrowserAct explores the live website, determines the navigation and extraction path, and validates the result. Reply in the same build conversation if the Agent requests a missing public URL, field, or expected output.

Step 3: Run the Bot and review the result
Run the completed Bot with default inputs. Check record count, source URLs, and required fields before reusing it with new inputs.


Why Use Facebook Ads Library Scraper?
- Replace repetitive copying from public Facebook Ads Library pages.
- Keep the same output structure across repeated runs.
- Send public records into research, reporting, enrichment, or monitoring workflows.
Who Can Use Facebook Ads Library Scraper?
- Researchers and analysts collecting public web data.
- Marketing, sales, and operations teams preparing structured datasets.
- Automation builders connecting BrowserAct output to other tools.
- Developers who need reusable browser-collected JSON records.
Automation and Export

BrowserAct returns structured records first. You can then use that output through API JSON responses, n8n workflows, Make scenarios, Zapier automations, MCP-based agent workflows configured from the Bot's Integrations tab, or manual spreadsheet export.
Need Help?
Contact us at
Discord: Discord Community
E-mail: service@browseract.com

