Skip to main content

Why Facebook leads go missing and what stops it

updated 5 min read

founder

Start free

When a lead goes missing, the culprit is usually not “the internet” but one specific step. Let us go through which step it is and what closes it.

Where the lead comes from

The moment someone fills in a Lead Ads form on Facebook or Instagram and taps the submit button, Meta sends Yuboraman a signed webhook. The lead does not wait in a queue — it enters the system the instant it is submitted.

The signature is not there for show: every request arrives with Meta's signature and that signature is checked. A request whose signature does not match is not accepted as a lead, so an outsider cannot push a fake lead into your integration.

When this step works, the lead is in the system the moment the form is submitted. Trouble usually starts at the next step — delivering the lead to your destination, or sometimes to several destinations at once.

When delivery fails: the retry ladder

The destination is not always ready: the Telegram bot may be blocked, the CRM may not answer, the sheet may not open for a while. In that case the lead is not thrown away — the delivery is retried.

First the system makes three quick attempts within a few seconds. If those fail, the pause grows to 5, 10, 20 and 40 minutes and then settles at one attempt an hour. If the destination itself says “wait this long” (the Retry-After header in its response), the system honours that interval — up to 10 minutes — instead of hammering the service and running into its limit.

These attempts run for 24 hours from the moment delivery started. Underneath them sits one more safety net: an hourly sweep collects the leads still in error within those 24 hours whose attempts broke off, and puts them back in the queue. Even if the CRM was down for half an hour, once it is back the leads reach their place.

  • First, three quick attempts within a few seconds
  • Then the pause grows from 5 minutes, up to an hour at most
  • The Retry-After header sent by the destination is honoured up to 10 minutes
  • Every hour, undelivered leads from the last 24 hours go back in the queue

What happens if the webhook misses one

A webhook is reliable but not perfect: a message can get stuck in the network or on Meta's side. So there is a backup mechanism underneath it.

Four times a day — at 08:00, 12:00, 16:00 and 20:00 — the system asks Meta itself for the leads of the last 72 hours, finds the ones that never arrived by webhook and puts them into processing. Even if one message is lost, the lead is caught by the next sweep at the latest.

This backup is there for completeness, not for speed. Normally the lead arrives by webhook straight away; the sweep only closes the gaps.

Why one lead sometimes arrives twice

Two paths can lead to the same lead — the webhook and the backup sweep. So there is duplicate control: every lead is remembered by the identifier of its source message, and if that identifier turns up again the lead is not sent a second time.

A Facebook lead is recognised by the ID Meta gave it. A site lead is recognised by the ID in the request or, if there is none, by the request content — in that case a repeat is caught within a short window, from a few minutes up to an hour. The control is not configurable. What matters: it works by the source message, not by the phone number — if one person fills in two different forms, that is two separate leads.

Even so, delivery does not guarantee “exactly once”. When the destination's answer stays unclear — the request went out, no response came back — the system tries again, and a duplicate can appear. The trade-off is deliberate: a repeated lead costs less than a lost one.

The honest limit: 24 hours

Automatic retries do not run forever. If the destination has not accepted the lead within 24 hours, the system stops trying and the lead stays in error, marked as not delivered within 24 hours.

What comes after that is a person's job: you fix the destination and press the “Resend” button in the panel. It sends the errored leads of the last 7 days again, up to 5,000 per press. That is deliberate: a destination that has not answered for a whole day usually has broken settings or is switched off, and endless retries only fill up the queue.

Facebook leads have one more path: in the integration menu, open the “Facebook leads” window, choose “Resend” and pick a period of up to 30 days. The leads of that period go to the CRM again, and the ones already delivered are not sent a second time.

In practice that means: if you notice a destination has been silent for a while, check it the same day. After 24 hours the lead will not go by itself, and manual resending has a limit too: 7 days for the button and 30 days for resending Facebook leads to the CRM.

Video tutorial

Lesson 8

Integration set up, but no leads arriving?

What to check when leads don't reach your Telegram group or Google Sheet: the connection, the Telegram bot's rights, a lead form test, the integration's status and logs, and the Lead Access Manager setting.

Duration:

By Bahodirjon Siddiqov, ads specialist

The video is in Uzbek.

Another useful lesson: Page not showing? Fixing form connection problems

Related pages

Read next

Do not keep your leads waiting

Sign up and turn on your first integration. No code needed, and up to 1000 leads a month are free.