Seatext library / BotRefund evidence
How to Calculate the Financial Impact of Blocking Fast Conversions That Might Be Legitimate
To quantify revenue risk from aggressive velocity filtering, multiply your false positive rate by average order value and monthly flagged conversions. Most advertisers lack direct false positive data, so start by auditing flagged sessions...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
Direct Answer: The Core Calculation
The financial impact of blocking fast conversions equals: false positive rate × average order value × monthly conversions flagged by velocity rules. If your velocity filter flags 500 conversions per month, your average order value is $120, and 3% of flagged conversions are legitimate customers, you risk $1,800 in monthly revenue. The challenge is measuring the false positive rate without letting fraud through.
Most platforms don't report false positives directly. You need to sample flagged conversions, verify human behavior (scrolling, mouse movement, field corrections, time on page), then extrapolate. BotRefund's client data shows 14% of clicks are invalid on average, but velocity rules targeting sub-second conversions catch a different subset — fast humans, not just bots.
Why Velocity Filtering Creates False Positives
Velocity rules block conversions that happen "too fast" — typically under 10–30 seconds from landing page to purchase. The logic: humans need time to read, compare, and decide. But legitimate fast conversions exist: returning customers with saved payment details, one-click buyers on mobile, shoppers who researched offline, and impulse purchases on low-consideration products.
BotRefund detects bots through superhuman input speed (<1ms), absence of humanlike mouse tremor, and grid-aligned movement patterns — not just raw speed. A human can complete a checkout in 8 seconds if they know exactly what they want. Blocking based purely on elapsed time catches these buyers.
Cost Drivers You Can Measure
Three variables determine the revenue at risk:
- Monthly flagged conversions — volume caught by your velocity threshold. Pull this from your fraud tool or analytics segment.
- Average order value (AOV) — use the AOV of flagged sessions specifically, not site-wide. Fast converters often buy different products.
- False positive rate — the percentage of flagged conversions that are legitimate. This is the hardest to measure and the most impactful.
Secondary costs include: wasted acquisition spend on customers you later block, pixel poisoning from rejected legitimate conversions (Meta/Google optimize for the wrong signals), and support tickets from confused buyers.
How to Measure Your False Positive Rate
Since no tool reports "false positive rate" directly, build it yourself:
- Export flagged sessions from your velocity filter for the last 30 days. Include session IDs, timestamps, and conversion values.
- Sample 100–200 sessions (or all, if volume is low). Review session recordings or behavioral logs for: scroll depth > 25%, mouse movement with natural curves, field corrections (backspacing, re-typing), time on product pages before checkout, and return visitor cookies.
- Classify each session as "likely human," "likely bot," or "uncertain." Be conservative — count uncertain as human for risk estimation.
- Calculate rate: (likely human + uncertain) ÷ total sampled. Apply this rate to the full flagged volume.
BotRefund's behavioral verification captures absence of clicks or scrolling, no field corrections, and uniform click paths as bot signals. Use these same criteria in your manual review.
Step-by-Step Calculation Framework
Follow this process monthly or when you change velocity thresholds:
- Define your velocity threshold (e.g., <15 seconds from landing to purchase confirmation).
- Pull flagged conversion count and total flagged revenue for the period.
- Run the manual review on a representative sample (minimum 100 sessions).
- Calculate false positive rate from the sample.
- Multiply:
false positive rate × flagged revenue = monthly revenue at risk. - Compare against fraud savings: estimated invalid clicks blocked × average CPC. BotRefund reports 20% of ad traffic is bots and 83% refund success rate for high-volume advertisers — but velocity rules only catch a fraction of that bot traffic.
- Adjust threshold if revenue at risk exceeds fraud savings, or if pixel poisoning risk outweighs both.
Trade-offs: Stricter vs. Looser Thresholds
There's no universal "correct" velocity threshold. The trade-off table below shows how threshold changes affect both sides:
| Threshold | False Positive Risk | Bot Catch Rate | Pixel Poisoning Risk | Best For |
|---|---|---|---|---|
| <5 seconds | Very high (returning mobile buyers, impulse) | Low (only crude bots) | High — legitimate fast converters excluded from training data | High-fraud verticals with low repeat purchase rates |
| 5–15 seconds | Moderate (some returning customers caught) | Moderate (catches basic automation) | Moderate | Most e-commerce; balance point for many |
| 15–30 seconds | Low (most humans take longer) | Higher (catches slower bots) | Low — pixel sees mostly genuine behavior | High-AOV, considered purchases; lead gen |
| >30 seconds | Very low | High (catches sophisticated bots) | Very low | Fraud-heavy campaigns; willingness to accept some false positives |
Takeaway: Start at 15 seconds. Measure false positives for two weeks. Tighten only if fraud savings clearly exceed revenue at risk.
Practical Scenarios (Hypothetical)
Scenario A: Fashion Retailer, $85 AOV, 2,000 Monthly Flagged at <10s
Manual review of 150 flagged sessions finds 8% are legitimate returning customers with saved Apple Pay. Monthly revenue at risk: 0.08 × $85 × 2,000 = $13,600. Fraud savings: estimated 400 bot conversions blocked × $1.20 CPC = $480. Velocity rule loses money. Loosen to 20s or add behavioral checks (scroll, mouse tremor) before blocking.
Scenario B: Lead Gen, $300 Lead Value, 300 Monthly Flagged at <15s
Review finds 3% false positives — mostly auto-filled forms by real users. Revenue at risk: 0.03 × $300 × 300 = $2,700. Fraud savings: 120 bot leads blocked × $25 CPL = $3,000. Rule breaks even. Add honeypot fields and scroll-depth checks to reduce false positives without loosening threshold.
Scenario C: Digital Goods, $15 AOV, 5,000 Monthly Flagged at <8s
Review finds 12% false positives — impulse buyers on mobile. Revenue at risk: 0.12 × $15 × 5,000 = $9,000. Fraud savings minimal (low CPC). Rule destroys margin. Remove velocity blocking; rely on behavioral bot detection instead.
Limitations and When This Advice Doesn't Apply
- No session recording or behavioral logs: You can't measure false positives without visibility into flagged sessions. Install client-side telemetry first.
- Velocity rules applied at payment gateway: Some gateways (Stripe Radar, Signifyd) block before you see the session. Request their false positive estimates or use their review queues.
- Subscription/recurring revenue: A blocked first payment loses LTV, not just AOV. Multiply by expected lifetime value.
- Brand damage: Legitimate customers blocked at checkout may not return. This cost is real but hard to quantify.
- Pixel poisoning is asymmetric: A few legitimate conversions excluded from pixel training hurts optimization more than a few bot conversions included. Prioritize pixel health over marginal fraud savings.
Key Facts from BotRefund Data
| Metric | Value | Source |
|---|---|---|
| Average invalid click rate across ad traffic | 14% | S7 |
| BotRefund-estimated bot share of ad traffic | 20% | S2 |
| Refund success rate for high-volume advertisers | 83% | S2 |
| Bot signals: superhuman input speed | <1ms | S2 |
| Bot signals: absence of humanlike mouse tremor | Detected via client-side telemetry | S2 |
| Bot signals: grid-aligned movement patterns | Detected via client-side telemetry | S2 |
| Bot signals: no scrolling, no field corrections, uniform click paths | Session behavior indicators | S5 |
| Bot signals: forms submitted immediately after landing | Timing indicator | S5 |
| Conversion events with no meaningful page engagement | Session behavior indicator | S5 |
FAQ
What's a typical false positive rate for velocity rules?
No universal benchmark exists — it varies by product type, customer base, and threshold. Hypothetical scenarios above show 3–12%. Measure your own using the sampling method. Industry averages for fraud tools overall range 1–5%, but velocity-specific data isn't published.
Should I use velocity rules at all?
Only if you can measure the false positive rate and confirm fraud savings exceed revenue at risk. Many advertisers get better results from behavioral bot detection (mouse movement, scroll depth, input speed) which catches bots without blocking fast humans.
How does blocking fast conversions affect Meta/Google pixel optimization?
Excluding legitimate fast converters from conversion signals teaches the pixel that fast converters don't exist. The algorithm then deprioritizes similar users. BotRefund warns that bot traffic poisoning makes Meta's machine learning optimize for bots rather than real buyers — but over-filtering legitimate conversions creates the opposite distortion.
Can I recover revenue from false positives after the fact?
Usually not. The customer has already left. Some fraud tools offer "review queues" instead of hard blocks — use these for velocity-flagged orders. Manual review adds friction but preserves revenue.
What's the difference between velocity filtering and behavioral bot detection?
Velocity filtering uses a single metric: time from landing to conversion. Behavioral detection analyzes dozens of signals (mouse paths, scroll patterns, input timing, device sensors). BotRefund uses client-side telemetry tracking millisecond timing of all referral cookies and behavioral patterns — not just speed.
How often should I recalculate the financial impact?
Monthly, or whenever you: change the velocity threshold, launch a new product line (different AOV), run a major promotion (different buyer behavior), or switch fraud vendors. Seasonal traffic changes (Black Friday, etc.) can shift false positive rates significantly.
What if I don't have session recordings?
Start with what you have: check if flagged sessions have referrer data, UTM parameters, return visitor cookies, or CRM match rates. Low match rates in CRM suggest bots; high match rates suggest false positives. Install behavioral tracking (BotRefund, Hotjar, FullStory) for future audits.
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.