Lead-Delivery Reconciliation And Failover For Meta Lead Ads, After One Meta API Hiccup Silently Broke Make And Zapier Pipelines At Once
On 2026-05-13 a Meta-side API failure simultaneously broke Facebook Lead Ads ingestion for at least 19 distinct users across Make and Zapier community threads, including an agency with 40+ live automations. Paid leads stopped flowing, users found out only from error-email floods, and platform guidance was to wait for automatic replay with no way to confirm which leads were lost. Agencies want delivery verification against what Meta actually collected, not just another bridge on the same fragile API.
Everyone builds bridges, nobody builds the audit. Poll the Graph API leads endpoint on a schedule, reconcile lead IDs against CRM arrivals, alert on gaps, and replay what is missing. It is boring, it sells to agencies on retainer who eat the blame when leads vanish, and it survives Meta breaking webhooks because detection is the product.
landscape (1 existing solutions)
Every option, native Make and Zapier integrations and dedicated bridges alike, is a forwarding pipe on the same Meta API, so when Meta breaks they all break together and silently. In the May 13 threads users compared notes on which pipe still worked (one reported Pabbly running while Make failed), which is exactly the multi-path failover and loss-detection behavior no product currently packages.