Seatext library / BotRefund evidence
Which Engagement Signals Should I Include in My Lead Quality Baseline?
Start with five signal groups: contactability checks, timing patterns, on-page session behavior, campaign-level quality splits, and CRM sales outcomes. Together they separate real prospects from bots and low-intent clicks without relying on any single...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
If you are building a lead quality baseline for Meta campaigns, include signals from five categories: contactability (valid emails, reachable phones, duplicate details), timing (burst arrivals, instant form submits, odd-hour conversions), session behavior (no scrolling, zero field corrections, uniform click paths, no meaningful time on page), campaign patterns (quality gaps by placement, creative, audience expansion, device, or landing page), and CRM outcomes (high lead count but zero calls connected, demos booked, or qualified opportunities). No single signal proves fraud; the baseline works because the signals reinforce each other.
What a lead quality baseline is and why engagement signals matter
A lead quality baseline is the set of measurable behaviors and outcomes that define "normal" for your account before you label traffic as suspicious. Without it, you risk treating every unresponsive contact as fraud and cutting off valuable audiences, or you miss bot traffic that mimics real leads just well enough to poison your pixel. The baseline gives you a reference point so you can spot clusters that deviate — placement A delivers 40% contactable leads while placement B delivers 5% — and investigate before you change targeting or request refunds.
Meta campaigns reach people across Facebook, Instagram, and the Audience Network at high volume. That reach brings accidental clicks, low-intent traffic, automated browsing, and deliberate form spam. A weak campaign can attract real people who aren't ready to buy; bot traffic leaves repeatable technical and behavioral patterns. The distinction is evidence.
Core engagement signal categories from platform and CRM data
The source material identifies five signal groups that together form a practical baseline. Each group answers a different question about the lead.
1. Contactability signals
These tell you whether the lead can actually be reached. Look for disconnected phone numbers, invalid email domains, repeated addresses, and unusual concentrations of a single country code. A lead with a fake email or a dead phone line is either a typo, a low-intent submission, or a bot. Track the percentage of leads that pass basic deliverability checks per campaign and placement.
2. Timing signals
Timing reveals automation and low intent. Several leads arriving in short bursts, forms submitted immediately after landing, or conversions clustered at unusual hours (e.g., 3–5 AM in the target timezone) suggest scripts or click farms. Real humans rarely complete a form in under five seconds or all arrive within the same minute.
3. On-page session behavior
Session behavior is the strongest indicator of human presence. Signals include no scrolling, no field corrections (backspacing, re-typing), uniform click paths (every visitor hits the same elements in the same order), and no meaningful time on the offer page. BotRefund's client-side detection flags 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. These are captured in the browser, not the server log, so they catch advanced bots that rotate IPs and user agents.
4. Campaign pattern signals
Quality normally changes by placement, creative, audience expansion, device, geography, and landing page. A sharp lead-quality difference in one cluster — for example, Audience Network placements delivering high click-through rates but near-instant bounce rates — is more useful than a site-wide average. Preserve the click identifier, campaign context, timestamp, URL parameters, and CRM record before you change settings.
5. CRM sales outcome signals
The ultimate truth lives in the CRM. A high reported lead count paired with zero calls connected, demos booked, qualified opportunities, or repeat engagement means the leads aren't converting. Give sales a small, mandatory set of dispositions: verified, contacted, qualified, disqualified, duplicate, invalid details, no response. Feed those dispositions back to the platform so the algorithm learns from real outcomes, not just form fills.
Trade-off table: signal groups compared on implementation effort, reliability, and what they catch
| Signal group | Implementation effort | Reliability for bot detection | Primary blind spot | Best used for |
|---|---|---|---|---|
| Contactability | Low – email/phone verification APIs, CRM deduplication | Medium – catches fake details but not real people with low intent | Real humans who give real info but never buy | Filtering obvious spam before it reaches sales |
| Timing | Low – timestamp analysis in CRM or analytics | Medium – bursts and instant submits are strong indicators but can occur with viral content | Slow bots that mimic human pacing | Spotting automated bursts and click-farm patterns |
| Session behavior (client-side) | Medium – requires JavaScript tracker on landing page | High – catches advanced bots that evade IP/user-agent filters | Privacy/consent blockers may reduce coverage | Detecting non-human interaction patterns at the browser level |
| Campaign patterns | Low – segmentation in Ads Manager and CRM | Medium – reveals where quality drops but not why | Doesn't distinguish bot from low-intent human | Prioritizing which placements/audiences to audit first |
| CRM sales outcomes | Medium – requires sales process discipline and feedback loop | Highest – ground truth on whether a lead becomes revenue | Lag time; needs volume to be statistically meaningful | Training the algorithm and calculating true ROAS |
Takeaway: Start with contactability, timing, and campaign patterns — they need no extra code. Add client-side session tracking when you have budget for a tracker. Close the loop with CRM dispositions as soon as sales can adopt a simple dropdown.
Decision framework: choosing the right signals for your stage
- Week 1 – Baseline with existing data. Pull the last 90 days of leads. Calculate contactable rate, verified rate, qualified rate, and revenue per campaign/placement/device. Flag any cluster where contactable rate drops below your account median by >20 percentage points.
- Week 2 – Add landing-page evidence. Measure page loads, redirects, consent acceptance, form start, form completion, time to completion, and meaningful engagement (scroll depth >25%, >10 seconds on page). A click-to-session gap often has ordinary causes: in-app browsers, consent banners, slow loads, analytics misconfiguration. Rule those out first.
- Week 3 – Deploy client-side behavioral tracking. Install a lightweight script that captures pointer behavior, speed behavior, motion behavior, path behavior, engagement behavior, and session behavior. This is where you catch bots that look human on the server side but move like machines in the browser.
- Week 4 – Close the CRM feedback loop. Require sales to set a disposition on every lead within 48 hours. Map dispositions back to click IDs. Use the verified/qualified subset as your conversion signal for optimization and refund claims.
- Ongoing – Re-baseline quarterly. Seasonality, creative refreshes, and platform changes shift the baseline. Recalculate medians every quarter and adjust investigation thresholds.
Key facts from BotRefund source material
| Fact | Detail | Source |
|---|---|---|
| Average invalid click rate | 14% of clicks are invalid on average across BotRefund clients | S6 |
| ROAS improvement after cleaning traffic | Advertisers see 40–60% improvement in true ROAS within 6–8 weeks | S6 |
| Refund success rate | 83% of BotRefund customers successfully get a refund from Google or Meta | S2 |
| Client-side detection behaviors | Ghost clicks, honeypot traps, robotic mouse movement, missing tremor, superhuman speed (<1ms), grid-aligned paths, no clicks/scrolling, unnatural session durations | S2 |
| Four-layer audit structure | Platform delivery → Landing-page evidence → Lead verification → Sales outcome feedback | S5 |
| Mandatory sales dispositions | Verified, contacted, qualified, disqualified, duplicate, invalid details, no response | S5 |
| Audience Network risk | High CTRs and near-instant bounce rates; publishers use bots to generate artificial revenue | S3 |
| Google invalid activity signals | Rapid clicking, duplicate clicks, known bad IPs, data center traffic, accidental mobile taps, competitor click fraud | S7 |
Limitations and when this advice does not apply
- Low volume accounts. If you get fewer than 200 leads per month per campaign, cluster analysis by placement or creative will be noisy. Aggregate longer time windows or group similar placements.
- Brand awareness campaigns. If the goal is reach, not leads, engagement signals like form completion speed are irrelevant. Use view-through and brand lift metrics instead.
- Offline conversion imports only. If you don't have a landing page with a form (e.g., click-to-call, click-to-message), session behavior signals aren't available. Rely on contactability, timing, and CRM outcomes.
- Strict consent regimes. In regions where analytics and behavioral scripts require explicit consent, client-side coverage may drop below 50%. Server-side signals become primary.
- Single-channel advertisers. This baseline assumes Meta (Facebook/Instagram/Audience Network). Google Ads, TikTok, LinkedIn, and programmatic have different placement structures and fraud vectors.
Terminology quick reference
- Click ID (GCLID/FBCLID): Unique identifier appended to the landing-page URL by the ad platform. Preserve it to tie a session back to the exact click, campaign, and placement.
- Pixel poisoning: When bot traffic triggers conversion events, the platform's machine learning optimizes for more bot-like users.
- Client-side audit: Behavioral analysis running in the visitor's browser (JavaScript). Captures mouse movement, scroll, timing, and interaction patterns that server logs miss.
- Server-side audit: Analysis of IP, user agent, headers, and request logs. Catches basic scrapers but struggles with residential proxy botnets.
- Disposition: A standardized sales outcome label (verified, contacted, qualified, etc.) used to feed ground truth back to the ad platform.
- Invalid activity credit: Google's automatic or claimed reimbursement for clicks deemed non-genuine. Not automatic for all fraud types.
FAQ
How many signals do I need before the baseline is useful?
Three is the practical minimum: contactability, timing, and one campaign-pattern split (usually placement). Add session behavior and CRM dispositions as you can. A baseline with one signal is a guess; with three it's a filter.
What if my CRM doesn't track click IDs?
Add a hidden field to your form that captures the FBCLID/GCLID from the URL. Most form builders and CRM integrations support this. Without it, you can't tie a sales outcome back to the specific click that generated the lead.
Can I use Google Analytics engagement metrics instead of client-side bot detection?
GA4 engagement rate, scroll depth, and average engagement time are helpful proxies, but they aggregate sessions and can't flag individual bot visits. Client-side detection produces a per-session verdict and video evidence for refund claims.
How do I know if a quality drop is bots or just a bad audience?
Check the session behavior signals. Real humans in a bad audience still scroll, correct typos, and spend variable time on page. Bots show uniform paths, zero corrections, superhuman speed, or no mouse tremor. If the session looks human but the lead is unqualified, it's an audience/targeting problem.
When should I request a refund vs. just exclude the placement?
Exclude first. If the placement shows client-side bot evidence (ghost clicks, honeypot hits, robotic movement) and you have preserved click IDs and behavioral logs, file a refund claim with that evidence. BotRefund clients average 83% approval when they submit forensic reports.
Does the baseline change for e-commerce vs. B2B lead gen?
The signal groups stay the same; the thresholds shift. E-commerce cares about add-to-cart and purchase events; B2B cares about verified contact, demo booked, and pipeline stage. Use the same four-layer audit but map the CRM dispositions to your funnel stages.
What's the fastest way to start if I have no tracking in place today?
Export the last 90 days of leads from your CRM. Add columns for: email deliverable (yes/no), phone connected (yes/no), duplicate (yes/no), time from click to form submit, placement, device. Pivot by placement. The worst-performing placement is your investigation starting point. Install a free bot audit script (BotRefund offers a one-minute install) to get session behavior data on new traffic immediately.
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.