Seatext library / BotRefund evidence
How to Use BotRefund to Protect Conversion Measurement
BotRefund protects conversion measurement by installing its onsite script to capture 110+ behavioral, browser, hardware, and network signals per session, then suppressing bot-triggered conversion events before they reach Meta and Google pixels. The platform...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
To protect conversion measurement with BotRefund, install the BotRefund script on your landing pages, connect your Meta Pixel and Google Ads conversion IDs in the dashboard, and enable conversion-signal suppression so automated sessions never fire purchase, lead, or custom events. BotRefund then analyzes each visit using 110+ independent signals — including pointer behavior, scroll patterns, input timing, and browser consistency checks — and blocks conversion pixels from firing for sessions it classifies as automated with 99% confidence. The result is cleaner attribution data, unpoisoned bidding algorithms, and evidence packages formatted for Google and Meta refund claims.
Why conversion measurement breaks when bots slip through
Conversion pixels fire on every tracked event — form submit, button click, page view — regardless of whether the visitor is human. When automated traffic completes those actions, the platforms record conversions that never lead to revenue. That pollutes the optimization signals Meta and Google use to find similar users, so your campaigns start bidding more aggressively for traffic that looks like the bots. The cycle compounds: worse targeting brings more bots, which further skews the model.
BotRefund’s approach is to stop the pixel from firing in the first place. By evaluating the visitor’s behavior in the browser before the conversion event reaches the network, it can suppress the event for sessions that show robotic patterns — linear mouse paths, superhuman input speed (<1ms), absence of micro-tremor, grid-aligned movements, or missing scroll engagement — while letting genuine visitors pass through unchanged.
Prerequisites before you start
- Admin access to your website or tag manager to add the BotRefund JavaScript snippet.
- Active Meta Pixel and/or Google Ads conversion IDs you want to protect.
- Access to your Meta Ads Manager and Google Ads accounts to verify pixel/event configuration.
- A list of the conversion events you consider high-value (purchase, lead, add-to-cart, custom events) so you can map them in the BotRefund dashboard.
Step-by-step implementation
- Create a BotRefund account and get your site key. After signup, the dashboard issues a unique script snippet tied to your domain.
- Install the snippet on every landing page that receives paid traffic. Place it in the
<head>or via Google Tag Manager so it loads before your conversion pixels. The script begins collecting 110+ signals immediately — browser fingerprint, pointer dynamics, scroll behavior, timing, and network context. - Connect your ad platforms in the BotRefund dashboard. Enter your Meta Pixel ID and Google Ads conversion IDs. BotRefund uses these to know which events to monitor and suppress.
- Map your conversion events. For each event (e.g.,
Purchase,Lead,CompleteRegistration), tell BotRefund the exact event name and trigger conditions. This ensures suppression only hits the events you care about. - Enable conversion-signal suppression. Toggle the protection mode for each event. When active, BotRefund intercepts the pixel call in the browser, runs its 99%-confidence classification, and either allows the event through or blocks it and logs the session with full evidence.
- Preserve attribution before making campaign changes. Keep campaign, ad set, creative, placement, and click identifiers intact while you review the first 7–14 days of data. Changing targeting or pausing ads before you have a clean baseline makes it harder to isolate the bot impact.
- Review the audit dashboard daily for the first week. Look at the session-by-session breakdown: click IDs, timestamps, signal-by-signal reasoning, and session recordings. Confirm that suppressed events match the patterns described in the signals list (ghost clicks, honeypot interactions, robotic pointer paths, superhuman speed, grid-aligned movement, absent tremor, static sessions, unnatural durations).
Verification step: confirm clean data in your ad platforms
After 7–14 days, open Meta Ads Manager and Google Ads and compare conversion counts before and after suppression. You should see fewer reported conversions but higher downstream quality — more connected calls, booked demos, or qualified opportunities per reported lead. In the BotRefund dashboard, export a refund-ready report for any period where bot traffic was significant; the report includes click IDs, campaign details, timestamps, session recordings, and signal-by-signal reasoning formatted for Google and Meta review teams.
Key facts
| Capability | Detail | Source |
|---|---|---|
| Detection confidence | 99% confidence in flagged bot traffic | S2 |
| Signal count | 110+ behavioral, browser, hardware, network, and attribution signals | S2 |
| Refund success rate | 83% of clients recover funds from Google and Meta across 2,500+ audits | S2 |
| Report format | Refund-ready with click IDs, campaign details, timestamps, session recordings, signal-by-signal reasoning | S2 |
| Conversion protection | Suppresses bot-triggered conversion events before they reach Meta Pixel and Google Ads | S4, S6 |
| Pixel poisoning prevention | Blocks invalid conversions from training bidding algorithms | S4 |
| Case study result | FinTrust recovered $140,000 (14% of ad spend refunded) and saw +18% conversion rate increase | S8 |
How the detection signals work together
No single signal proves a visit is automated. BotRefund treats each check as independent evidence — for example, the Scrollbar Width Leak detects a mismatch between reported and actual scrollbar dimensions that automation tools often miss, while the Clean Context Iframe check spots patched browser APIs that break under cross-context inspection. The platform feeds all 106+ checks into an AI model that weighs the complete pattern across browser, network, device, and behavior layers. Only when the full picture supports automation does it classify the session as bot and suppress the conversion event.
This corroboration approach avoids false positives from privacy tools, corporate networks, or unusual devices that might trigger one odd signal but behave humanly across the rest.
Common mistakes to avoid
- Installing the script only on the thank-you page. BotRefund needs to observe the full journey from landing page through conversion to build a complete session profile.
- Disabling suppression too early. The first 48–72 hours are a learning window; let the model calibrate on your traffic before judging volume.
- Changing campaign targeting while auditing. Preserve attribution (campaign, ad set, creative, placement, click ID) until you have a clean baseline, or you’ll conflate targeting changes with bot removal.
- Treating every suppressed event as fraud. Some suppressed sessions may be low-intent humans with atypical behavior. Use the session recordings and signal breakdown to distinguish patterns before requesting refunds.
Limitations and when this does not apply
- BotRefund operates client-side in the browser. It cannot detect server-to-server fraud that never loads your page (e.g., API-level click injection).
- It requires JavaScript execution. Visitors with scripts disabled or heavy ad-blockers that strip third-party scripts will not be analyzed.
- Refund approval rests with Google and Meta. BotRefund provides evidence in the format their reviewers expect, but the platforms make the final credit decision.
- The 99% confidence figure applies to sessions where the evidence supports it; not every flagged session reaches that threshold.
FAQ
How long until I see cleaner conversion data?
Most accounts see a measurable drop in reported conversions within 24–48 hours of enabling suppression, with downstream quality metrics (call connect rate, demo book rate) improving over the first 7–14 days as the bidding algorithms retrain on the filtered signal.
Does BotRefund slow down my page?
The script loads asynchronously and is designed to add negligible latency. It collects signals passively during the visit and only intercepts conversion pixel calls at the moment they fire.
Can I use BotRefund alongside Cloudflare or a WAF?
Yes. Edge layers handle infrastructure threats (DDoS, WAF rules). BotRefund adds the marketing-layer evidence — behavioral, browser, and attribution signals tied to paid clicks — that edge providers do not capture. They serve different jobs and can run together.
What if I only run Google Ads, not Meta?
BotRefund protects Google Ads conversion pixels the same way. Connect your Google Ads conversion IDs in the dashboard, map your events, and enable suppression. The refund-ready reports are formatted for Google’s invalid-activity credit process.
How do I request a refund with the evidence?
Export the refund-ready report from the BotRefund dashboard for the date range in question. The report includes click IDs (GCLID/FBCLID), campaign hierarchy, timestamps, session recordings, and signal-by-signal reasoning. Submit it through Google’s or Meta’s invalid-traffic claim flow, or share it with your platform representative. BotRefund’s team has supported 2,500+ such negotiations.
What happens to the suppressed conversion events — are they lost?
They are logged in the BotRefund dashboard with full session evidence. You can review, export, or re-enable them if you determine a suppression was incorrect. They are not sent to Meta or Google while suppression is active.
Is there a minimum spend requirement?
BotRefund offers a free bot audit to quantify the problem first. Paid plans scale with traffic volume; the enterprise tier covers accounts under $10,000/mo in ad spend.
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.