13 min read

Facebook Leads Not Syncing? 7 Fixes That Actually Work

Luke Moulton

Your Facebook lead ads are running, the budget is being spent, but leads aren’t showing up in your CRM. Sound familiar? You’re not alone — it’s one of the most common (and most frustrating) problems in paid social advertising.

The good news: Facebook leads not syncing is almost always fixable. This guide covers the 7 most common reasons leads stop syncing, how to troubleshoot by platform (Zapier, Make, native CRM, and more), what specific error messages mean, and how to permanently fix the problem.

7 Reasons Your Facebook Leads Aren’t Syncing

Before diving into platform-specific fixes, let’s identify why leads stop syncing in the first place. In most cases, it’s one of these seven causes.

1. Facebook Page Permissions Were Reset

This is the #1 reason leads stop syncing — and it catches everyone off guard. Meta periodically resets third-party app permissions on your Facebook Page, especially after:

  • Page admin changes (someone is added or removed)
  • Facebook policy updates or platform migrations
  • Your access token expires (typically every 60-90 days)
  • You change your Facebook password

When permissions reset, your sync tool silently loses access to new lead data. Leads still come in through your ads — they just can’t be delivered to your CRM or email.

How to check: Go to your Facebook Page → Settings → Business Integrations (or Page Access). Look for your sync tool (e.g., Zapier, LeadSync, LeadsBridge) in the list. If it’s missing or shows limited permissions, that’s your problem.

Fix: Re-authorize the integration. In most tools, this means disconnecting and reconnecting your Facebook account. For LeadSync, go to Settings → Sources → Reconnect Facebook.

2. Terms of Service Not Accepted

Meta requires you to accept the Lead Ads Terms of Service before any third-party app can access your leads. This is easy to miss — especially if you created your Page before lead ads existed, or if a new team member set up the ads.

How to check: Visit your Page’s Lead Ads Terms of Service page in Meta Business Suite. You’ll see a prompt to accept if you haven’t already. You can also check by going to your Page → Publishing Tools → Forms Library → look for any ToS banner.

Fix: Accept the Terms of Service. It takes 10 seconds, and leads will start syncing immediately after. Every Page admin who manages lead ads should accept this.

3. Lead Form Mismatch

Your Facebook ad must use the exact same lead form that’s configured in your sync tool. This sounds obvious, but it’s surprisingly easy to create a new form (or duplicate one) and forget to update your integration.

Common scenarios where this happens:

  • You duplicated a campaign and it created a new form
  • A team member created a fresh form instead of using the existing one
  • You’re A/B testing forms but only connected one to your sync
  • The form was deleted and recreated with the same name (different ID)

How to check: Compare the form ID in your ad (Ads Manager → Ad → Instant Form) with the form configured in your sync tool. They must match exactly.

Fix: Update your sync connection to point to the correct form, or update your ad to use the form that’s already connected.

4. CRM Access Token Expired

Just like Facebook can revoke permissions, your destination CRM can too. OAuth tokens expire, API keys get rotated, and CRM admins change settings — all of which break the connection on the receiving end.

This is especially common with:

  • HubSpot — tokens expire if the authorizing user is deactivated
  • Salesforce — security tokens reset when passwords change
  • ActiveCampaign — API keys change if regenerated in settings
  • Mailchimp — API keys are tied to the user who created them

How to check: Try sending a test lead through your sync tool. If the error mentions “unauthorized,” “invalid token,” “access denied,” or “CRM access revoked,” your destination credentials have expired.

Fix: Re-authorize your CRM connection. Go to your sync tool’s destination settings and reconnect the account. You may need to generate a new API key in your CRM’s settings.

5. Webhook Delivery Failures

If your sync tool uses webhooks (real-time push notifications from Facebook), those webhooks can fail silently. Common causes include:

  • Your receiving server returned a timeout or 5xx error
  • SSL certificate expired on the webhook endpoint
  • Firewall or CDN blocked Facebook’s webhook delivery IPs
  • The webhook URL changed (e.g., after a server migration)

Facebook will retry failed webhooks for up to 24 hours, then give up. If your endpoint is down for longer than that, those leads are lost.

How to check: Look at your sync tool’s delivery logs or error dashboard. Tools like LeadSync show delivery status for every lead. For custom webhook setups, check your server access logs for Facebook’s delivery attempts.

Fix: Resolve the server/SSL issue, then re-subscribe the webhook. For tools that handle this automatically, simply reconnecting the Facebook source will re-establish the webhook.

6. Zapier/Make Polling Delays and Task Limits

If you’re using Zapier or Make (formerly Integromat) to sync Facebook leads, there’s a fundamental limitation: these tools poll for new leads on a schedule rather than receiving them in real-time.

