On this page
The Facebook Lead Ads integration delivers every submission from your Facebook and Instagram lead forms into the VGraple CRM Leads board within about a minute, matched to a contact, routed to the right pipeline and followed up on WhatsApp by a sequence or automation rule. It is native: VGraple CRM subscribes your Page to Meta's leadgen webhook through the same OAuth connection used for Messenger and Instagram.
What syncs
| Data | Direction | Timing |
|---|---|---|
| New lead form submissions with every field, the form name, campaign, ad set and ad IDs | Meta to VGraple CRM | Within about a minute, by webhook |
| Historical submissions | Meta to VGraple CRM | On demand with Sync past leads |
| Lead record, contact match or creation, source and consent | Inside VGraple CRM | Immediate on arrival |
| Sequence enrolment, assignment and pipeline placement | Inside VGraple CRM | Immediate, per campaign mapping |
| Page token health and reconnect notices | Meta to VGraple CRM | Continuous |
Setup
- Go to Settings, then Channels, and connect your Facebook Page with Connect via Facebook (the same flow as Messenger and Instagram).
- Go to Settings, then Integrations, find the Facebook Lead Ads card and enable Lead Ads for the Page. This subscribes the Page to Meta's leadgen webhook field.
- Under Leads settings, map campaigns to pipelines, a default agent and a sequence if you run more than one campaign or product.
- Submit a test lead with Meta's test tool (or wait for a real one) and confirm it appears on the Leads board tagged with the campaign and form name.
- Click Sync past leads to backfill submissions from before the connection.
- If a Page token expires, the Leads settings page shows a reconnect notice; reconnect from Channels and the flow resumes.
What a lead looks like when it arrives
A Lead Ads submission becomes a lead card with the campaign, ad set, ad and form names, every form answer as a field (standard fields mapped to name, email and phone; custom questions stored as form data and, where mapped, as custom fields), the source set to Facebook Lead Ads, and consent recorded from the form's consent question if you added one. The contact is created or matched by phone, and if a WhatsApp conversation already exists it is linked, so the salesperson sees prior history before calling.
Three recipes
- Lead Ad for a coaching batch -> lead in the JEE pipeline, counsellor assigned, WhatsApp intro template within a minute. The campaign mapping routes it; the sequence sends a utility introduction with a Book button and pauses when the parent replies.
- Real estate Lead Ad -> qualifier flow on WhatsApp, site visit slots offered. The lead's first WhatsApp reply triggers the qualifier; answers feed lead scoring; the salesperson calls a scored lead.
- Lead with no WhatsApp reply in 3 days -> second utility touch, then a marketing offer with consent. The sequence handles the cadence; a reply or STOP stops it.
Reporting
Source reports show leads, conversations, bookings and revenue per campaign and per form.
Limits and gotchas
- Meta delivers leads only for Pages where Lead Ads is enabled; the toggle is per Page.
- Consent for WhatsApp marketing must be part of the form (a checkbox or a clearly worded question); a lead form submission on its own is consent for follow-up about the enquiry, not for offers.
- Phone fields with unusual custom wording can be missed by automatic detection; the raw answers are stored and the number can be corrected on the lead.
- Sync past leads reads what Meta retains (about 90 days of form data on Meta's side).
- A WhatsApp message to a number that has never messaged you must be a template; sequences handle that automatically.
The Lead Ads guide covers settings and troubleshooting; the Lead Ads feature page shows the end-to-end funnel.