What problem does it solve?
Cold email personalization requires knowing what a prospect is actively advertising, but the Meta Ad Library is keyed to Facebook Pages while lead lists are keyed to company domains, and naive lookups return the wrong company's page or fabricated ad claims.
Core Features & Use Cases
- Verified page discovery chain: Resolves a bare domain to a verified Facebook Page via website HTML scraping, gated SERP search, and a rendering proxy, with three anti-false-positive gates.
- Metered ad fetching with cost controls: Calls the Apify facebook-ads-scraper with onlyTotal billing, a 45-day domain cache, and dedup to prevent per-ad billing surprises.
- Guarded line writer: Produces a lowercase ad_library_line merge field using a locked prompt, deterministic lint guards, an ungrounded-words check, and a mandatory truth judge on 100% of rows.
- Use Case: Given a lead list of ecommerce brands, generate a "Noticed {{ad_library_line}}." opener for each row, abstaining safely when no verified page or usable ad exists.
Quick Start
Give the skill a list of company domains and names and ask it to generate the ad_library_line personalization line for each row using the Meta Ad Library chain.