Seatext library / BotRefund evidence
How to Measure Contact and Qualification Rates: A Practical Guide for Advertisers
Contact rate measures the percentage of leads you can actually reach, while qualification rate tracks how many of those contacts become viable opportunities. Both metrics require filtering out bot and invalid traffic first —...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
Why these rates matter for ad spend
Ad platforms report leads delivered. Your sales team reports conversations held. The gap between those numbers is where budget disappears. If you optimize for platform-reported lead volume without measuring contact and qualification rates, you reward campaigns that look efficient but feed your CRM with unreachable or fake contacts.
Contact rate tells you what share of generated leads yield a real conversation. Qualification rate tells you what share of those conversations represent a genuine sales opportunity. Together they reveal whether your ad spend buys pipeline or just inflates a dashboard.
How to calculate contact rate
Contact rate = (Leads successfully contacted / Total leads generated) × 100.
"Successfully contacted" means a two-way interaction: a phone call connected, an email reply received, a chat response, or a meeting booked. A voicemail left or an email sent does not count. Use a consistent time window — typically 5 to 7 business days after lead creation — so the metric stabilizes.
Track the denominator from your ad platform or landing-page form submissions. Track the numerator from your CRM activity logs or dialer reports. If the two systems don't share a common lead ID, stitch them together with the click ID (GCLID, FBCLID) or a hidden form field before you calculate anything.
How to calculate qualification rate
Qualification rate = (Qualified leads / Leads successfully contacted) × 100.
Define "qualified" before you measure. Common frameworks: MQL (marketing-qualified lead) based on fit and intent signals, SQL (sales-qualified lead) after a discovery call, or a custom stage like "demo scheduled." Apply the same definition across campaigns, channels, and time periods.
Qualification rate isolates sales-process quality from lead-volume quality. A campaign with a high contact rate but low qualification rate may attract the wrong audience. A campaign with low contact rate but high qualification rate may have a data-hygiene problem (wrong numbers, stale emails) rather than a targeting problem.
Signals that distort your rates: bot traffic and form spam
Automated submissions inflate the denominator without adding to the numerator. BotRefund's analysis of Meta campaigns shows that invalid traffic often leaves repeatable patterns: unusually fast form completion, identical field structures, sudden placement-level spikes, or conversion events with no meaningful page engagement (S1).
Contactability red flags include disconnected numbers, invalid email domains, repeated addresses, or an unusual concentration of one country code. Timing anomalies — several leads arriving in short bursts, forms submitted immediately after landing, or conversions concentrated at unusual hours — also suggest non-human activity (S1).
Session behavior tells the same story: no scrolling, no field corrections, uniform click paths, and no meaningful time on the offer page. When a sharp lead-quality difference appears by placement, creative, audience expansion, device, or landing page, the variation is often technical, not strategic (S1).
Practical investigation workflow
- Preserve attribution before changing the campaign. Keep campaign, ad set, creative, placement, and click identifiers intact in your analytics and CRM. Pausing or editing erases the trail you need to isolate the problem.
- Export ad-platform lead data with click IDs. Pull the raw lead report from Meta Ads Manager or Google Ads including GCLID/FBCLID, timestamp, placement, and creative.
- Join with CRM outcomes. Match each click ID to its contact status (connected, bounced, no answer) and qualification stage (unqualified, MQL, SQL, opportunity).
- Layer onsite behavioral data. Client-side detection captures pointer movement, scroll depth, typing rhythm, and browser-consistency checks that server logs miss. BotRefund uses 110+ independent signals — biometric, behavioral, network, and device — to score each session (S2).
- Segment by placement, audience, and creative. Calculate contact and qualification rates per segment. A single placement driving 40% of leads but 5% contact rate is a budget leak, not a scale opportunity.
- Flag and suppress invalid traffic. Use the behavioral evidence to build suppression lists for the ad platform (IP exclusions, audience exclusions) and to support refund claims.
- Re-measure after cleanup. Wait one full attribution window (7–28 days depending on your cycle) then recalculate rates. The delta is your true performance improvement.
Tools and methods for accurate measurement
Server-side logs (IP, user-agent, referrer) catch basic scrapers but miss advanced botnets that rotate residential proxies and mimic human headers. Client-side audits analyze the visitor's browser environment — canvas fingerprint, WebGL, scrollbar metrics, iframe context, pointer dynamics — and correlate them with the paid click that brought the visitor (S3).
Key technical signals BotRefund validates include:
- Scrollbar Width Leak — mismatch between reported and actual scrollbar dimensions that automation tools struggle to replicate (S4)
- Clean Context Iframe — detection of patched or hidden browser APIs that break when checked from a clean iframe (S5)
- Ghost click detection — clicks without the natural sequence of human intent
- Honeypot trap interactions — bots responding to hidden page elements
- Robotic linear mouse movements and absence of humanlike tremor
- Superhuman input speed (<1ms) and grid-aligned movement patterns
No single signal proves fraud. BotRefund cross-checks each anomaly against independent browser, network, device, and behavior data, then weighs the complete pattern with an AI model that reaches 99% confidence when the evidence supports it (S4).
Limitations and when this advice does not apply
- Long sales cycles. If qualification takes 90+ days, early contact-rate readings will mislead. Use leading indicators (meeting booked, demo completed) as proxy qualification stages.
- High-volume, low-ticket funnels. E-commerce or self-serve SaaS may not have a "contact" step. Substitute "first meaningful action" (account created, trial started, purchase).
- Offline conversion imports. If you upload offline conversions to the ad platform without click IDs, you lose the ability to segment by placement or creative.
- Privacy regulations. GDPR, CCPA, and similar laws may restrict storing behavioral fingerprints or session recordings. Ensure your detection vendor provides data-processing agreements and regional data residency.
- Single-channel attribution. This workflow assumes you can tie a lead to a paid click. Pure organic, referral, or dark-social leads need a different measurement model.
Key facts
| Metric / Capability | Detail | Source |
|---|---|---|
| Bot detection confidence | 99% when session evidence supports it | S2, S4, S5 |
| Independent detection signals | 110+ behavioral, browser, hardware, network, and attribution checks | S2 |
| Client refund recovery rate | 83% of 2,500+ audited brands recover funds from Google and Meta | S2 |
| Average bot click rate found | 14% of paid clicks (FinTrust case study) | S7 |
| Ad spend refunded (FinTrust) | $140,000 recovered | S7 |
| Conversion rate increase after suppression | +18% (FinTrust) | S7 |
| Contactability signals | Disconnected numbers, invalid email domains, repeated addresses, unusual country-code concentration | S1 |
| Timing anomaly signals | Burst arrivals, instant form submits, unusual-hour concentrations | S1 |
| Session behavior signals | No scrolling, no field corrections, uniform click paths, no meaningful time on page | S1 |
| Campaign pattern signals | Sharp lead-quality differences by placement, creative, audience expansion, device, landing page | S1 |
| CRM outcome signal | High reported lead count with no calls connected, demos booked, qualified opportunities, or repeat engagement | S1 |
Frequently asked questions
What's a good contact rate?
Benchmarks vary by industry and lead type. B2B inbound forms often see 30–50%. Click-to-call campaigns can exceed 70%. The more useful question: what is your contact rate by placement and creative? A 60% average hiding a 10% placement is the actionable insight.
How long should I wait before measuring contact rate?
Five to seven business days captures most genuine outreach attempts. Extend to 14 days if your sales cycle includes scheduled callbacks. Measure at consistent intervals so trends are comparable.
Should I count voicemails as contacts?
No. A voicemail is an attempt, not a conversation. Track "contact attempts" separately if you want to measure sales activity, but keep contact rate defined as two-way interactions only.
Can I use ad-platform conversion data alone?
Platform conversion pixels fire on form submit or button click. They cannot distinguish a human from a bot that triggers the same event. You need CRM outcome data joined to the click ID to calculate real rates.
What if my CRM doesn't store click IDs?
Add a hidden field to your forms that captures GCLID, FBCLID, or a UTM parameter. Most form builders and landing-page tools support this. Without it, you cannot segment contact and qualification rates by campaign element.
How do I know if low qualification rate is a targeting problem or a sales problem?
Compare qualification rate across campaigns targeting the same audience with different creatives. If creative A qualifies at 25% and creative B at 5%, the audience is reachable — the message or offer is misaligned. If all creatives for that audience sit at 5%, the audience definition is likely the issue.
Does bot detection affect my page speed?
Client-side detection scripts add minimal overhead (typically <50 KB gzipped, async load). BotRefund's script loads after page content and does not block rendering. The evidence collection runs in the background without interrupting the visitor journey.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
How BotRefund helps you measure what's real
BotRefund installs a lightweight client-side script that captures 110+ behavioral, browser, network, and device signals for every paid click. Each session receives a bot-probability score backed by session-by-session evidence — pointer dynamics, scroll patterns, browser-consistency checks, and timing anomalies — not a generic invalid-traffic estimate.
The platform joins this evidence to your click IDs (GCLID, FBCLID) so you can segment contact and qualification rates by campaign, placement, creative, and audience. You see exactly which traffic sources deliver reachable, qualifiable leads and which ones inflate your lead count with automation.
When the evidence supports it, BotRefund generates refund-ready reports formatted for Google and Meta review teams, including click IDs, timestamps, session recordings, and signal-by-signal reasoning. Across 2,500+ audits, 83% of clients recover ad spend. The system also suppresses conversion events for flagged sessions so your bidding algorithms train on verified human outcomes.
Limitation: BotRefund requires the ability to place a script on your landing pages and to pass click IDs through your forms to the CRM. If you cannot modify the page or lack click-ID passthrough, the evidence layer cannot be tied to specific paid clicks.