How to Export Meta Ad Library Data in 2026

Trying to export Meta Ad Library data is the moment most practitioners realise the tool is built for casual browsing, not serious research. You can search ads all day, but the moment you want that data in a spreadsheet, a database, or a BI dashboard, the interface offers you nothing. No download button. No CSV. No API key. Just a screen you can screenshot.

This is a real problem. If your job is to track competitor creative at scale — mapping what formats they're running, when spend peaks, which offers keep appearing — you need structured data, not browser tabs. And you need it flowing into the tools your team already uses: Airtable, Notion, Google Sheets, Looker, whatever your stack is.

This guide covers every real method to export Meta Ad Library data in 2026, what each one actually costs in time and money, and which one works without a 6-week bureaucratic detour.

TL;DR: Meta has no native export. Your three options are: (1) the official Marketing API, which takes 6–8 weeks of app review; (2) browser scraping, which is fragile and ToS-adjacent; (3) third-party tools like AdLibrary that already have API access and surface clean CSV + API export without the approval queue. For most practitioners, option 3 is the only one that ships today.

Why Exporting Meta Ad Library Data Is Harder Than It Should Be

Meta's Ad Library was built under regulatory pressure — specifically the EU Digital Services Act, which mandates transparency about political and commercial advertising. The public-facing website satisfies that obligation. An export function does not exist because it was never in scope for the compliance goal.

For researchers and advertisers who want structured data, Meta provides the Ad Library API via the Marketing API. But access is gated behind Business Verification and App Review — a process that takes 6–8 weeks even when you do everything right. Many smaller teams and freelancers do not meet the business verification threshold at all.

The practical result: the data is technically public, but extraction requires either significant compliance overhead or creative workarounds. Understanding which workarounds are stable — and which will break on a Tuesday morning — is what this guide is about.

For context on what the Meta Ad Library actually contains and how to use it for competitor ad research strategy, those posts cover the research side. This guide is about the data pipeline.

What Fields Are in a Meta Ad Library Export?

Before choosing a method, it helps to know what data you're actually trying to extract. A well-structured Meta Ad Library export dataset contains:

In a sample of in-market DTC ads we pulled from adlibrary across Meta placements, over 60% of active advertisers reuse the same creative hook across 3+ ad variations — something only visible when you can sort and filter a structured dataset, not when you're browsing a web UI.

For a full breakdown of the dynamic creative patterns that show up in bulk exports, the glossary entry is worth reading before you build your export schema.

Method 1: Meta Marketing API (The Official Route)

The Meta Marketing API includes an Ad Archive endpoint that lets you query public ad data programmatically. This is the sanctioned, stable, and future-proof method. It is also the most time-consuming to access.

What's required

• A Facebook Developer account
• A registered app (App Type: Business)
• Business Verification for your company
• App Review approval for the ads_read permission and Ad Library API access

The timeline

Business Verification takes 1–2 weeks if your documents are in order. App Review for Ad Library access is separate and typically adds another 4–6 weeks. Total: 6–8 weeks minimum, with no guarantee of approval. Meta can request additional documentation or reject without clear explanation.

What you can do once approved

A basic API call looks like this:

GET https://graph.facebook.com/v19.0/ads_archive?
  access_token={token}&
  ad_type=ALL&
  ad_reached_countries=['US']&
  search_terms='running shoes'&
  fields=id,ad_creative_body,ad_snapshot_url,spend,impressions

The API returns paginated JSON. You'd write a script to loop pages, extract fields, and write to CSV or push to a database.

What it doesn't give you

• Exact spend figures (ranges only)
• Creative assets directly (you get snapshot URLs that expire)
• Hook text parsed from creative (you get raw body text)
• Cross-platform data (Meta API only covers Meta properties)

For teams who need cross-platform ad intelligence — comparing Meta creative against TikTok or YouTube simultaneously — the Marketing API is structurally incomplete regardless of approval status.

Method 2: Browser Scraping (The Brittle Route)

Browser automation tools (Playwright, Puppeteer, Selenium) can navigate the Meta Ad Library, trigger searches, and extract rendered HTML. Some SaaS tools are built on top of this approach.

The appeal is obvious: no app review, no waiting, data available today.

Why it breaks

Meta actively defends against scraping. Common countermeasures include:

