Seatext library / BotRefund evidence
When to Flag a Lead as Bad vs. Unqualified: A Readiness Checklist
Flag a lead as bad only when you have concrete evidence of invalidity — bot behavior, fake contact details, or zero human intent. Unqualified leads are real people who don't fit your offer yet;...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
Only flag a lead as bad when it shows clear signs of invalidity like bot behavior, fake contact info, or zero intent. An unqualified lead is a real person who doesn't match your ideal customer profile, budget, or timing — they may convert later with nurture. A bad lead is a technical artifact: a bot submission, a form filled with garbage data, or a click farm entry that never had purchase potential. Treating the two the same way pollutes your CRM, skews your Meta pixel, and makes your ad platform optimize for fraud.
Readiness Checklist: Conditions That Must Be Met Before Marking a Lead Bad
Use this checklist before you change a lead status to "bad" or "invalid." Every item should be verifiable from your analytics, CRM, or landing-page session data.
- Contact details are technically invalid — disconnected phone numbers, email domains that don't exist, or repeated addresses across multiple submissions.
- Session behavior is non-human — form submitted in under two seconds, no scrolling, no field corrections, uniform click paths, or zero meaningful time on the offer page.
- Timing patterns are mechanical — multiple leads arriving in tight bursts, conversions clustered at unusual hours, or submissions immediately after page load with no engagement.
- Clustered quality drop by placement or audience — a sharp lead-quality difference tied to a specific placement, creative, audience expansion, device type, or landing page variant.
- CRM outcomes show zero human follow-through — high reported lead count paired with no calls connected, demos booked, qualified opportunities, or repeat engagement over a reasonable window.
- Attribution is preserved — you still have the click identifier, campaign context, timestamp, URL parameters, and CRM record before any campaign changes.
If you cannot tick at least three of these with evidence, keep the lead in an unqualified or nurture track. A single signal is rarely enough; clusters of signals are what separate fraud from a bad fit.
Why the Distinction Matters
Meta's machine learning optimizes toward whatever conversion events you feed it. When bot submissions or form spam trigger your pixel, the algorithm learns to find more bots. Imperva reported that automated traffic represented more than half of web traffic in 2025, but that does not mean half of your Meta clicks are fraudulent. Treat broad statistics as context, then measure your own sessions and leads. Advertisers who clean their traffic see an average 40–60% improvement in true ROAS within six to eight weeks. The cost of mislabeling is double: you waste budget on fake clicks and you teach the platform to buy more of them.
How Bad Leads Enter Meta Campaigns
Meta campaigns reach people across Facebook, Instagram, and the Audience Network — thousands of third-party apps and sites. Publishers on that network sometimes run automated scripts to click ads and generate revenue. Profile scrapers and directory bots crawl Facebook and follow outbound links on posts and ads. Competitor click farms and affiliate fraud rings also target high-volume lead campaigns. These sources leave repeatable technical fingerprints: superhuman input speed (<1 ms), robotic linear mouse movements, absence of humanlike mouse tremor, grid-aligned movement patterns, and sessions with no clicks or scrolling.
Four-Layer Audit Framework
Before you flag any lead, run a structured audit that compares ad-platform data, website sessions, and CRM outcomes. The four layers are:
- Platform delivery — Compare reach, link clicks, landing-page views, placements, and spend. A cheap placement is not a win unless it produces contacts that can be reached and qualified.
- Landing-page evidence — Measure page loads, redirects, consent behavior, form start, form completion, time to completion, and meaningful engagement. A click-to-session gap often has ordinary explanations: in-app browsers, tracking consent, slow loads, or analytics configuration.
- Lead verification — Record whether an email is deliverable, a phone connects, duplicate details recur, and the prospect confirms interest. Add qualification questions that reveal fit, not just extra fields that make the form longer.
- Sales outcome feedback — Give sales a small, mandatory set of dispositions: verified, contacted, qualified, disqualified, duplicate, invalid details, no response. Feed those dispositions back into your reporting so you can see which campaigns produce real pipeline.
Signs to Wait: When a Lead Is Just Unqualified
Keep the lead in a nurture track when:
- The contact details check out (email delivers, phone rings) but the prospect says "not now" or "wrong budget."
- Session behavior looks human — scrolling, field corrections, time on page — but the lead doesn't match your ICP.
- Quality varies by audience or creative in a way that suggests targeting mismatch, not fraud.
- Sales dispositions show "disqualified" or "no response" rather than "invalid details."
Unqualified leads are real people. They may convert in a later quarter, refer a colleague, or enter a different buying cycle. Bad leads never do.
Common Mistakes That Blur the Line
| Mistake | What Happens | Better Approach |
|---|---|---|
| Treating every unresponsive lead as fraud | Excludes valuable audiences; shrinks reach | Require clustered evidence before flagging |
| Changing campaign settings before preserving attribution | Loses click IDs, timestamps, placement data needed for refund claims | Export click identifiers and CRM records first |
| Relying on server-side logs only | Misses advanced botnets that mimic human IPs and headers | Add client-side behavioral verification |
| Using industry averages as proof for your account | Over- or under-estimates your actual invalid rate | Calculate your own baseline: sessions per click, contactable leads, verified leads, qualified opportunities, revenue by campaign |
| Flagging a lead bad after a single sales call fails | Confuses fit problems with validity problems | Use the disposition "disqualified" or "unqualified"; reserve "invalid" for technical evidence |
Key Facts
| Metric | Value | Source |
|---|---|---|
| Average invalid click rate on Meta/Google | 14% | S6 |
| Typical ROAS improvement after cleaning traffic | 40–60% within 6–8 weeks | S6 |
| BotRefund refund approval rate across client claims | 83% | S2, S7 |
| Time to install BotRefund and start free audit | ~1 minute | S2 |
| Behavioral signals BotRefund detects | Ghost clicks, honeypot traps, robotic mouse paths, superhuman speed (<1 ms), grid-aligned movement, static sessions, unnatural durations | S2 |
| Meta Audience Network default status | Opted in by default | S3 |
| Sales dispositions recommended for feedback loop | Verified, contacted, qualified, disqualified, duplicate, invalid details, no response | S5 |
Limitations and When This Advice Does Not Apply
This checklist assumes you run Meta lead-generation campaigns with a CRM and landing-page analytics. If you rely solely on platform-reported lead counts without session or CRM data, you cannot reliably separate bad from unqualified. The framework also assumes you have control over form fields and can add verification steps (email deliverability, phone connection, confirmation flows). Pure e-commerce campaigns optimizing for purchase events instead of lead forms follow a different evidence trail — look for fake orders, chargeback patterns, and address verification failures instead.
Terminology
- Bad lead (invalid lead) — A submission with technical evidence of non-human origin or fabricated contact data. No real person exists behind it.
- Unqualified lead — A real person who does not currently match your ideal customer profile, budget, authority, need, or timeline.
- Pixel poisoning — When bot conversions train Meta's algorithm to optimize for more bot traffic.
- Click ID (GCLID / fbclid) — The unique identifier appended to landing-page URLs that ties a session back to a specific ad click. Required for refund claims.
- Client-side behavioral verification — Analysis of mouse movement, scroll depth, input timing, and interaction patterns in the visitor's browser to distinguish humans from automation.
- Disposition — A standardized sales outcome label (e.g., verified, disqualified, invalid details) fed back into reporting.
FAQ
How many bad signals do I need before I flag a lead?
At least three independent signals from different categories (contactability, timing, session behavior, campaign pattern, CRM outcome). A single signal is a reason to investigate, not to flag.
What if sales says the lead is "fake" but the session looks human?
Trust the session data. A real person can give a fake name or wrong number. Mark the lead "invalid details" in your disposition set, not "bad." That keeps the session data clean for pixel training while flagging the contact quality issue.
Can I automate the bad-lead flagging?
Yes, but only after you've validated the rules against a labeled sample. Build rules that require clustered evidence (e.g., superhuman speed + honeypot trigger + invalid email). Review flagged leads weekly for false positives before feeding the status back to Meta.
Does flagging a lead bad in my CRM tell Meta to stop sending similar traffic?
Not directly. Meta optimizes on conversion events fired from your pixel. If you stop firing the lead event for flagged leads (or fire a "lead_invalid" event with a negative value), the algorithm adjusts. Simply changing a CRM status does nothing unless it's connected to your conversion API.
What's the fastest way to get a refund for bot clicks on Meta?
Collect click IDs, session recordings, and behavioral evidence for each suspicious click. Submit a structured dispute through your Meta rep or the Ads Manager help flow. BotRefund clients see an 83% approval rate on claims backed by client-side evidence.
Should I turn off Audience Network to avoid bots?
It's a blunt fix. Audience Network can deliver cheap volume; the problem is quality variance by placement. Audit placement-level lead quality first. If a specific placement cluster shows the bad-lead signals above, exclude that placement rather than the whole network.
How often should I re-audit my lead quality baseline?
Quarterly, or whenever you change creative, audience strategy, or landing page. Baselines drift as Meta's delivery shifts and fraud tactics evolve.
How BotRefund Helps
BotRefund adds client-side behavioral verification to your landing pages in about one minute. It captures ghost clicks, honeypot interactions, robotic mouse paths, superhuman input speed, grid-aligned movement, static sessions, and unnatural durations — the same signals used to separate bad leads from unqualified ones. Each detection comes with video proof and the click ID you need for Meta and Google refund disputes. The free audit shows your current invalid rate before you commit. You export the report, send it to your ad rep, and claim the refund. The platform does not replace your CRM dispositions or sales feedback loop; it supplies the technical evidence layer that makes those dispositions defensible.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.