What leads_retrieval Is

Facebook Lead Ads store form submissions (name, email, phone, custom answers) inside Meta's systems. The leads_retrieval permission grants API access to read those submissions for Pages the user manages — either by polling or, in production-quality integrations, in real time via the leadgen webhook.

Standard Access only works with your own test Pages and forms. Serving real advertisers requires Advanced Access through Meta App Review, and usually a verified business behind the app.

Who Actually Needs It

• CRM platforms and CRM connectors that sync Facebook leads into pipelines automatically
• Marketing automation SaaS that triggers email/SMS follow-up the moment a lead form is submitted
• Agencies with client dashboards that collect leads across many client ad accounts and Pages
• Lead distribution tools that route form submissions to sales teams, franchises, or dealers

Speed is the whole value: a lead contacted within minutes converts far better than one exported manually the next day — which is why real-time retrieval, not CSV export, is what businesses pay for.

What Approval Requires

• A working lead-sync feature — reviewers expect to see a real lead travel from a test form into your app
• The leadgen webhook configured and receiving events (polling-only demos read as incomplete integrations)
• A screencast showing the user connecting their Page, granting the permission, and the lead appearing in your interface
• A use-case description that states what lead fields you access, where they are stored, and who can see them
• A privacy policy that covers lead data handling and retention — checked strictly for this permission
• Meta Business Verification completed on the Business Manager behind the app
• Related permissions scoped correctly — lead retrieval typically rides with pages_show_list and pages_manage_ads or pages_read_engagement, each needing its own justification

Why leads_retrieval Gets Rejected

As with most Meta rejections, the product is usually fine — the submission simply fails to prove compliant data handling in the format reviewers require. A full breakdown of failure patterns is in the Meta App Review rejection reasons guide.

Where This Fits in the Bigger Approval

leads_retrieval is reviewed inside the standard Meta App Review flow, so everything that applies to Facebook permissions applies here: separate justification per permission, screencast quality, policy alignment, and verification status. If you want the submission prepared end to end — scoping, screencast scripting, use-case writing, webhook checks, and resubmission handling — that is what the Facebook App Review service covers.