When someone fills in one of your Meta lead forms, PromoPilot files them as a contact (and an opportunity, when the brand has a default pipeline) and tells everyone who can see the brand's contacts: a notification in PromoPilot and an email with their name, email, phone, the form and ad they came from, and their answers. The link opens the contact in the right brand. Each lead alerts once.
Who hears about new leads
Choose under Ads > Lead forms > Lead alerts: In PromoPilot and by email, In PromoPilot only, or Off. Leads still land in your contacts when alerts are off, and the email follows each person's own email notification setting. While alerts are on they replace the pipeline's "New Lead" notice for Meta leads.
Send a test lead
Open a lead form and press Send a test lead (one a minute per form). Meta creates a lead with placeholder answers (one test lead per form, so an earlier one is replaced). PromoPilot gives Meta 10 seconds to deliver it, then files it either way and sends your alert, marked as a test. Lead events then shows whether Meta delivered it. Real leads only reach PromoPilot that way, so if it did not, use Sync from Meta on the Lead forms page and send another. Playbooks that start when a contact is created run for it too. Test leads never reach Meta's Conversions API.
When a lead gives the email of someone already in your contacts, the alert says so, and the phone number they typed is kept with their answers rather than replacing how you reach that contact.
From the API and the MCP server
POST /api/v1/ads/lead-forms/<id>/test-lead/ and the send_test_lead tool send a test lead and return its lead event. lead_alerts (all, in_app or off) is in /api/v1/ads/settings/ and the get_ads_settings and update_ads_settings tools. list_lead_events shows when the webhook delivered each lead, when it was alerted, and whether it was a test.