• CAPTCHA challenges triggered by non-human navigation patterns
• Session limits that cut off after N results
• CSS class name obfuscation that breaks selectors weekly
• IP-rate limiting for datacenter IPs
• Login walls that require cookies from an authenticated session

In practice, any scraper working today has a ~3–4 week lifespan before a Meta UI change or countermeasure breaks it. The maintenance burden is constant. If you're building a research workflow that needs to run reliably every week, scraping is not a foundation.

There's also a ToS dimension. Meta's platform policies prohibit automated access except via approved API. While enforcement against small-scale users is inconsistent, it's a real consideration for agencies and brands that value their Meta Business account standing.

For background on why Meta ad library scraping tools exist despite these limitations — and what the category looks like — that post has a full breakdown.

Method 3: Third-Party Tools with Existing API Access

This is the category that resolves the core tension: you want structured, exportable ad data today, without the 6–8 week approval queue, and without brittle scraper maintenance.

Several platforms have already gone through the Meta API approval process, maintain ongoing compliance, and expose that data through their own cleaner interface — with CSV download and API access built in.

How this category works

The provider holds the approved API access. You authenticate with the provider. The provider's database is already populated with crawled and structured ad data across platforms. You query the provider's API or use their UI to filter and export.

For a full comparison of options in this space, the ad-library alternative landing page covers the category. The key differentiators to evaluate:

• Platform coverage: Meta only, or multi-platform?
• Export formats: CSV only, or API with structured JSON?
• Data freshness: How often is the database updated?
• Spend data: Ranges only, or enriched estimates?
• App review required: Does the user need to do their own app review, or does the provider handle it?

How AdLibrary's Export Workflow Works

AdLibrary (ad-library alternative with API access) takes the third-party approach. It covers 7 networks — Facebook, Instagram, TikTok, LinkedIn, YouTube, Pinterest, Snapchat — and exposes all of that through a single REST API key. No app review on your end.

CSV Export (UI-based)

1. Run a search with your filters (advertiser, keyword, platform, date range, format)
2. Apply any secondary filters — spend range, active/inactive, format type
3. Click the Export button — CSV downloads immediately
4. The file includes: advertiser, creative URL, format, platform, run dates, spend range, impressions range, and any AI-enriched fields if you're on a plan that includes AI ad enrichment

This takes under 5 minutes from search to file. No code required.

API Export (Programmatic)

For teams who want to pipe data directly into Airtable, a data warehouse, or a BI tool, the API access feature is available on the Business plan (€329/mo).

A basic export call:

POST https://adlibrary.com/api/v1/search
Authorization: Basic {base64(email:password)}
Content-Type: application/json

{
  "query": "running shoes",
  "platforms": ["facebook", "instagram"],
  "dateRange": { "from": "2026-01-01", "to": "2026-05-01" },
  "formats": ["video", "image"],
  "limit": 100
}

The response is structured JSON with all export fields. You loop pages, accumulate records, and push to wherever your stack needs them. One credit per result — credits reset monthly on the Business plan.

For a worked example of how this fits into a media buyer daily workflow, the use case page has a step-by-step template.

Building Your Export Pipeline: Step-by-Step

Here's a concrete workflow for getting Meta ad library data into Airtable. The same pattern applies to Notion, BigQuery, or any destination with an API.

1. Define your target advertisers. List the 10–20 competitors or category players you want to track. Pull their Facebook Page IDs or use name search.
2. Set your field schema. Decide which export fields map to which columns in your destination. At minimum: advertiser, creative URL, format, start date, spend range low, spend range high, platform.
3. Run a baseline pull. Export the last 90 days of ads for each advertiser. This becomes your historical baseline.
4. Schedule weekly deltas. Use the API with a dateRange.from set to 7 days ago. This captures new ads without re-pulling the full history.
5. Enrich with AI fields. If you're using the AI ad enrichment feature, the API response includes parsed hook text, offer type, and creative angle — pre-structured for database insertion.
6. Flag changes. Add a formula column in Airtable that highlights ads that appeared in the last 7 days versus ads that have been running 30+ days. Long-running ads are signals — they're likely profitable.
7. Connect to your BI layer. If you're on a data warehouse setup, push the Airtable data to BigQuery or Redshift via Airbyte or a simple cron script. The ad timeline analysis feature in AdLibrary's UI can supplement this with visualised run-time data.

For tracking creative decay and when competitors start rotating out ads, the creative fatigue calculator is a useful companion to the raw export data.

Comparing the Three Export Methods

