Competitor Ad Change Monitor (Meta Ad Library)
Pricing
$200.00 / 1,000 advertiser monitoreds
Go to Apify Store
Competitor Ad Change Monitor (Meta Ad Library)
Pricing
$200.00 / 1,000 advertiser monitoreds
Competitor brand names, keywords, Facebook Page URLs, or numeric Page IDs to monitor in the Meta Ad Library. Examples: 'Nike', 'Allbirds', 'https://www.facebook.com/Nike', '15087023444'. Each run fetches each advertiser's current ads and diffs them against the last run.
2-letter ISO country code for the Ad Library search (US, GB, DE, FR, CA, AU, ...). Ad Library results are country-specific, so keep this stable across runs for the same monitor.
Hard cap on how many current ads to pull per advertiser each run. Keeps compute predictable and the diff fast. 20-50 is plenty for change monitoring.
'Active' tracks currently-running ads (recommended for launch/kill alerts). 'All' also includes stopped ads.
Optional stable identifier for this monitor's saved snapshot. Leave blank to auto-derive a key from the advertiser set + region. Set it explicitly if you want several scheduled monitors that each keep their own history.
How long to wait for the underlying Meta Ad Library actor run per advertiser before moving on. 120-200 is typical.
Optional. Connect your Notion workspace and the change report is also written as a Notion page in the same run — the Actor never sees your Notion credentials. Authorize a Notion MCP connector in Apify Console -> Settings -> API & Integrations, then select it here.
Optional. The Notion page ID to create the change-report page under. If blank, Notion creates a private page at workspace root.
Optional. Connect your own Supabase project and the results are also inserted into a table in the same run — the Actor never sees your Supabase credentials. Authorize a write-scoped, project-scoped Supabase MCP connector in Apify Console (Settings -> Integrations), then select it here.
Target table in the public schema (created if missing, with id, a jsonb data column, and a scraped_at timestamp). Default: nexgendata_leads.
Your Supabase project reference (e.g. abcdefghijklmnop). Required unless your connector URL is already project-scoped. Find it in your project URL: supabase.com/dashboard/project/THIS_PART.
When on (default), records already delivered in a previous run are not delivered again to the same destination — so scheduled runs only push new items. Turn off to deliver every record on every run.
Optional. Connect your Slack workspace and get a message for each new change (first 5) plus a summary, every run. Authorize a Slack MCP connector in Apify Console (Settings -> Integrations) using your own Slack OAuth app, then select it here. The Actor never sees your Slack token.
