Meta Lead Ads
Auto-call Facebook and Instagram leads the moment they submit, and feed call outcomes back to Meta to sharpen ad targeting.
Connect a Facebook Page and Talkif places an AI phone call to every Lead Ads submission within seconds — running the flow you choose, from the caller ID you choose. As each call plays out, Talkif reports funnel-stage events back to Meta's Conversions API so Meta can optimize ad delivery toward leads that actually convert on the phone.
Configure it in the dashboard under Developer → Integrations.
Before you start, you need a published flow to run the calls, an active phone number to use as caller ID, and a Facebook Page you manage. To send conversion feedback, you also need a Meta dataset (pixel) ID from Events Manager.
Connect a Facebook Page
- In Developer → Integrations, start the Meta connection. You'll be redirected to Facebook to authorize Talkif.
- After authorizing, pick which Page to connect. Talkif subscribes that Page's
leadgenwebhook so new leads are delivered automatically. - Optionally provide a dataset (pixel) ID to enable Conversions API feedback. You can add or change this later.
One account can connect multiple Pages. Access tokens are encrypted at rest and never leave the backend; lead webhooks are signature-verified.
Map lead forms to flows
A connected Page does nothing until you map its lead forms. Each mapping ties one Meta lead form to the flow, caller ID, and calling behavior used for leads from that form.
| Setting | Default | Range | Description |
|---|---|---|---|
| Flow | — | — | The published flow run when calling these leads. |
| Caller ID | — | — | The active phone number the call is placed from. |
| Enabled | On | — | Whether new leads from this form trigger calls. |
| Call delay | 0s | 0–86400s | How long to wait after a lead arrives before calling. |
| Max attempts | 1 | 1–10 | Call attempts per lead, retrying on no-answer. |
| Retry delay | 30 min | 1–1440 min | Wait between retry attempts. |
Leads from a form with no mapping are recorded but not called.
What happens when a lead comes in
- The lead submits your Facebook or Instagram Lead Ad. Meta delivers a
leadgenwebhook to Talkif. - Talkif fetches the full lead, then creates or matches a contact from its fields.
- If the form is mapped and enabled, Talkif places the call with the mapped flow and caller ID, honoring the call delay and retry settings.
- Call and post-call analysis outcomes advance the lead through your funnel and are reported back to Meta.
You can review every ingested lead and its status in the dashboard.
Conversion feedback (Conversions API)
When a dataset is configured, Talkif sends a funnel-stage event to Meta's Conversions API each time a lead advances. This is what lets Meta's "Conversion Leads" optimization learn which ads produce leads that convert on the phone — not just leads that submit a form.
| Stage | Sent when | Default event name |
|---|---|---|
| Lead received | The lead is ingested and a contact is created | lead_received |
| Contacted | A person answers and the call completes | contacted |
| Qualified | Post-call analysis marks the lead qualified | qualified |
| Converted | Post-call analysis marks a conversion | converted |
Post-call analysis outcomes map to stages. By default:
| Analysis outcome | Advances to |
|---|---|
lead_qualified | Qualified |
appointment_set | Converted |
sale_completed | Converted |
Customizing the mapping
Both mappings are configurable per integration:
- Event names — rename a stage's event (for example, send Qualified as
sales_qualified) so it matches the events you defined in Meta Events Manager. Set an event name to empty to stop sending that stage. - Outcomes — remap which post-call analysis outcomes advance a lead to which stage.
Dataset and token settings
| Setting | Description |
|---|---|
| Dataset (pixel) ID | The Events Manager dataset that receives the events. Clearing it disables feedback. |
| CAPI access token | A dataset-scoped Conversions API token. Preferred over the connection's user token because dataset tokens don't expire. Stored encrypted; never returned. |
| Test event code | An Events Manager Test Events code. While set, events route to the Test Events tab so you can verify the setup before going live. |
| CRM name | The source name shown in Events Manager for these events. Defaults to Talkif. |
Events are deduplicated by lead and stage, so a retried or re-reported stage is never double-counted in Meta.