Seatext library / BotRefund evidence
Signs Your Lead Quality Baseline Is Outdated (And What to Do About It)
Your lead quality baseline is outdated when your CRM outcomes consistently diverge from platform-reported metrics — such as steady cost per lead but declining contact rates, rising duplicate submissions, or conversion events with no...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
If your Meta Ads Manager shows a stable cost per lead but your sales team is calling disconnected numbers, getting copied messages, or seeing enquiries that never progress, your baseline is likely stale. The baseline is the set of normal rates you expect for sessions per click, contactable leads, verified leads, qualified opportunities, and revenue by campaign. When those rates shift without a corresponding change in targeting or creative, the baseline no longer reflects reality.
What a lead quality baseline actually measures
A baseline is not a single number. It is a profile of normal performance across five linked metrics: landing-page sessions per click, contactable leads, verified leads, qualified opportunities, and revenue attributed to each campaign. Before calling traffic fraudulent, calculate the normal rate for your account: landing-page sessions per click, contactable leads, verified leads, qualified opportunities, and revenue by campaign. This comes from the Meta CRM lead quality audit guide, which stresses that a low-quality lead can be genuine but wrong for the offer, while a suspicious session is a signal for investigation, not proof on its own.
You build the baseline by segmenting. Quality normally changes by placement, audience, creative, device, geography, landing page, and time. A sudden gap in one cluster is more useful than a site-wide average. Preserve the click identifier, campaign context, timestamp, URL parameters, CRM record, and any verification result before you change campaign settings.
Why baselines drift over time
Baselines drift for three main reasons. First, platform delivery changes: Meta may expand audience network placements, shift budget to new inventory, or alter how clicks are counted. Second, the threat landscape evolves: bot operators adopt new fingerprints, proxy networks rotate IPs, and click farms mimic human behavior more closely. Third, your own funnel changes: a new form, a different qualification step, or a revised sales disposition process alters what "good" looks like. If you last set the baseline six months ago, at least one of these has probably shifted.
Core signals your baseline no longer matches reality
The audit guide identifies five signal categories worth investigating. Treat each as a trigger to compare current data against your stored baseline.
- Contactability: disconnected numbers, invalid email domains, repeated addresses, or an unusual concentration of one country code.
- Timing: several leads arriving in short bursts, forms submitted immediately after landing, or conversions concentrated at unusual hours.
- Session behavior: no scrolling, no field corrections, uniform click paths, and no meaningful time on the offer page.
- Campaign patterns: a sharp lead-quality difference by placement, creative, audience expansion, device, or landing page.
- CRM outcome: a high reported lead count paired with no calls connected, demos booked, qualified opportunities, or repeat engagement.
When these signals appear together — for example, a placement shows normal click-through but zero contactable leads and session recordings show zero scroll — the baseline for that placement is effectively broken.
How to audit your current baseline: a four-layer workflow
The source pack outlines a practical investigation workflow that doubles as a baseline health check. Run these layers in order; each layer either confirms the baseline or isolates where it has failed.
Layer 1: 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. Avoid eliminating an entire audience from a small sample; use enough volume to see a consistent quality pattern.
Layer 2: Landing-page evidence
Measure page loads, redirects, consent behavior, form start, form completion, time to completion, and meaningful engagement. 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 gap is bot traffic.
Layer 3: 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. For high-value offers, a confirmation step or booking flow can be more valuable than the cheapest raw lead.
Layer 4: Sales outcome feedback
Give sales a small, mandatory set of dispositions: verified, contacted, qualified, disqualified, duplicate, invalid details, and no response. Feed those dispositions back into the baseline so the next cycle reflects what actually closed, not what the platform reported.
Common mistakes when interpreting baseline shifts
The most frequent error is treating every unresponsive contact as fraud. Not every bad lead is a bot, and that matters. Treating every unresponsive contact as fraud can make a team exclude a valuable audience. Another mistake is reacting to a single day's spike without checking whether the same placement showed the same pattern last month. A third is changing targeting or creative before preserving attribution — once you edit the campaign, you lose the clean click identifier needed to trace the bad leads back to their source.
When to reset vs. adjust your baseline
Reset the baseline when the underlying funnel has structurally changed: new offer, new form, new sales process, or a platform policy shift (for example, Meta removing a placement type). Adjust the baseline when the funnel is stable but quality has drifted — for instance, a gradual rise in invalid emails from a specific geography. In both cases, re-measure using the four-layer workflow and store the new baseline with a date stamp and the reason for the change.
Limitations of baseline monitoring
Baseline monitoring cannot distinguish sophisticated human fraud (click farms with real people) from genuine low-intent traffic. It also cannot catch bots that perfectly mimic human session behavior — though the BotRefund homepage notes their detection covers "ghost click detection," "honeypot trap interactions," "robotic linear mouse movements," "absence of humanlike mouse tremor," "superhuman input speed (<1ms)," "grid-aligned movement patterns," "absence of clicks or scrolling," and "unnatural session durations." Even with client-side detection, some advanced botnets may evade identification. Treat the baseline as a trigger for investigation, not a verdict.
Key facts
| Metric | Detail | Source |
|---|---|---|
| Baseline components | Sessions per click, contactable leads, verified leads, qualified opportunities, revenue by campaign | S6 |
| Segmentation dimensions | Placement, audience, creative, device, geography, landing page, time | S6 |
| Signal categories | Contactability, timing, session behavior, campaign patterns, CRM outcome | S1 |
| Audit layers | Platform delivery, landing-page evidence, lead verification, sales outcome feedback | S6 |
| Common mistake | Treating every unresponsive contact as fraud | S1 |
| BotRefund refund approval rate | 83% of customers successfully get a refund | S2 |
| BotRefund detection signals | Ghost clicks, honeypot traps, linear mouse paths, missing tremor, sub-millisecond input, grid-aligned movement, static sessions, unnatural durations | S2 |
FAQ
How often should I recalculate the baseline?
Recalculate after any structural funnel change (new form, new qualification step, new sales disposition set) and at minimum quarterly. If you see a persistent variance in one segment for two consecutive weeks, run the four-layer audit immediately.
What is the difference between a stale baseline and a bad campaign?
A bad campaign shows poor metrics across the board. A stale baseline shows a mismatch: platform metrics look normal but downstream outcomes have diverged. The baseline tells you what "normal" used to be; the audit tells you whether the campaign or the baseline is the problem.
Can I use industry benchmarks instead of my own baseline?
No. The audit guide explicitly warns: 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. Treat broad industry statistics as context, then measure the quality of your own sessions and leads.
What data do I need to preserve before changing a campaign?
Click identifier, campaign context, timestamp, URL parameters, CRM record, and any verification result. Without these, you cannot trace a quality drop back to a specific placement, creative, or audience.
How does bot traffic poison the baseline?
Bots that trigger conversion pixels create fake conversion events. This inflates reported conversion value and teaches Meta's optimization to target more bot-like users. The click fraud impact article notes that phantom conversions can make a 2:1 real ROAS appear as 4:1 in the dashboard.
When should I involve a detection tool like BotRefund?
When the four-layer audit shows consistent session-level anomalies (zero scroll, superhuman form speed, grid-aligned mouse paths) that you cannot explain by consent banners, slow loads, or app browsers. BotRefund's client-side audit captures video proof for each bot click and generates compliance-ready refund reports for Google and Meta disputes.
What is the typical refund recovery rate?
BotRefund reports an 83% approval rate across client refund claims submitted to ad platforms, with refunds recoverable on Google Ads spend dating back to 2017.
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.