Seatext library / BotRefund evidence
How to Use BotRefund to Measure Opportunity Rate: A Practical Guide
BotRefund measures opportunity rate by filtering bot and invalid traffic from your Meta and Google ad campaigns, then comparing verified human sessions against CRM outcomes like qualified leads, booked demos, and connected calls. The...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
Direct answer: what opportunity rate means in BotRefund
Opportunity rate is the share of paid clicks that turn into qualified sales conversations — connected calls, booked demos, or pipeline-ready leads. BotRefund calculates it by first removing automated and invalid traffic from your Meta and Google campaigns, then matching the remaining human sessions to your CRM results. The difference between platform-reported leads and CRM-qualified opportunities reveals how much budget was wasted on bots, scrapers, and low-intent clicks.
Why measuring opportunity rate changes budget decisions
Meta and Google report leads or conversions, but they cannot tell you which of those contacts your sales team can actually reach. When a campaign shows a steady cost per lead while the sales team sees disconnected numbers, copied messages, or enquiries that never progress, the gap is often invalid traffic. BotRefund's audit compares ad-platform data, website sessions, and CRM outcomes before you change targeting or request a refund. That comparison is the foundation of a reliable opportunity rate.
Prerequisites before you start
- Active Meta or Google Ads campaigns sending traffic to a landing page you control
- Access to the website's
<head>to install the BotRefund script (or tag-manager permission) - CRM or lead-tracking system that records call outcomes, demo bookings, or qualification stages
- Click IDs (GCLID, FBCLID) passed through your forms so sessions can be linked to pipeline data
Step-by-step process to measure opportunity rate with BotRefund
- Install the detection script. Add BotRefund's client-side snippet to your landing pages. It captures 110+ behavioral, browser, hardware, network, and attribution signals per session — including mouse tremor, scroll behavior, input speed, and iframe context checks.
- Run a baseline audit. Let traffic accumulate for 7–14 days without changing campaigns. BotRefund flags each session as human or automated with 99% confidence, preserving click IDs, timestamps, and session recordings.
- Export the refund-ready report. The report includes campaign, ad set, creative, placement, click identifier, and signal-by-signal reasoning in the format Google and Meta reviewers expect.
- Match verified human sessions to CRM outcomes. Join the report's click IDs to your CRM records. Count qualified opportunities (connected calls, booked demos, SQLs) divided by verified human clicks. That quotient is your opportunity rate.
- Compare against platform-reported metrics. Contrast the opportunity rate with Meta's or Google's reported lead count and cost per lead. The delta quantifies budget lost to invalid traffic.
- File refund claims where warranted. BotRefund's team formats the evidence, writes the claim, and supports negotiation with Google and Meta. Across 2,500+ audits, 83% of clients recover funds.
Key signals BotRefund uses to separate humans from bots
No single signal proves fraud. BotRefund cross-checks independent browser, network, device, and behavior evidence, then weighs the complete pattern with an AI prediction model. The table below summarizes the signal categories drawn from the source pack.
| Signal category | What it detects | Why it matters for opportunity rate |
|---|---|---|
| Contactability | Disconnected numbers, invalid email domains, repeated addresses, unusual country-code concentration | Flags leads that can never become opportunities |
| Timing | Burst arrivals, instant form submits, conversions at unusual hours | Identifies automated form-filling scripts |
| Session behavior | No scrolling, no field corrections, uniform click paths, no meaningful time on page | Reveals non-human navigation patterns |
| Campaign patterns | Sharp lead-quality differences by placement, creative, audience expansion, device, landing page | Pinpoints which traffic sources waste budget |
| CRM outcome | High reported leads but no calls connected, demos booked, qualified opportunities, repeat engagement | Directly measures the opportunity-rate gap |
| Biometric & behavioral | Mouse tremor, scrollbar width leak, clean context iframe, pointer linearity, superhuman input speed, grid-aligned movement | Provides session-level evidence for refund claims |
How to verify the measurement is working
After the first audit cycle, check three things: (1) the bot-flag rate aligns with known problem placements (e.g., Audience Network, Messenger inbox), (2) CRM-qualified opportunity count rises as a percentage of verified human clicks, and (3) the refund-ready report passes platform review without requests for additional data. If any check fails, review the signal breakdown for that placement and adjust suppression rules before the next claim cycle.
Limitations and when this approach does not apply
- Requires client-side script installation; cannot audit traffic on pages you do not control (e.g., instant forms hosted entirely on Meta).
- Measures opportunity rate only for click-based campaigns where a landing page visit occurs. View-through or impression-only conversions are outside scope.
- CRM matching depends on consistent click-ID pass-through. Broken UTM or parameter stripping breaks the link.
- Refund success depends on platform policy; BotRefund's 83% recovery rate is historical, not a guarantee.
Terminology quick reference
- Opportunity rate: Qualified sales opportunities ÷ verified human clicks from paid campaigns.
- Invalid traffic: Automated interactions (bots, scrapers, click farms, publisher scripts) that generate clicks but cannot convert.
- Pixel poisoning: Conversion pixels trained on bot events, causing the ad algorithm to optimize for more bot traffic.
- Refund-ready report: Evidence package formatted to Google and Meta's review specifications, including click IDs, timestamps, session recordings, and signal reasoning.
- Click ID (GCLID/FBCLID): Unique identifier appended to landing-page URLs that ties a session to a specific ad click.
FAQ
How long before I see a reliable opportunity rate?
Plan for 7–14 days of baseline traffic after script install. Shorter windows risk sampling noise; longer windows capture weekly placement cycles.
Does BotRefund block bots in real time or only report them?
It detects and reports with session-level evidence. Suppression of conversion events for flagged sessions is configured in your ad platform (e.g., Meta CAPI, Google Enhanced Conversions) using the exported click IDs.
Can I use this with server-side tracking only?
No. Server-side logs miss browser-level signals like mouse tremor, scroll behavior, and iframe context. BotRefund's 99% confidence comes from client-side corroboration across 110+ independent checks.
What if my CRM doesn't store click IDs?
Add a hidden field to your forms that captures the GCLID or FBCLID from the URL. Without it, you cannot join verified sessions to pipeline outcomes.
How does BotRefund differ from Cloudflare or WAF bot protection?
Edge providers protect infrastructure. BotRefund protects ad-spend measurement: it preserves attribution, observes the post-click journey, and produces marketing-ready evidence for refund claims. The two layers can coexist.
What does the free bot audit include?
A sample analysis of your traffic using the same 110+ signals, with a summary of bot percentage by campaign and placement. No contract required to start.
Can opportunity rate be measured for lead-gen forms hosted on Meta (Instant Forms)?
Not directly, because the form loads inside Meta's iframe where client-side scripts cannot run. Measure opportunity rate on your own landing pages; use the audit to inform targeting exclusions for Instant Form campaigns.
Key facts from BotRefund source pack
| Fact | Detail | Source |
|---|---|---|
| Detection confidence | 99% confidence in flagged bot traffic | S2 |
| Signal count | 110+ behavioral, browser, hardware, network, and attribution signals | S2 |
| Client base | 2,500+ brands audited | S2 |
| Refund recovery rate | 83% of clients recover funds from Google and Meta | S2 |
| Report format | Refund-ready with click IDs, campaign details, timestamps, session recordings, signal-by-signal reasoning | S2 |
| Case study result | FinTrust recovered $140,000, 14% bot click rate, +18% conversion rate increase | S8 |
| Budget impact | Bot clicks steal up to 20% of Google and Meta ad budget | S2 |
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.