Seatext library / BotRefund evidence
How to Integrate BotRefund Detection Into Your Website
BotRefund integrates with a lightweight JavaScript snippet that you paste into your site's header. The script starts collecting browser, network, device, and behavioral signals immediately, and a free bot audit begins within minutes —...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
What BotRefund detection actually does
BotRefund is a bot detection and ad-refund platform that sits on your website and evaluates every visit using 106 independent checks. Those checks span hardware and GPU fingerprinting (such as WebGL texture constraints), biometric and behavioral interactions (impossible tab speed, window.open tamper, mouse tremor, click timing, pointer paths, honeypot traps), and session-level patterns (duration, engagement, scroll depth). Each signal is treated as evidence, not a verdict. The platform's AI prediction model weighs the complete pattern across browser, network, device, and behavior data to reach a 99% accuracy claim for distinguishing human from automated traffic.
The same detection layer also captures the click identifiers (GCLID, FBCLID) that Google Ads and Meta Ads attach to paid visits. When the AI flags a click as automated, BotRefund packages the evidence into audit-ready reports that you can submit to the ad platforms for refund disputes. The company says it has recovered spend dating back to 2017 and that bot clicks can consume up to 20% of a typical Google and Meta budget.
Key facts
| Fact | Details |
|---|---|
| Integration time | About one minute to add the script; no credit card required |
| Detection scope | 106 independent checks across hardware/GPU fingerprinting, biometric/behavioral interaction, and session patterns |
| Accuracy claim | 99% via AI model that cross-checks all signals rather than relying on single rules |
| Refund coverage | Google Ads and Meta Ads; claims supported back to 2017 |
| Typical bot-click share | Up to 20% of Google and Meta ad budget, per BotRefund |
| Free tier | Free bot audit starts automatically after installation |
| Pricing model | Tiered by monthly Google/Meta ad spend (under $10K, $10K–$50K, $50K–$250K, $250K–$1M, $1M–$5M, over $5M) |
| Case study result | FinTrust (neobank) recovered $140,000, saw 14% average bot click rate, +18% conversion rate increase |
Prerequisites before you start
- Access to your site's
<head>section or a tag manager (Google Tag Manager, Tealium, etc.) so you can paste a JavaScript snippet. - Admin rights in your Google Ads and/or Meta Ads accounts if you want BotRefund to pull click IDs (GCLID/FBCLID) automatically for refund claims.
- A rough idea of your monthly Google and Meta ad spend — this determines the pricing tier and the volume of data the audit will analyze.
Step-by-step integration process
- Create a BotRefund account. Go to the BotRefund homepage and click "Get my free bot audit." Fill in your name, work email, website URL, and monthly Google/Meta spend range. No credit card is asked for at this stage.
- Receive the installation snippet. After the form submits, the dashboard displays a short JavaScript tag (typically a single
<script>line with a unique site key). Copy it. - Paste the snippet into your site's
<head>. If you edit code directly, place it before the closing</head>tag. If you use Google Tag Manager, create a new Custom HTML tag, paste the snippet, set the trigger to "All Pages," and publish. - Verify the script loads. Open your site in an incognito window, open DevTools → Network, filter for "botrefund" or the script name, and confirm a 200 response. The dashboard will also show "Script active" within a few minutes.
- Connect ad accounts (optional but recommended). In the BotRefund dashboard, follow the OAuth flows for Google Ads and Meta Ads. This lets the platform automatically match detected bot clicks to GCLID/FBCLID values and pre-fill refund dispute reports.
- Let the free audit run. BotRefund begins scoring live traffic immediately. The audit typically surfaces a bot-click rate, estimated wasted spend, and a sample of flagged sessions with video-style replay evidence within the first 24–48 hours.
- Review and act. If the audit shows meaningful bot traffic, you can either stay on the free tier (detection only) or upgrade to a paid tier to unlock automated refund filing, pixel-poisoning protection, and dedicated escalation support.
Verification and testing
After the script is live, do a quick sanity check:
- Visit your own site and confirm the BotRefund cookie or localStorage key appears (usually prefixed
brf_). - Trigger a known bot-like behavior — for example, run a headless Chrome script that loads the page and clicks a button in <1 ms. The dashboard should flag the session as automated within a few minutes.
- Check that GCLID/FBCLID parameters from your test ad clicks appear in the session detail view. This confirms the ad-account linkage works.
If the script loads but no sessions appear after 30 minutes of real traffic, re-check the tag placement (it must fire on every page, not just the landing page) and ensure no Content Security Policy directive blocks the BotRefund domain.
Common integration mistakes
- Placing the snippet only on landing pages. BotRefund needs to see the full session — including post-click navigation — to evaluate behavioral signals like scroll depth, mouse tremor, and session duration. Install site-wide.
- Blocking the script with an overzealous CSP. Add
https://*.botrefund.com(or the exact domain shown in your snippet) to yourscript-srcandconnect-srcdirectives. - Skipping ad-account connection. Without GCLID/FBCLID capture, you still get detection, but you lose the one-click refund report generation that makes the paid tiers worthwhile.
- Assuming the free audit equals full protection. The free tier shows you the problem; paid tiers add real-time suppression (blocking conversion pixels for flagged clicks), automated dispute filing, and SLA-backed escalation with ad-platform reps.
Limitations and when this advice does not apply
- BotRefund is built for websites running Google Ads and/or Meta Ads campaigns. If your paid traffic comes exclusively from other sources (TikTok, LinkedIn, programmatic DSPs without click-ID pass-through), the refund workflow will not work.
- The 99% accuracy figure is a platform claim based on internal validation; independent third-party benchmarks are not published in the source pack.
- Integration via a single JavaScript snippet works for most CMSs (WordPress, Shopify, Webflow, custom stacks). Single-page apps with heavy client-side routing may need an extra
router.pushlistener to ensure the tracker re-initializes on virtual page views — check the developer docs for the exact event name. - Enterprise contracts (over $1M/mo spend) involve a sales call, custom SLA, and possible on-premise data-residency options. The self-serve flow described above covers tiers up to $1M/mo.
FAQ
How long until I see results in the dashboard?
Live sessions appear within minutes of the script firing. The first audit summary (bot-click rate, estimated waste, sample flagged sessions) usually populates after 24–48 hours of normal traffic volume.
Does the script slow down my site?
The snippet is asynchronous and under 30 KB gzipped. BotRefund states it adds negligible load time; no independent Core Web Vitals impact data is provided in the source pack.
Can I use BotRefund alongside Cloudflare Bot Management or reCAPTCHA?
Yes. BotRefund operates at the application layer and focuses on post-click ad-traffic verification. It does not replace WAF-level bot mitigation or CAPTCHA challenges.
What happens if I cancel a paid plan?
Detection continues on the free tier (audit only). Real-time suppression, automated refund filing, and escalation support stop at the end of the billing period.
Is there a WordPress plugin or Shopify app?
The source pack does not mention a dedicated plugin or app. The standard method is pasting the JavaScript snippet into the theme header or via a tag manager.
How are refund disputes actually submitted to Google and Meta?
BotRefund generates PDF/CSV audit reports with click IDs, timestamps, behavioral evidence, and the AI confidence score. You (or their team on higher tiers) upload those reports through the platforms' standard invalid-click dispute forms.
What if my site uses a strict Content Security Policy?
Add the BotRefund script domain to script-src and the API endpoint to connect-src. The exact domains are shown in your dashboard after account creation.
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.