Why Facebook lead ads bring fake and junk leads, and how to filter them
Wrong numbers, duplicates, people outside your area and accidental taps. Where junk leads in Meta lead ads come from, what you can change inside Ads Manager, and how to test every lead before your team calls it.
If you run lead ads on Facebook or Instagram, you know the pattern. The dashboard says 300 leads this month. Your team says half of them were useless. Both are telling the truth: Meta counts form submissions, your team counts people who wanted to talk.
This article explains where junk leads come from, what you can change inside Meta, and what to do with each lead after it arrives.
What "junk" usually means
When owners say a lead was fake, they usually mean one of six things:
- The number does not work. It is too short, a repeated pattern like 9999999999, or not a mobile number for your country.
- The same person, twice. Someone fills your form on Monday and again on Thursday. Your team calls them twice and counts them twice.
- Outside your area. Your clinic is in Pune and the lead lives in Nagpur. A real person, but not a customer you can serve.
- Junk answers. "asdf", "test", "no" or a string of random letters in a text field.
- Test leads. Leads created by your own team or agency with Meta's Lead Ads Testing Tool while setting up the CRM connection, which then flow into the sales list.
- Accidental or curious taps. A real person with a working number who does not remember filling the form, or filled it to see what happens.
The first five can be caught automatically. The sixth can only be found by talking to the person.
Why Meta lead ads produce more of it
Instant forms are built to be easy. Meta fills in contact details such as name, phone number and email from the person's account, so submitting can take a couple of taps. That is good for volume and bad for intent.
The default form type is More volume, described in Ads Manager as quick to fill out and submit. If your campaign is optimised for the number of leads, Meta's delivery system does exactly that: it finds people who are likely to submit forms. It has no way of knowing which of them became customers unless you tell it.
What you can change inside Meta
Switch the form type to Higher intent. It adds a review step where the person confirms their details before sending. You will usually get fewer leads, and the ones you get have looked at what they are submitting. (Jon Loomer's guide to instant forms walks through the three form types.)
Ask one question that takes thought. A short answer or a multiple choice question about the actual need ("Which treatment are you interested in?", "1, 2 or 3 BHK?") slows down people who were never interested and gives your team context for the call.
Tell Meta which leads were real. This is the change that compounds. Meta's Conversions API for CRM lets you send back what happened to each lead (qualified, booked, converted), and the Conversion leads performance goal then optimises for people who reach that stage instead of people who submit forms. We cover the requirements in Meta Conversions API for CRM, in plain words.
What to do with each lead after it arrives
Even with the best form settings, some junk gets through. The fix is to test every lead before a person spends time on it:
- Check the number against the patterns of a real mobile number in your country.
- Check for duplicates against the same number in recent days.
- Check the location against the areas you actually serve.
- Check the answers for junk text.
- Drop test leads from your sales list.
- Check the speed. A long form completed in a few seconds was probably not read.
Then contact the ones that pass, quickly, in their language. A short WhatsApp message with two or three questions tells you more than any check. People who do not reply get a call. Only after that does a lead reach your sales team, with the answers attached.
Two rules make this safe. Never delete a lead that fails a check, hold it with the reason so someone can release it with one tap if the check was wrong. And send the outcome back to Meta, so the next month has fewer of them.
How Streakstone handles this
Streakstone runs exactly these six checks the second a Meta, Google or website lead arrives, messages the people who pass on WhatsApp in Marathi, Hindi, English or Arabic, calls them with an AI voice if they do not reply, and sends only qualified leads to your CRM or your reps on WhatsApp. Leads that fail wait in Held for review with the reason. Every stage goes back to Meta through the Conversions API. You can see it working on the homepage or start a 14-day trial.
Sources
- Meta for Developers: Conversions API for CRM integration
- Meta for Developers: Lead Ads Testing Tool
- Jon Loomer: A guide to instant forms