Receive leads from Meta Lead Ads

This article shows how to connect a Facebook account and route leads from your Instant Forms on Facebook and Instagram into a Datahubb campaign. Nobody has to build a post integration, because Datahubb collects the leads from Meta directly.

Once a form is connected, its leads run through the normal pipeline: fields, filters, duplicate checks, integrations, and distribution to your buyers.

Prerequisites

• The Meta Lead Ads feature enabled on your workspace. If the provider is not in your integrations list, ask your admin.
• A Facebook account with admin access to the Page that owns the form
• A campaign ready to receive the leads, and a supplier on that campaign

Connect an account and bind a form

1. Open Integrations from the sidebar and open Meta Lead Ads.
2. On the Connection tab, click Connect Facebook.
3. Complete the login popup and grant every permission it asks for. Missing permissions are the most common cause of an empty forms list later.
4. Pick a Page, then one of its Instant Forms.
5. Choose the campaign, the supplier whose campaign should receive these leads, and, for internal suppliers only, a traffic source.
6. Click Save. The form appears under Connected and leads start routing.

The connection lives on the server, not in your browser. Any admin can add more forms to a granted Page later without signing in to Facebook again.

Map the form to your campaign fields

1. On the connected form's row, open Field mapping.
2. Pair each form question with the campaign field it should fill.
3. Set a fixed fallback value for any field the form does not ask for. A real answer from the form always wins, and the fallback only fills a gap.
4. Read the coverage banner. It names any required campaign field with no source, which is exactly what would reject the lead at ingest.
5. Save.

Fields satisfied elsewhere are not flagged. The supplier's payload defaults count, and the visitor's IP address and user agent are added automatically.

You can also set a global default mapping on the Global Defaults tab, and override it for one campaign from that campaign's Integrations tab. A per-form mapping wins over both, which is how two forms on one campaign can map differently.

Manage a connected form

The Connected, Paused and Archived filters group your forms, and each row carries its own controls.

Each row also shows how many leads it received in total and in the last seven days, how many were accepted and rejected, and when the last one arrived.

To stop all Meta intake at once, deactivate the Meta Lead Ads integration itself. Both the live webhook and the recovery sweep check that switch before ingesting.

Missed leads

Meta does not always deliver its notification, and it never re-sends one it dropped. A scheduled sweep closes that gap by asking Meta what leads each active form has and pulling in anything not already taken. Nothing is ever ingested twice, and the sweep is bounded by Meta's own 90-day lead retention.

If you resume a paused form and opt into the catch-up, the same bound applies. Catch-up is off by default, because lead buyers reject stale data.

Expected result

A test submission on the Instant Form appears in Leads within seconds, mapped to your campaign fields. Its timeline carries an intake event naming the form, the Page, and Meta's own lead id so you can cross-reference it in Meta's Lead Center.

Troubleshooting

• The Page's forms list is empty or errors. The token is missing the ads management permission. Reconnect and grant every permission.
• A Business Manager Page does not appear. Business management permission was not granted. It is needed for Pages administered through Meta Business Manager.
• A lead never arrived. Meta dropped the notification. The recovery sweep picks it up shortly. Confirm the form and the supplier are both active.
• The form is already routed somewhere else. Datahubb asks before re-routing rather than silently taking the form from another campaign. Confirm the prompt to move it.
• Leads arrive but get rejected. Open Field mapping and read the coverage banner, then check the lead timeline for the rejecting field.
• Deactivating the integration did not stop leads. Also check whether the form itself is paused or archived, and whether the supplier is active.
• Reconnecting flooded in old leads. The catch-up option was ticked. It is off by default.