Seatext library / BotRefund evidence
How to Identify Cheap Leads That Are Actually Invalid Traffic or Bots
Cheap leads are usually invalid traffic when several signals appear together: forms completed faster than a human can type, bursts of submissions with repeated contact details, sessions with no real engagement, and contacts that...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
Cheap leads are usually invalid traffic when several signals appear together: forms completed faster than a human can type, bursts of submissions with repeated contact details, sessions with no scrolling or clicks, and contacts that never answer. No single signal proves a bot. A cluster of signals, checked in a fixed order, gives you evidence you can act on.
Use this diagnostic sequence: preserve your click and campaign data first, compare ad-platform clicks to real landing-page sessions, inspect behavioral signals, verify contactability, and only then decide whether to block a placement or file a refund claim.
What counts as invalid traffic or bot traffic?
Invalid traffic is any click or impression that is not the result of genuine user interest. That includes accidental clicks, automated tools, bots, click farms, scrapers, and competitor click fraud.
Bot traffic is a subset of invalid traffic. A bot is software that loads pages, clicks ads, or submits forms without a human driving it. Some bots are simple scrapers. Others use real browsers and rotate IP addresses to look human.
Not every bad lead is a bot. A real person can click an ad by accident, fill a form with a typo, or lose interest after submitting. Treating every unresponsive contact as fraud can make you exclude a valuable audience.
Why cheap leads hide the problem
Ad platforms bill a click when it happens. Whether that click was human is left to you to prove, after the fact, session by session. Your dashboard cannot show you the problem, which is exactly what makes it expensive.
Meta Ads Manager may report a steady cost per lead while the sales team receives unreachable contacts, copied messages, or enquiries that never progress. The cost per lead metric only looks healthy if the lead can be reached and qualified.
There is a second cost. When bots trigger conversion events, they poison the Meta Pixel and make the ad platform optimize targeting for bots rather than real buyers. Cheap lead volume can quietly teach the algorithm to buy more of the same fake traffic.
Before you diagnose: what you need
Run this diagnostic only after you have the data to compare. You need:
- Ad platform access with campaign, ad set, creative, placement, device, and click identifier data.
- Website analytics or server logs showing page loads, form starts, form completions, and time on page.
- A CRM or lead export with timestamps, contact details, and sales dispositions.
- A spreadsheet or BI tool to join those sources by click or session.
- Optional but useful: a client-side bot detection tool that captures behavioral evidence.
Preserve attribution before changing the campaign. Save the click identifier, campaign context, timestamp, URL parameters, CRM record, and any verification result before you switch anything off.
Diagnostic sequence: seven checks to separate bad leads from bots
Run these in order. Each check narrows the list. Stop only when you have enough evidence to act.
- Preserve attribution. Export campaign, ad set, creative, placement, click identifier, timestamp, URL parameters, and CRM records. You need this to compare clusters and, if needed, build a refund case.
- Compare ad clicks to landing-page sessions. Take link clicks in the ad platform and compare them with landing-page sessions in analytics. A large gap can mean bots, but first rule out app browsers, tracking consent, slow loads, and analytics configuration.
- Inspect session behavior. Check time on page, scrolling, mouse movement, field corrections, and click paths. Bots often have no scrolling, no field corrections, uniform click paths, and no meaningful time on the offer page.
- Measure form speed and structure. Forms completed immediately after landing, or faster than a person can type, are a classic sign. Also look for identical field structures across many submissions.
- Verify contactability. Call a sample of numbers, test the emails, and look for duplicate addresses, invalid domains, or an unusual concentration of one country code.
- Segment by placement, creative, device, and time. Look for sharp lead-quality differences by placement, creative, audience expansion, device, or landing page. Check for several leads arriving in short bursts or conversions concentrated at unusual hours.
- Compare CRM outcomes. Count calls connected, demos booked, qualified opportunities, and repeat engagement. A high reported lead count paired with no calls connected, demos booked, qualified opportunities, or repeat engagement is the strongest business-level signal.
One common mistake: jumping to fraud after one bad signal. A single fast form fill is not proof. Look for the cluster before you block anything.
Signals worth investigating
The table below summarizes the patterns to check and how to verify them.
| Signal | What it looks like | How to verify |
|---|---|---|
| Contactability | Disconnected numbers, invalid email domains, repeated addresses, one country code dominating | Call a sample, run deliverability checks, compare duplicates |
| Timing | Several leads in short bursts, forms submitted immediately after landing, conversions at unusual hours | Compare CRM timestamps to session start times |
| Session behavior | No scrolling, no field corrections, uniform click paths, no meaningful time on page | Use session replay or engagement events |
| Campaign patterns | Sharp quality difference by placement, creative, audience expansion, device, or landing page | Slice data by each dimension with enough volume |
| CRM outcome | High lead count but no calls connected, demos booked, qualified opportunities, or repeat engagement | Match leads to sales dispositions |
Key facts to keep in mind
These facts set the boundaries for a fair diagnosis.
| Fact | What it means for you |
|---|---|
| Invalid traffic includes both accidental interactions and intentionally fraudulent activity. | Not all invalid traffic is malicious. Some is just misclicks. |
| Meta divides traffic quality into valid and invalid. Valid traffic is human. Invalid traffic is automated interactions. | The platform already has a category for this. Your job is to find the sessions it missed. |
| Bots load pages but do not read, scroll, or convert. | Behavioral evidence is often the fastest way to tell a bot from a human. |
| Industry audits place automated traffic in a range that can reach 20% of paid clicks. | This is context, not proof for your account. Measure your own sessions. |
| A click-to-session gap can have ordinary explanations such as app browsers, tracking consent, slow loads, or analytics configuration. | Investigate those before concluding that the traffic is fraudulent. |
| Refunds from ad platforms usually require specific evidence for specific charges. | Preserve click IDs and session logs if you think you will file a claim. |
How to verify your fix
After you block a suspected source, watch the next 7 to 14 days. Ask two questions: Did contactable leads stay the same or improve? Did cost per qualified lead drop? If nothing changes, the traffic you blocked was not the real problem. Look again at offer, audience, or follow-up speed.
Limitations and when this advice does not apply
This diagnostic does not apply when you have not preserved click IDs or CRM dispositions. You can still spot clusters, but you cannot build a refund case without evidence.
Not every bad lead is a bot. A low-quality lead can be genuine but wrong for the offer. A suspicious session is a signal for investigation, not proof on its own.
Broad industry statistics are context. Imperva reported that automated traffic represented more than half of web traffic in 2025; that does not mean half of a Meta advertiser’s clicks are fraudulent. Measure your own account.
Server-side audits catch basic scraper bots but struggle to detect advanced botnets. Client-side audits analyze the visitor’s browser and capture the behavioral evidence you need, but they require adding a script to your site.
Avoid eliminating an entire audience from a small sample. Use enough volume to see a consistent quality pattern before you cut a placement.
Terminology you will meet
- Invalid traffic: clicks or impressions that are not the result of genuine user interest.
- Bot: automated software that loads pages, clicks ads, or submits forms.
- Click farm: paid workers who click ads to generate artificial publisher revenue.
- Pixel poisoning: bots trigger conversion events and corrupt the ad platform’s optimization data.
- Honeypot trap: a hidden or intentionally deceptive page element that humans never interact with. When a bot does, you know it is automated.
- Server-side audit: analysis of server logs, IP addresses, request headers, and user-agent data.
- Client-side audit: analysis of the visitor’s browser behavior, including movement, speed, and session patterns.
Frequently asked questions
How fast is too fast for a form fill? There is no universal threshold. A human may complete a short form in 20 seconds; a bot can do it in under a second. Compare completion time to your normal distribution. Superhuman input speed, under one millisecond, is a stronger signal.
Can a VPN or data-center IP prove bot traffic? No. A data-center IP is a clue, not proof. Real users use VPNs. Use IP as one input alongside behavior and CRM outcome.
Do Google or Meta automatically refund bot clicks? Sometimes, but not reliably. Google may issue invalid activity credits automatically in some cases. Refunds happen almost exclusively when an advertiser contests specific charges with specific evidence.
What is a honeypot trap? A hidden or intentionally deceptive page element that humans never see or interact with. When a bot interacts with it, you know the visitor is automated.
How many leads should I sample before excluding a placement? Enough to see a consistent quality pattern. Avoid eliminating an entire audience from a small sample. Compare placement-level quality across campaigns before deciding.
What is the difference between a cheap lead and a bad lead? A cheap lead may be a real person who is not ready to buy. A bad lead may be uncontactable or low-fit. A bot lead is automated and will never become a customer. Each needs a different response.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
How BotRefund can help
BotRefund detects non-human traffic on your site with behavioral checks: ghost click detection, honeypot traps, pointer movement, motion tremor, input speed, path shape, engagement, and session duration. It captures video proof for each flagged click so you can dispute invalid traffic with Google and Meta. It requires adding a script tag to your website, takes about one minute, and does not require ad-account access. It does not replace your CRM lead-quality audit; you still need sales dispositions to decide which leads matter.