For teams doing competitor ad research at any meaningful frequency, the time-to-first-data gap between the official API and a third-party tool is the deciding factor. Waiting 6–8 weeks to test a research workflow is not a viable option for most teams.

For a broader comparison of what's available in the ad intelligence category, the competitor research tools comparison post covers the full landscape including SEO and market signal tools.

What About Cross-Platform Export?

Most discussions of exporting ad library data focus exclusively on Meta, but the same job applies to TikTok, LinkedIn, YouTube, and Pinterest. Your competitors are advertising everywhere, and a Meta-only export gives you a partial picture.

Meta's Marketing API doesn't help here. It only covers Meta properties. TikTok's Creative Center has its own API with different authentication requirements. LinkedIn's ad transparency data is accessible via the LinkedIn Ad Library but also has no direct export. Google's Ad Transparency Center offers some lookup functionality but no bulk export.

Managing separate API approvals for each platform — and building separate ETL pipelines for each data format — is a significant engineering investment. For most teams, a single unified source that already handles cross-platform normalisation is the practical answer. See the ad library alternative for TikTok ads and ad library alternative for LinkedIn ads pages for platform-specific context.

For ad spy tool comparisons that include cross-platform coverage, that post covers which tools cover which networks.

Data Freshness and Schema Stability

One concern that often comes up when building a data pipeline on top of any export source: will the schema change and break your pipeline?

With the Meta Marketing API, schema changes are versioned — Meta releases new API versions and deprecates old ones on a defined schedule, with migration guides. Stable, but slow to absorb new ad formats.

With scraping tools, schema is tied to Meta's HTML structure. Any UI change breaks the parser. Expect 2–4 pipeline breaks per year.

With AdLibrary's API, the schema follows the platform's versioned endpoint. Field additions are backward-compatible; removals are announced. The saved ads feature also lets you pin specific ads to a permanent record, so even if an ad expires from the live database, your saved version retains the full structured record.

For teams building competitor ad research workflows that run automatically, schema stability is as important as data quality. An export that breaks silently is worse than one that doesn't exist.

Frequently Asked Questions

Can you export Meta Ad Library data directly from the website?

No. Meta's Ad Library website has no native export or download button. You can only view ads on screen. To get structured data out, you need either the Marketing API (requires app review), a browser scraping tool, or a third-party service like AdLibrary that already has API access and provides CSV and API export.

What fields are included in a Meta Ad Library export?

A complete export typically includes: advertiser name, ad creative URL, ad format (image/video/carousel/collection), platforms (Facebook/Instagram), start date, end date or active status, spend range (low/high estimate), impressions range, geographic targeting, and demographic targeting (age, gender). Third-party tools may add enriched fields like hook text, CTA, and creative classification.

How long does it take to get access to the Meta Marketing API for ad library data?

The Meta Marketing API requires both Business Verification and App Review. Business Verification alone takes 1–2 weeks. The App Review process for Ad Library API access adds another 4–6 weeks. Total time from application to approved access is typically 6–8 weeks, and approval is not guaranteed.

Is scraping the Meta Ad Library against the Terms of Service?

Automated scraping of the Meta Ad Library website violates Meta's Terms of Service. Meta actively blocks scrapers with CAPTCHAs, rate limiting, and IP blocks. Additionally, the EU Digital Services Act requires Meta to provide structured data access via the API, which is the sanctioned route for researchers and businesses.

What is the best way to export Meta ad library data into Airtable or Notion?

The most reliable workflow is: (1) use AdLibrary's REST API or CSV export to pull structured ad data, (2) map the fields (advertiser, creative URL, format, run dates, spend range) to your Airtable base or Notion database, (3) schedule recurring pulls via the API to keep your database fresh. This avoids the 6–8 week Marketing API review and the fragility of scraping.

Conclusion

The gap between "Meta has a public ad library" and "I can export that data into my tools" is not a technical problem — it's a bureaucratic and architectural one that Meta built intentionally. The three methods differ not in capability but in who absorbs the friction: you (Marketing API review queue), your engineering team (scraper maintenance), or a provider that already absorbed it. If your job is to get competitor ad data into Airtable today and build a research system that runs every week without breaking, the right choice for most practitioners is the one that ships the same afternoon you decide to try it. Start with the Business plan on AdLibrary if you need API access for automated pipelines, or the Pro plan at €179/mo if CSV export and manual research is the primary workflow.