Routing Meta leads into Salesforce or HubSpot comes down to one question: does the integration keep Meta’s lead ID? Salesforce Lead Capture does, in a field called Lead ID that you map to a custom field. HubSpot Lead Sync does not, so you either add a webhook or partner integration, or you accept that stages can never be matched back to the ad that produced them.
The two native routes, side by side
| Salesforce Lead Capture | HubSpot Lead Sync | |
|---|---|---|
| Meta lead ID stored | yes, in the Lead ID field, which you map to a custom field | no |
| Delivery | automatic after you connect it in Business Suite | automatic after you connect it in Business Suite |
| Stage events back to Meta | possible, because the lead ID is there | needs a webhook or a partner integration, or Lifecycle Stage Sync on Professional and Enterprise |
| What to map before launch | lead ID, ad ID, form ID, tracking parameters | ad ID, form ID, tracking parameters, and an alternative match key for stages |
Everything else is the same on both sides. The connection is made once, it runs unattended, and it delivers whatever the CRM can map.
How to connect either CRM
- In Meta Business Suite, open All tools, then Instant forms.
- Select the CRM setup tab and search for your CRM.
- Click Connect from website and finish the steps on the CRM’s side.
Only admins of the Facebook Page who hold leads access can connect a CRM. If someone with full control of the business portfolio has customized leads access, the CRM must be assigned there before a single lead arrives. That is the permission that quietly disappears when a person changes role.
One detail saves an hour of searching later: an integration installed from the CRM’s own website cannot be edited or disconnected in Business Suite. You manage it on the CRM side, so when leads stop the fault is there.
Route on IDs, not on names
Routing rules compare fields. Every field your rules read has to survive the trip from Meta, so check the mapping before you write a single rule.
| Field | Why routing needs it |
|---|---|
| Lead ID | the match key for stage events, and for de-duplicating a lead that arrives twice |
| Ad, ad set and campaign IDs | assigns the lead to the right offer, client or territory |
| Form ID | one form can serve many ads, so it separates offers that share an audience |
| Tracking parameters | fixed labels set per form, such as a client name or an offer code |
is_organic and platform | separates paid from organic, Facebook from Instagram |
Store the IDs as text. A numeric field drops leading digits or turns a 17-digit lead ID into a rounded value, and every stage event then matches nothing.
Ad fields come out blank for organic leads, for ad preview submissions, and for anyone without advertiser privileges on the ad account. A rule of the form “if ad ID equals X, assign to Y” sends those records to the fallback or to nobody, so give the fallback a real owner.
Leads stay downloadable in Meta for 90 days from submission. A route that works only through manual export is a route that loses whatever nobody notices in time, which is why the comparison of all six delivery methods in Facebook lead ads CRM integration is worth reading before you pick one.
When the native integration is not enough
Two situations send agencies to a webhook: many client Pages with per-client routing, and a CRM whose integration drops the lead ID.
The flow is short. Meta posts a notification to your endpoint when a form is submitted, carrying the lead identifier, the ad ID, the form ID and the Page ID. Meta says these pings can arrive with a delay of up to a few minutes. Your endpoint then fetches the lead’s answers with a Graph API read and routes them wherever you decide.
The cost is real: a Meta app, App Review for the lead ads permission, Business Verification, an endpoint with a valid certificate, and a token whose owner has leads access. Meta files webhooks among the developer routes for exactly that reason.
A daily bulk read is a cheap companion. Call the form or the ad with a filter on time_created, compare the lead IDs with what you already stored, and the lead a webhook missed turns up the next morning.
Sending stages back so the routing holds
The route into the CRM is half the loop. The other half sends each lead’s progress back to Meta, and since April 2026 the qualified leads performance goal needs a Conversions API integration on new campaigns, with existing campaigns affected from August 2026.
The mechanics are the same for both CRMs, and the lead ID is what makes them work:
- Store Meta’s lead ID on every lead.
- Send an event per stage change, starting with the raw lead. Meta’s example: 100 leads that become 70 marketing qualified leads, 30 opportunities and 15 sales make 215 events, not 15.
- Keep
event_timeafter the lead was created and no more than 7 days before you send it. - Batch small. A batch holds up to 1,000 events and one error discards the whole batch.
- Upload at least daily, and send each status change rather than a snapshot of the latest one.
Validation needs at least seven days of data and at least two funnel stages, three if possible. Meta’s partner list for this includes HubSpot, Salesforce, LeadsBridge, Make, Stape, Zapier and Zoho, and a Google Sheets connection does it from a lead_status column. The step-by-step setup is in how to set up conversion leads optimization.
Without the lead ID, the stage events still arrive: Meta accepts a hashed email or phone number, or a click ID. The match rate drops, and the optimization learns from a smaller, vaguer sample than the one your CRM reports.
Rules that hold up across many clients
- Give the token to a shared system user, not to an individual.
- Write the fallback owner first, so an unmapped field never means an unassigned lead.
- Keep one form per offer, or a tracking parameter per offer, and route on it.
- Send one test lead per form before launch and confirm the IDs arrive.
- Check the counts weekly: Meta’s Results column against your CRM, with organic and test leads explaining small gaps.
- Log the hour the first call attempt happened, so a routing delay shows up as a routing delay and not as a bad creative.
The decisions behind the form and the follow-up are in all the questions on leads, CRMs and follow-up, and the goal that depends on the stage events is conversion leads. Once the IDs survive the trip, cost per lead per ad stops being an average: DropCPL keeps the ad and the landing page on every lead and syncs spend per ad from the Meta Ads API, so each CPL has a creative behind it.