Here’s how polling works:

  • Zapier Free/Starter: Polls every 15 minutes
  • Zapier Professional: Polls every 2 minutes
  • Make Free: Minimum 15-minute intervals
  • Make Pro: Minimum 1-minute intervals

This means a lead could wait up to 15 minutes before your tool even checks for it — and that’s when everything is working. Add task limits (Zapier’s Free plan caps at 100 tasks/month), and you can easily miss leads entirely when your quota runs out mid-campaign.

How to check: In Zapier, go to Zap History and look for “Zap turned off” or “Task limit reached.” In Make, check your scenario history for “Operation limit reached” warnings.

Fix: Upgrade your plan for faster polling, or switch to a webhook-based tool that receives leads in real-time (more on this below).

7. Meta API Rate Limits or Outages

Meta’s Graph API has rate limits that affect how often tools can fetch lead data. If you’re running high-volume campaigns across many Pages, your sync tool may hit these limits — especially polling-based tools that make repeated API calls.

Meta also experiences periodic outages that affect the Lead Ads API specifically. During these outages, leads are collected but API access is temporarily blocked.

How to check: Visit the Meta Platform Status page for current outage information. For rate limits, your sync tool’s error logs will show “rate limit exceeded” or HTTP 429 errors.

Fix: For outages, wait it out — leads collected during the outage will still be accessible once the API recovers. For rate limits, reduce polling frequency or switch to webhook-based delivery which uses fewer API calls.

How to Troubleshoot by Platform

Different sync tools fail in different ways. Here’s how to diagnose the problem based on what you’re using.

Zapier: Facebook Leads Not Syncing

Zapier is the most commonly used (and most commonly reported broken) tool for Facebook lead syncing. Here’s the troubleshooting checklist:

  1. Check Zap history — Go to Zap History. Are leads appearing but erroring? Or are no leads being detected at all?
  2. Check task usage — If you’ve hit your monthly task limit, Zapier silently stops running Zaps. Go to Settings → Usage to check.
  3. Re-test the trigger — Edit your Zap, go to the trigger step, and click “Test trigger.” If no leads appear, the Facebook connection is broken.
  4. Reconnect Facebook — Go to Zapier → My Apps → Facebook Lead Ads → Reconnect. This refreshes the access token.
  5. Check Page permissions — When reconnecting, make sure you grant access to the correct Page (Zapier shows a Page selection dialog).
  6. Verify the form selection — In your Zap trigger, confirm the selected Page and Form match your active ad campaign.

Common Zapier-specific issue: Zapier’s Facebook Lead Ads integration uses polling, not webhooks. Even when everything is connected correctly, there’s a built-in delay of 2-15 minutes depending on your plan. If you’re seeing leads arrive late (but they do arrive), this is normal Zapier behavior — not a bug.

Make (Integromat): Facebook Leads Not Syncing

Make works differently from Zapier — it uses “scenarios” that can be triggered on a schedule or by a webhook.

  1. Check scenario history — Open your scenario and click the history tab. Look for failed executions (shown in red).
  2. Verify the schedule — Is the scenario set to run at the right interval? A paused scenario won’t poll for leads.
  3. Check operations usage — Make limits operations per month. If you’ve exceeded your limit, scenarios stop running.
  4. Re-authorize Facebook — Go to Connections → Facebook Lead Ads → Re-authorize. Choose the correct Page during re-auth.
  5. Check the webhook (if using instant trigger) — Make offers a “Watch New Leads” instant trigger. If it stops working, delete and recreate the webhook module.

Native CRM Integrations: Leads Not Appearing

Some CRMs offer direct Facebook lead ad integrations (HubSpot, Salesforce, etc.). When these break:

  1. Check the integration status in your CRM — Most CRMs show a connected/disconnected status for Facebook. Look for warning icons.
  2. Verify the Facebook user — The Facebook account that authorized the CRM integration must still have admin access to the Page. If that person left your team, the integration breaks.
  3. Re-authorize from the CRM side — Don’t just reconnect Facebook — go to your CRM’s integration settings and re-authorize the Facebook connection there.
  4. Check field mapping — If leads are syncing but data is missing, your CRM’s field mapping may need updating (especially after adding new form fields).

LeadsBridge and Other Sync Tools

Third-party sync tools like LeadsBridge, Automate.io (discontinued), or Pabbly Connect each have their own dashboards for troubleshooting:

  • Check the bridge/connection status — Most tools show green (active), yellow (warning), or red (broken) indicators.
  • Review error logs — Look for specific error messages about permissions, tokens, or API failures.
  • Re-authorize both ends — Reconnect both your Facebook source and your CRM destination. Credentials can expire on either side.

