Meta Ads Library Competitor Monitor

Track competitor ads from Meta Ads Library across Facebook, Instagram, Messenger and Audience Network.

What it does

• Searches Meta Ads Library by brand, domain, keyword, or numeric Facebook page ID.
• Handles Meta's lightweight rd_challenge verification flow with a cookie jar.
• Extracts server-rendered ad results from Meta's prefetched Relay JSON.
• Uses Meta Relay GraphQL pagination for additional result pages when maxAdsPerQuery exceeds the initial payload.
• Returns clean competitor-intelligence records plus optional summary rows.

Output includes

• advertiser/page name and page ID
• ad archive ID and source URL
• active status, start/end dates
• platforms and countries
• ad copy, CTA, caption, landing page
• image/video creative URLs when available
• spend/impression/reach metadata when Meta exposes it

Notes

Meta can change or harden Ads Library at any time. This Actor detects blocking and returns blockedByMeta: true summary rows instead of silently failing.

Pagination

The first Meta page usually contains about 30 ads. For larger exports, set maxAdsPerQuery and maxPagesPerQuery; the Actor follows Meta's Relay cursor pagination and records pagesFetched plus hasMoreResults in the summary row.

Logged-out Meta pagination currently tends to return smaller follow-up pages than the initial SSR payload, so very high limits may require raising maxPagesPerQuery. If Meta hardens the GraphQL route, the Actor reports the pagination error in the summary row rather than silently truncating.