Seatext library / BotRefund evidence
How to Use BotRefund to Verify Leads: A Step-by-Step Process
BotRefund verifies leads by installing a lightweight script on your landing pages, capturing 110+ behavioral and technical signals per session, and producing refund-ready reports that link suspicious activity to specific click IDs and campaigns....
✓ Built for advertisers who need clear, refund-ready traffic evidence.
To verify leads with BotRefund, add the tracking script to every page a paid visitor can reach, let it collect session data for at least one full traffic cycle, then open the dashboard to review sessions flagged as automated. Each flagged session includes a click ID, timestamp, placement, and a signal-by-signal explanation so you can suppress that conversion in Meta or Google Ads and attach the report to a refund request.
Prerequisites before you start
- Admin access to your website or tag manager to paste the BotRefund snippet in the
<head>. - Active Google Ads and/or Meta Ads accounts with auto-tagging (GCLID/FBCLID) enabled.
- Access to your CRM or lead spreadsheet to match BotRefund session IDs against real outcomes (calls connected, demos booked, revenue).
- A billing admin role on the ad platforms so you can file invalid-activity claims once you have the report.
Step-by-step implementation
- Create a BotRefund account and claim your free audit. The onboarding flow generates a unique JavaScript snippet.
- Install the snippet site-wide. Paste it into the
<head>of every landing page, thank-you page, and any intermediate step a paid click might touch. If you use Google Tag Manager, add it as a Custom HTML tag that fires on All Pages. - Verify the script is firing. Open the BotRefund dashboard → Live View → visit your own landing page via a test ad click. You should see your test session appear within seconds with a session ID and click ID attached.
- Run traffic for one full attribution window. Let the script collect data for at least 7–14 days (or one full campaign learning phase) so the AI has enough sessions to build a baseline.
- Open the Lead Quality report. The dashboard groups sessions by campaign, ad set, placement, and device. Sessions scored as automated show a confidence percentage, a list of triggered signals (e.g., superhuman input speed, missing mouse tremor, honeypot interaction), and a session replay link.
- Cross-reference with CRM outcomes. Export the flagged session IDs and match them to your lead records. Look for the patterns BotRefund highlights: disconnected phones, invalid email domains, burst arrivals, zero scroll depth, and no downstream CRM activity.
- Suppress bot conversions in the ad platforms. In Meta Events Manager or Google Ads Conversions, create a rule that excludes the flagged click IDs (GCLID/FBCLID) from conversion counting. This stops the bidding algorithm from optimizing toward fraudulent leads.
- Generate the refund-ready report. Use the “Export for Refund” button. The PDF/CSV includes click IDs, campaign hierarchy, timestamps, signal evidence, and session recordings formatted for Google and Meta review teams.
- File the invalid-activity claim. Attach the BotRefund report to a Google Ads Invalid Activity Credit request or a Meta Ads Refund Request. BotRefund’s historical 83% approval rate across 2,500+ audits comes from this evidence structure.
How BotRefund distinguishes bots from real visitors
BotRefund does not rely on IP reputation alone. It runs 110+ independent checks in the visitor’s browser — behavioral (mouse tremor, scroll variance, click timing), technical (canvas fingerprint, scrollbar width leak, clean-context iframe), and attribution (click ID presence, campaign consistency). A single anomaly is kept as evidence, not a verdict. The AI model weighs the complete pattern across browser, network, device, and behavior layers to reach up to 99% confidence when the session evidence supports it.
Key signals that trigger a bot flag
| Signal category | What it detects | Why it matters for lead verification |
|---|---|---|
| Pointer behavior | Robotic linear mouse movements, grid-aligned paths, absence of humanlike tremor | Real users exhibit micro-jitter; bots often move in straight lines or snap to coordinates. |
| Speed behavior | Superhuman input speed (<1 ms) | Form submissions faster than humanly possible indicate scripted fills. |
| Engagement behavior | Absence of clicks, scrolling, or meaningful time on page | Leads that never scroll or click cannot have read the offer. |
| Trap behavior | Honeypot trap interactions | Hidden fields only bots fill; a strong indicator of automated form submission. |
| Session behavior | Unnatural durations (too short, too long, too uniform) | Real sessions vary; bot sessions often cluster at identical lengths. |
| Attribution consistency | Missing or mismatched click IDs, placement-level spikes | Links the suspicious session to the exact paid click for refund claims. |
Common mistake: treating every bad lead as a bot
Not every unresponsive contact is automated. A weak offer, confusing form, or mismatched audience can produce real people who don’t convert. BotRefund’s workflow starts with a structured audit that compares ad-platform data, website sessions, and CRM outcomes before you change targeting or request a refund. Use the CRM-outcome column in the dashboard (connected calls, booked demos, qualified opportunities) to separate low-intent humans from automated traffic.
Verification step: confirm the next batch is clean
After you suppress the flagged click IDs and file the refund claim, keep BotRefund running. In the following week, check the Live View for new sessions from the same campaigns. The bot rate should drop toward zero. If it doesn’t, review whether the suppression rule caught all placements and whether new creative or audience expansion introduced fresh invalid sources.
Limitations and when this process does not apply
- BotRefund only observes traffic that reaches your landing page. It cannot detect invalid impressions or clicks that bounce before the script loads.
- The refund-ready report is accepted by Google and Meta review teams, but approval is at each platform’s discretion; BotRefund’s 83% historical success rate is not a guarantee.
- If you run lead-gen forms entirely inside Meta (Instant Forms) without a landing page, you cannot install the script there. You would need to drive that traffic to a page you control first.
- Enterprise pricing applies above $10,000/mo ad spend; smaller accounts use the self-serve tier with the same detection engine.
Terminology quick reference
- Click ID (GCLID/FBCLID): Unique parameter appended to your landing-page URL by Google Ads or Meta Ads when auto-tagging is on. Links a session to the exact paid click.
- Pixel poisoning: When bot conversions train the ad platform’s optimization algorithm to find more bots instead of buyers.
- Refund-ready report: A PDF/CSV export structured with the columns and evidence format Google and Meta reviewers expect for invalid-activity claims.
- Suppression rule: A platform-side filter that excludes specific click IDs from conversion counting so the bidding model stops optimizing for them.
FAQ
How long before I see flagged sessions?
First flagged sessions usually appear within hours of installing the script, but wait 7–14 days for a representative sample before filing a claim.
Does BotRefund block bots in real time?
No. It detects and reports. You use the report to suppress conversions in the ad platforms and request refunds. Real-time blocking would require a WAF or edge layer, which is a different job.
What if my CRM doesn’t store click IDs?
Add a hidden field to your forms that captures the GCLID/FBCLID from the URL query string. Most form builders and CRMs support this with a few lines of JavaScript.
Can I use BotRefund on client accounts as an agency?
Yes. The “For agencies” section in the dashboard lets you manage multiple client workspaces under one login and generate co-branded reports.
How much does it cost?
Self-serve plans start free for the audit tier. Paid tiers scale with monthly ad spend; enterprise pricing applies above $10,000/mo. Exact pricing is on the BotRefund pricing page.
What happens after I get a refund?
Keep the script installed. Ongoing monitoring prevents pixel poisoning from recurring and gives you fresh evidence if invalid traffic returns.
Does BotRefund work with TikTok, LinkedIn, or other ad platforms?
The detection engine works on any traffic that lands on your page, but the refund-ready report format and click-ID mapping are optimized for Google and Meta. For other platforms, you can still use the session evidence to build a manual claim.
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 verify leads
BotRefund installs a lightweight script that captures 110+ browser, behavioral, network, and attribution signals for every paid session. It scores each session, shows you the exact click IDs and signal evidence for automated traffic, and exports a refund-ready report formatted for Google and Meta review teams. You use that report to suppress bot conversions in the ad platforms and file invalid-activity claims. The detection engine reaches up to 99% confidence when the session evidence supports it, and historical data shows an 83% refund approval rate across 2,500+ audits. You need admin access to your site to install the script, auto-tagging enabled in your ad accounts, and CRM access to match session IDs to real outcomes. BotRefund does not block bots in real time — it gives you the evidence to stop paying for them and recover past spend.