iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If Facebook Lead Ads aren’t showing in your CRM, first find out whether the lead exists in Meta. Then check access to the Page, lead records and CRM app; confirm the integration points to the right Page and form; and inspect its live trigger and reporting settings. A successful test alone does not prove that a live connection still has access or is switched on.
Start by locating the failure
“Facebook leads not showing in CRM” can describe several different problems: no lead was created, the CRM cannot access it, an integration trigger is misconfigured, or the lead synced but is absent from a particular report. Diagnose these layers in order instead of changing unrelated settings.
- Check for a lead record. Look in Meta’s lead records for the expected Page and form. If you are testing an integration, use its test or preview workflow and note the status or error details. Zapier recommends creating a sample lead with Meta’s Lead Ads testing tool; Salesforce documents checking test lead status and error codes. See Zapier’s trigger troubleshooting and Salesforce’s Lead Ads testing guidance.
- Check the access chain. Verify the connecting user’s access to the Facebook Page and, when required, the ad account. Then check whether the user and the CRM or connector app can access leads from that Page. If access is customized, permission for a human administrator may not automatically grant it to the app.
- Verify the Page and form. Confirm the connected Page is the one hosting the ad form, and that the integration trigger selects the intended form. If a form was edited or recreated, reselect it: Zapier says an updated form can have a new ID.
- Inspect the live connection. Check that the workflow is on, the account connection has not expired or lost permissions, and the trigger uses the correct connected account. If permissions changed, reconnect and select that reconnected account in the trigger.
- Only then investigate reporting. If the lead exists as a CRM record, compare the report’s attribution rules and the integration’s sync scope before treating the issue as failed delivery.
Menu names and available controls vary by CRM, Meta account configuration and product edition. Use the relevant provider’s current instructions for your setup.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Facebook Lead Ads not syncing: check the Page, user and app permissions
Several distinct permissions can affect delivery; having one does not establish that the others are in place.
#1 Best Overall
- THE ALTERNATIVE: The Office Suite Package is the perfect alternative to MS Office. It offers you word processing as well as spreadsheet analysis and the creation of presentations.
- LOTS OF EXTRAS:✓ 1,000 different fonts available to individually style your text documents and ✓ 20,000 clipart images
- EASY TO USE: The highly user-friendly interface will guarantee that you get off to a great start | Simply insert the included CD into your CD/DVD drive and install the Office program.
- ONE PROGRAM FOR EVERYTHING: Office Suite is the perfect computer accessory, offering a wide range of uses for university, work and school. ✓ Drawing program ✓ Database ✓ Formula editor ✓ Spreadsheet analysis ✓ Presentations
- FULL COMPATIBILITY: ✓ Compatible with Microsoft Office Word, Excel and PowerPoint ✓ Suitable for Windows 11, 10, 8, 7, Vista and XP (32 and 64-bit versions) ✓ Fast and easy installation ✓ Easy to navigate
- Page access: the account used to connect the integration needs the relevant access to the Facebook Page.
- Ad-account access: some integrations or ad-attributed lead workflows also require access to the ad account.
- Lead access: when lead access is customized, the relevant user and integration app may need explicit authorization for Page leads.
- CRM integration permissions: a CRM may require its own advertising or integration permission to be enabled.
When using Zapier
Zapier’s guidance distinguishes having Page or administrator permissions from granting the Zapier app access to leads. Check the Page’s lead access for the correct app entry; Zapier notes that “Zapier” and “Zapier Inc.” may appear as separate entries. If access was changed, reconnect Facebook, select the reconnected account in the trigger, and turn the Zap back on. Follow Zapier’s permissions guidance.
When using HubSpot
HubSpot’s troubleshooting guide lists Page and ad-account administrator access for the connected user, Business Manager ownership alignment, user Leads Access, Ads Publish permissions, enabled HubSpot Ads Integration permissions, and matching Page/form setup among the checks. Confirm lead syncing is enabled for each Page. HubSpot also says the Leads Access settings screen may be unavailable if the Business Manager has not enabled Leads Access Manager; according to its guide, the connected Facebook user then already has Leads Access. See HubSpot’s lead-sync troubleshooting guide.
Rank #2
When using Salesforce Lead Capture
Salesforce advises that the task creator needs Page administrator access and permission to download leads. Ad-attributed leads may also require ad-account access. If lead access is customized, check access for both the relevant person and Salesforce Lead Capture, and confirm the lead still exists in Meta’s lead download area. Salesforce’s guidance is in Common warning errors when leads fail to ingest and Lead Capture prerequisites and requirements.
Free tools Windows power users keep installed
One-click scans. No signup required.
Confirm the connected Page and form
A working CRM account can still be connected to the wrong Page or form. Match the Page used by the ad and form to the Page selected in the CRM integration, then check the selected form in the trigger.
Rank #3
- Pre-designed templates for both business and personal use
- 10,000 clipart images and 100 fonts
- Notes table for history and to-do items
- Sort, filter and index
- Calculation & totaling
For Zapier, a changed form may have a new ID, so an existing Zap can keep pointing at the old form. Reselect the current form in the trigger and use a sample submission if the test step needs a lead to detect. HubSpot likewise requires the form to be created in the connected Meta account and run under the Page connected to HubSpot.
Why test leads work but real leads stop
A successful setup test only confirms that the test worked under the conditions at that time. It does not establish that the live workflow is on or that the integration still has access to the Page’s leads. If “Why did test leads work but real leads stop?” is the issue, check these items:
- The automation is switched on and its trigger still points to the intended account, Page and form.
- The Facebook connection has not expired or had its permissions changed.
- The CRM or connector app still appears in the Page’s lead access where access is customized.
- The live lead exists in Meta’s lead records.
- The test or event history shows a status or error that helps identify where processing stopped.
If permissions changed, reconnect the account, update the trigger to use that account and reactivate the workflow as needed. Zapier describes this recovery sequence in its troubleshooting guidance.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →When the CRM has the lead but a report does not
A lead missing from a dashboard is not necessarily a failed sync. Reports can apply different attribution rules. HubSpot gives the example of a person who became a contact through a website conversion before later submitting a lead ad: a report based on first ad interaction may omit that lead. HubSpot says its “All ad interactions” report can show all synced lead-ad leads for Professional and Enterprise customers; it describes an Ads Interactions list as an option for Starter or Free users. These are HubSpot-specific options and depend on its subscription guidance, not a general rule for other CRMs.
Also check the HubSpot sync scope. Its guide identifies a setting limited to “New leads” rather than “All leads” as a possible reason for a discrepancy. Compare the CRM record itself with the report before repairing an integration that may already be working.
Use the symptom to choose the next check
| What you find | Next checks |
|---|---|
| No expected lead record or test lead in Meta | Verify the form submission and the Page/form used. The cited provider guidance does not establish a complete diagnosis for every Meta-side failure. |
| Lead exists in Meta, but the integration test fails | Check Page, user, ad-account and CRM-app permissions; customized lead access; and the exact Page and form selected. |
| Test passes, but live leads do not arrive | Check the live workflow’s on/off state, the Page’s CRM-app lead access, connection expiry and whether the trigger uses the current account and form. |
| CRM record exists, but a report omits it | Inspect attribution rules and sync scope before changing access or rebuilding the connection. |
For Salesforce Lead Capture, use its test status and error details to narrow the failure, then verify prerequisites and that the lead remains available in Meta. Its setup requirements and supported editions are product-specific; consult Salesforce’s prerequisites rather than assuming they apply to a different connector. Meta’s lead-generation forms campaign setup guide covers campaign and form setup, but does not establish a universal CRM delivery-time promise.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