Common Error Messages Explained

Seeing a specific error? Here’s what it means and how to fix it.

“Terms of Service Not Accepted”

This error means the Facebook Page hasn’t accepted Meta’s Lead Ads Terms of Service. Without this, no third-party app can access your lead data — the API simply refuses to return leads.

Fix: A Page admin must accept the Lead Ads ToS. Go to your Facebook Page → Publishing Tools → Forms Library. If there’s a Terms of Service prompt, accept it. You only need to do this once per Page.

Common trap: If you manage multiple Pages, each one needs its own ToS acceptance. Accepting for one Page doesn’t cover the others.

“CRM Access Revoked” or “Invalid Access Token”

Your CRM has revoked the access token that your sync tool was using. This typically happens when:

  • The CRM user who authorized the connection was deactivated or had their role changed
  • An admin regenerated API keys
  • The OAuth token reached its expiration date
  • A security policy in the CRM forced a token rotation

Fix: Go to your sync tool’s destination settings and reconnect the CRM. Make sure you authorize with an admin account that won’t be deactivated.

“Test Lead Sent But Not Received”

You sent a test lead from Facebook’s Lead Ad Testing Tool, but it never arrived at your destination. This usually means:

  • Permissions issue — Your sync tool can’t read leads from the Page (see #1 above)
  • Wrong form connected — The test form isn’t the one configured in your sync (see #3 above)
  • Email in spam — If syncing to email, check your spam/junk folder
  • Polling delay — If using Zapier/Make, wait 15 minutes and check again

Pro tip: Use Facebook’s Lead Ad Testing Tool to generate a test lead. Select your Page, choose your form, and click “Create Lead.” If using LeadSync, the test lead should arrive within 60 seconds. LeadSync’s App ID for reference: 1711149865783520.

“Permission Denied” or “Insufficient Permissions”

The Facebook user who connected the integration doesn’t have the right role on the Page. To access lead data, the connected user must have at least the Advertiser role (ideally Admin).

Fix: Check the user’s Page role under Page Settings → Page Roles. Upgrade to Admin if needed, then re-authorize the sync tool connection.

“Rate Limit Exceeded” (Error 429)

Your sync tool has made too many API requests to Facebook in a short period. This is more common with polling-based tools running across many Pages.

Fix: Wait 15-30 minutes for the rate limit to reset. If this happens frequently, your tool is polling too aggressively — consider switching to a webhook-based solution that makes fewer API calls.

The Real Fix: Real-Time Sync vs. Polling

If you’ve been troubleshooting repeatedly — reconnecting accounts, upgrading Zapier plans, checking permissions every week — there’s a deeper issue at play: you’re using the wrong architecture.

Most lead sync problems come down to two fundamentally different approaches:

Polling (Zapier, Make, Most Tools)

Polling-based tools check Facebook for new leads on a timer — every 1 to 15 minutes. This creates several problems:

  • Built-in delay — Even on premium plans, leads arrive minutes late
  • Higher API usage — Constant polling burns through API rate limits
  • Task/operation limits — Every poll counts as a task, even when there are no new leads
  • Silent failures — When polling stops (task limit, error), there’s often no alert

Webhooks (Real-Time Push)

Webhook-based tools receive a push notification from Facebook the instant a lead is submitted. Benefits:

  • Instant delivery — Leads arrive in under 60 seconds
  • No task limits — You’re not burning tasks on empty polls
  • Lower API usage — No repeated polling calls
  • More reliable — Push-based systems are harder to silently break

LeadSync uses Facebook’s real-time webhook API to deliver leads in under 60 seconds — no polling, no task limits, no delays. It’s purpose-built for Facebook (and Instagram, LinkedIn, TikTok, and Google) lead ads, which means fewer things can break compared to general-purpose automation tools.

How to Switch to LeadSync in 5 Minutes

If you’re tired of troubleshooting broken syncs, here’s how to set up LeadSync and start receiving leads in real-time.

Step 1: Connect Your Facebook Account

Sign up at leadsync.me and connect your Facebook account. LeadSync will request permission to access your Pages and lead forms. Grant access to the Pages running lead ads.

Step 2: Connect Your Destination

Choose where you want leads delivered. LeadSync supports 40+ CRMs and tools including:

  • CRMs: HubSpot, Salesforce, Pipedrive, Zoho, ActiveCampaign, Follow Up Boss
  • Email marketing: Mailchimp, ConvertKit, Klaviyo, AWeber
  • Notifications: Email, SMS, Slack
  • Other: Google Sheets, webhooks, Jobber, ServiceTitan

Step 3: Map Your Fields

LeadSync shows your Facebook form fields on the left and your CRM fields on the right. Match them up — name to name, email to email, phone to phone. Custom fields are supported too.

Step 4: Send a Test Lead

Use Facebook’s Lead Ad Testing Tool to create a test lead. With LeadSync, it should arrive at your destination within 60 seconds. Verify the data mapped correctly.

Step 5: Go Live

That’s it. LeadSync will now deliver every new lead in real-time. You can safely turn off your old Zapier/Make automation — or keep it as a backup until you’re confident everything is working.

Start your free 14-day trial →

Quick-Reference Troubleshooting Checklist

Bookmark this checklist for the next time leads stop syncing:

CheckWhat to Look ForFix
Page permissionsSync tool missing from Business IntegrationsRe-authorize the integration
Lead Ads ToSToS banner in Forms LibraryAccept Terms of Service
Form matchForm ID in ad ≠ form ID in sync toolUpdate form selection
CRM connection“Unauthorized” or “token expired” errorsReconnect CRM in sync tool
Webhook statusServer errors in delivery logsFix server issue, re-subscribe
Task/operation limits“Zap turned off” or quota warningsUpgrade plan or switch tools
API rate limitsHTTP 429 errors in logsWait 30 min or reduce polling
Facebook user roleConnected user lacks Admin/Advertiser roleUpdate Page role, re-authorize

Frequently Asked Questions

Why are my Facebook leads not syncing to my CRM?

The most common reasons are expired permissions (Facebook resets third-party access periodically), Lead Ads Terms of Service not accepted, form mismatch between your ad and sync tool, or expired CRM credentials. Check each of these in order — permissions are the culprit about 60% of the time.

How do I fix “Terms of Service not accepted” for Facebook Lead Ads?

Go to your Facebook Page → Publishing Tools → Forms Library and look for a Terms of Service prompt. A Page admin must accept the Lead Ads ToS before any third-party tool can access leads. Each Page needs its own acceptance — it’s not account-wide.

Why is Zapier not picking up my Facebook leads?

Zapier polls for leads every 2-15 minutes depending on your plan, so there’s always a delay. If leads aren’t arriving at all, check your Zap history for errors, verify your task limit hasn’t been reached, and reconnect your Facebook account in Zapier’s app settings. Also confirm the correct Page and form are selected in the Zap trigger.

How long does it take for Facebook leads to sync?

It depends on your tool. Polling-based tools like Zapier take 2-15 minutes. Webhook-based tools like LeadSync deliver leads in under 60 seconds. Facebook’s own Leads Center in Meta Business Suite can take hours to update and requires manual checking.

Can I recover Facebook leads that failed to sync?

Yes, but there’s a time limit. Facebook stores lead data for 90 days. You can download leads manually from Ads Manager → Instant Forms → Download. Some sync tools (including LeadSync) also let you re-sync historical leads after fixing the connection issue.

Why do Facebook lead ads stop working after a password change?

Changing your Facebook password invalidates all active access tokens. Every third-party tool connected to your account — including lead sync tools — loses access immediately. After a password change, you need to re-authorize each integration.

What does “CRM access revoked” mean?

This error means your CRM has invalidated the access token your sync tool was using. Common causes: the authorizing user was deactivated, API keys were regenerated, or a security policy forced token rotation. Fix it by reconnecting the CRM destination in your sync tool.

How do I test if my Facebook lead sync is working?

Use Facebook’s Lead Ad Testing Tool: go to Meta Business Suite → All Tools → Lead Ads Testing Tool. Select your Page and form, then click “Create Lead.” A test lead should arrive at your connected destination within 60 seconds (webhook-based tools) or 2-15 minutes (polling-based tools).

Is there a more reliable alternative to Zapier for Facebook lead syncing?

Yes. Purpose-built lead sync tools like LeadSync use Facebook’s real-time webhook API instead of polling, which means faster delivery (under 60 seconds), no task limits, and fewer points of failure. They’re designed specifically for lead ads, so they handle Facebook’s permission quirks automatically.

Do I need to accept Terms of Service for each Facebook Page separately?

Yes. Meta’s Lead Ads Terms of Service must be accepted individually for each Facebook Page that runs lead ads. If you manage multiple Pages, check each one. This is the most commonly missed step when setting up lead syncing for a new Page.

author avatar
Luke Moulton
Luke is the founder of LeadSync and, as a Digital Marketer, has been helping businesses run lead generation campaigns since 2016.

Sync your leads in under 60 seconds

Try LeadSync free for 14 days. No credit card required.

Start Free Trial