botrefund.com

How BotRefund works under the hood without slowing your site or touching your design

How to add BotRefund to your website and properly configure it to achieve maximum results.

SECTION 01

Step 1: Creating your account and choosing your scope

Before adding any script, you choose your operational setup during account creation on login.seatext.com. Here is how the registration fork works visually, and how your selection determines which loader tier you receive.

Depending on your registration choice and plan, the platform provisions one of three loader delivery tiers. Select an option below to view when to choose it and copy its exact installation snippet:

Which installation should you choose? Click an option to see when it fits your website
Tier 1: Dedicated botrefund.js sensor (<6 KB passive script) Exempt from cookie banners • Zero DOM edits
✓ Choose this installation if:
  • You only want ad fraud refunds: You run Google, Meta, or TikTok ads and want to detect fake bot clicks, protect your ad budget, and generate refund claim dossiers.
  • You have strict DOM & checkout protection rules: Your engineering or brand team requires that third-party scripts never modify page HTML, styling, layout, or checkout funnels.
  • You don't want cookie consent popups: Operates strictly under GDPR Art. 6(1)(f) cybersecurity legitimate interest. Sets zero marketing cookies and collects zero PII.
✕ Do not choose this if:
  • You want SeaText AI growth tools: Automated full-site translation, AI CRO split testing, and visitor chat agents are permanently deactivated with this setup.
What gets installed: A lightweight <6 KB sensor (botrefund.js) that runs silently during browser idle periods with zero main-thread blocking.
Tier 1 script: botrefund.js (<6 KB gzip • add to <head>)
<!-- Tier 1: BotRefund Dedicated Sensor (Ad Fraud Defense Only, <6KB Gzip) -->
<!-- 1. Dynamic Fastly Edge Sensor (Cloaked against Adblockers) -->
<script src="https://fthhkh7iahqirmy6lu9vvp.edgecompute.app/botrefund.js" async></script>

<!-- 2. Universal CDN Direct Fallback (Hosted on Cloudflare R2) -->
<script src="https://cdn.seatext.com/botrefund.js?id=YOUR_PROJECT_ID" async></script>
SECTION 02

End-to-end detection lifecycle: The timeline waterfall

How BotRefund detects ad fraud step-by-step, from asynchronous loading in 0ms to edge verification in 10ms, kinetic human observation, and finalized refund evidence in 10-15 seconds.

Legacy anti-bot tools run monolithic client scripts that synchronously query browser APIs during page load, harming Core Web Vitals (LCP and INP). BotRefund replaces this with a chronological, asynchronous waterfall: lightweight micro-probes execute during browser idle cycles, network signatures are verified at the edge, and final decisions converge naturally as visitors interact.

T = 0 ms • Initial Page Load
0 ms CPU Blocking • No LCP Impact
1. Asynchronous and non-blocking sensor injection

The lightweight sensor (botrefund.js, <6 KB gzip) loads asynchronously with defer. Your HTML, CSS, fonts, and primary application code render instantly without waiting for BotRefund.

  • Zero Core Web Vitals impact: 0ms delay to First Contentful Paint (FCP) and Largest Contentful Paint (LCP).
  • Zero DOM mutation: Never alters page elements, never injects visible widgets, and never changes checkout layouts.
T + 10 ms • Edge Network Ingress
< 10 ms Edge Latency • 310+ Global PoPs
2. Edge TLS and TCP fingerprinting (Fastly / Cloudflare)

Before client code even finishes executing, our edge proxy inspects low-level network packets to catch sophisticated residential proxies and spoofed browser clients.

  • TLS Handshake Invariants: Natively extracts JA3 / JA4 client cipher fingerprints and verifies against genuine browser signatures.
  • HTTP/2 & HTTP/3 Multiplexing: Analyzes stream dependency trees, frame priority order, and TCP window header anomalies.
  • First-Party Edge Cloaking: Routes traffic through your first-party domain, guaranteeing 100% immunity against ad blockers and bypassing Safari ITP 7-day cookie caps.
T + 50-300 ms • Idle Browser Cycles
< 8 ms CPU Budget • Instant Pixel Defense
3. Headless browser and environment integrity micro-probes

Scheduled strictly via requestIdleCallback during idle frame intervals. Probes the browser environment to detect automated scrapers, emulators, and headless test runners.

  • Automation Framework Detection: Unmasks Puppeteer, Playwright, Selenium, and Chrome DevTools Protocol (CDP) overrides.
  • Hardware & GPU Invariants: Verifies unmasked WebGL GPU renderer strings, canvas anti-aliasing digests, and device memory consistency.
  • Immediate Conversion Pixel Defense (<12ms): If a confirmed automated bot is identified, ad conversion tags (Google Ads, Meta Pixel) are instantly suppressed in <12ms, stopping fake bot conversions from poisoning your ad bidding algorithms.
T + 1-10 s • Natural Interaction
Passive Listening • Zero PII Inspected
4. Biomechanical and kinetic human motion analysis

As a visitor navigates, passive listeners analyze organic human motion physics. Real humans produce natural micro-variations; bots produce mechanical straight lines or zero-second clicks.

  • Sub-Pixel Kinetic Physics: Evaluates mouse tremor entropy, gesture curvature torque, scroll momentum, and touch contact area.
  • Hardware Accelerometer Reading: Samples natural device tilt and Earth gravity vectors (~9.81 m/s²) on mobile devices.
  • Privacy Guarantee: Form fields, passwords, keystroke content, and user-typed text are strictly ignored and never read.
T + 10-15 s • Consensus & Verdict
1,500 ms Fail-Open Circuit Breaker
5. ML consensus: Ephemeral memory discard or sealed refund dossier

Our local ONNX machine-learning consensus engine evaluates a 25-feature normalized vector and routes the session to one of two final paths:

✓ Path A: Verified human visitor Ephemeral Memory Discard. Once human consensus is reached, all raw sensor readings are permanently deleted from volatile RAM within seconds. Zero PII is stored. GDPR Art. 6(1)(f) compliant.
✗ Path B: Confirmed bot click fraud Cryptographically Sealed Refund Dossier. Captures ad attribution tokens (gclid, fbclid, msclkid, timestamp, ASN, forensic triggers) ready for 1-click refund claims from Google & Meta.
SECTION 03

Choose what counts as a conversion

Start with the two free ways to define success. If you want Seatext to understand the whole page and identify conversion intent for you, activate the paid AI option when your plan allows it.

Site-wide vs. Page-Specific Configuration

You are editing conversion settings for the entire website. Select an individual page to inspect or fine-tune its conversion targets. Manage and test your live conversion configuration at login.seatext.com/welcome/conversion-settings.

Your conversion options

Use the free options for straightforward tracking. The paid option understands page intent and lets you fine-tune the targets it finds.

Option 01 • FREE No code required
Automatic detection
Recognise common events

Seatext watches for recognisable purchase, contact, sign-up, login, and form interactions. Get useful conversion counts without adding a marker or writing code.

✓ Common actions • Out-of-the-box tracking
Option 02 • FREE HTML or JavaScript
Manual conversion tracking
Define exactly what matters

Mark an important button, form, or success state yourself when your conversion has a custom business rule that automatic detection cannot see.

✓ You stay in control • HTML attribute or JS API
Option 03 • PAID AI 100% Free Agent
Let AI understand the page
High-intent conversion discovery

Paid AI reads the page structure and understands which buttons, forms, links, and flows represent real conversion intent—not ordinary navigation.

✓ Page-aware • AI-selected • Fine-tunable
Inspect & fine-tune a page
Choose a page to inspect in the visual editor or rebuild its conversion targets (e.g. 8 active targets • refreshed until 11/23/2026). Turn on the small switch in the blue card to activate AI analysis for the selected configuration scope.
Open Conversion Settings →

Manual implementation examples

Each example shows how to use Option 2 (Manual conversion tracking). One full-width example per row keeps every snippet readable and ready to copy.

1. For non-developers (WordPress, Wix, Shopify, Squarespace) Zero JavaScript required

Add seatextconversion to button text in WordPress, Wix, or Shopify. Visitors see only the normal button label:

In your editor:
<button>Buy Now seatextconversion</button>
Visitors see:
<button>Buy Now</button>
2. For developers (HTML data attribute & React components) HTML • JSX • Vue

Add data-seatextconversion to any button, form, link, or component that represents a completed conversion action:

HTML & React Component Attribute
<!-- Plain HTML -->
<button data-seatextconversion>Buy Now</button>

<!-- React / Next.js Component -->
<Button data-seatextconversion>Finish</Button>

<!-- Contact or Checkout Form -->
<form action="/submit" data-seatextconversion>
  <input type="email" name="email" required />
  <button type="submit">Start Trial</button>
</form>
3. Advanced JavaScript (SPAs, APIs, & Async Success Handlers) Programmatic API

Call the global method after a successful Single Page Application flow, fetch/Axios API response, or any custom business rule:

JavaScript Programmatic Call
// Simple programmatic conversion trigger:
window.seatextConversion();

// Example inside an asynchronous checkout or lead form handler:
async function handleCheckoutSuccess(order) {
  try {
    const response = await api.submitOrder(order);
    if (response.ok) {
      // Notify Seatext and record verified conversion
      if (typeof window.seatextConversion === 'function') {
        window.seatextConversion();
      }
      navigateToReceipt(response.orderId);
    }
  } catch (err) {
    console.error('Checkout error:', err);
  }
}
Implementation Tip: Unified Multi-Layer Tracking

Manual tracking works alongside automatic detection and paid AI targets, so you can make critical business events explicit while Seatext discovers other high-intent paths. If a confirmed bot triggers a conversion element, BotRefund's Pixel Guard blocks the ad platform pixel from receiving fake data while logging the fraud evidence for your refund claim.

SECTION 04

Runtime lifecycle and single-call teardown: seatext.destroy()

How to programmatically pause or tear down the sensor, flush in-flight telemetry to the server, and clean up all listeners in a single command.

When developing Single Page Applications (React, Vue, Angular, Svelte), testing user opt-out flows, or unmounting pages, you can cleanly stop all Seatext and BotRefund processes with a single global command.

It’s a single call: seatext.destroy()

Calling seatext.destroy() immediately recalculates dynamic biometrics, flushes the final bot detection verdict and session recording chunk to the server via navigator.sendBeacon (with keepalive fallback), disconnects all DOM MutationObservers, clears all background intervals/timers, detaches all passive biometric and Form Guard listeners, and sets Pixel Guard to PASSTHROUGH.

Single-Call Teardown Command
// It’s a single call to flush data and terminate all background processes:
seatext.destroy();

// Or call with an optional audit reason:
seatext.destroy({ reason: 'user_opt_out' });

// Also accessible on window or botrefund namespace:
window.seatext.destroy();
window.botrefund.destroy();

Alternative stop signals (Events & PostMessage)

In addition to the direct function call, both seatext.js and botrefund.js listen for stop commands across custom DOM events and cross-frame messages:

Trigger mechanism Code example Best used for
Single Programmatic Call seatext.destroy() SPA unmounting, user opt-out buttons, custom app logic.
Custom DOM Event window.dispatchEvent(new CustomEvent('seatext:stop')) Google Tag Manager (GTM), Consent Management Platforms (CMP).
Unified Stop-All Event window.dispatchEvent(new CustomEvent('seatext:stop-all')) Immediately stops both seatext.js and botrefund.js runtimes.
Cross-Frame PostMessage window.postMessage({ type: 'seatext:stop' }, '*') Embedded iframes, Chrome extensions, or web-worker communications.
SECTION 05

180+ detection vector taxonomy and ML model

An architectural breakdown of the biometric, execution environment, hardware, and network signals evaluated by BotRefund, combined with an ONNX machine learning consensus model.

Sophisticated click farms and automated scrapers easily bypass IP blacklists and user-agent checks using rotating residential proxies and stealth browser forks (Undetected Chromedriver, Puppeteer Stealth, Playwright). BotRefund inspects 180+ physical device invariants and behavioral entropy vectors grouped into four distinct forensic layers:

Forensic layer Signals analyzed Sample forensic flags Evasion trap mechanics
1. Biomechanical behavioral entropy Continuous passive sampling of sub-pixel mouse trajectories, Euclidean curvature variance, touch contact area & rotational torque deflection, 3-axis accelerometer micro-tremors ($~9.81 m/s^2$). MOUSE_ENTROPY_LOW EUCLIDEAN_STRAIGHT_VECTOR ZERO_LATENCY_SUBMISSION PHYSICAL_MOTION_MISSING Bots inject artificial clicks programmatically. Synthetic mouse events lack natural physiological hand tremors, yielding an entropy score < 0.15. Zero-movement submitters on desktop are flagged.
2. Execution environment and anti-stealth traps Chrome DevTools Protocol (CDP) runtime artifacts, window.cdc_ variables, console.debug eval leaks, Playwright/Puppeteer execution stubs, navigator.webdriver getter proxy traps, native function prototype bytecode lengths. CDP_DEBUGGER_LEAK WEBDRIVER_GETTER_TAMPERED PROTOTYPE_TOSTRING_PROXY EVAL_BYTECODE_MISMATCH When stealth frameworks mask navigator.webdriver = false via Object.defineProperty, BotRefund interrogates Function.prototype.toString.call() and V8 native string bytecode lengths (33 vs 37 bytes) to expose tampering.
3. Hardware and GPU topology integrity WebGL unmasked renderer string extraction, SwiftShader/llvmpipe software rasterizer detection, canvas 2D non-zero winding rule anti-aliasing digests, WebAudio oscillator phase drift & hardware clock discrepancies, font bounding box coherence. SWIFTSHADER_RENDERER CANVAS_WINDING_POISON AUDIO_CLOCK_DRIFT ZERO_PLUGINS_DESKTOP Server VMs running in AWS or Hetzner lack physical GPUs, falling back to SwiftShader software rendering. Canvas digests verify that sub-pixel font rasterization matches the claimed OS font tables.
4. L4/L7 network and infrastructure consistency L4 TCP SYN packet option fingerprinting (port 8443 pcap sniffing), TLS cipher suite ordering & JA3/JA4 MD5 hashes, HTTP/2 frame priority structures, tokenized authoritative DNS leak challenge matching resolver IP with HTTPS peer. DNS_LEAK_COUNTRY_MISMATCH TCP_SYN_TTL_ANOMALY PUBLIC_PROXY_LISTENER HEADER_HASH_DISCREPANCY Residential proxy evasion is exposed when the visitor's DNS resolution route traverses an ASN or country different from their HTTPS TCP peer, or when the TCP SYN initial TTL contradicts the client operating system.

Machine learning consensus architecture

Rather than relying solely on brittle static thresholds that attackers can reverse-engineer, BotRefund utilizes a calibrated ONNX Machine Learning Inference Engine running locally within our Go backend:

  • 25-Dimensional Normalized Feature Vector: Telemetry is condensed into a 25-feature tensor spanning mouse curvature variance, GPU vendor indices, audio buffer hashes, TCP window scales, and timing deltas.
  • Synergistic Dual-Engine Decision:
    1. Deterministic Heuristic Veto: Catches blatant automation markers (e.g. active CDP debuggers, SwiftShader renderers) with 100% precision.
    2. Trained Anomaly Classifier: Evaluates subtle, multi-variable correlation discrepancies across residential proxy clusters.
  • False-Positive Suppression (<0.01% Error Rate): Calibrated against hundreds of thousands of human sessions. Legitimate users on corporate VPNs or privacy browsers (e.g. Brave) produce natural biomechanical micro-tremors and consistent hardware tables, preventing false rejections.
SECTION 06

Data privacy, retention, and zero-PII invariant

Technical specification of our data handling invariants for Enterprise Security Councils and Data Protection Officers.

The zero-PII invariant: No personal data serialization

BotRefund is architected for zero personally identifiable information (Zero-PII). Client sensors inspect physical device hardware and biomechanical interaction physics only. The sensor never reads, serializes, or transmits form input values, passwords, credit card numbers, email addresses, or document text. Form input nodes are explicitly ignored in our DOM event listeners.

Technical data retention policies

Traffic classification Retention and storage lifecycle Technical rationale and legal basis
Verified human traffic
Legitimate website visitors
Ephemeral Volatile Memory Discard. All raw behavioral telemetry and hardware signals exist strictly in volatile RAM during the 10-15s voting window and are immediately discarded. Zero session recording or hardware profile is retained. Only an anonymized aggregate metric counter (total_clean_sessions + 1) is incremented for billing transparency and conversion rate reporting.
Confirmed malicious bots
Click fraud & automated scrapers
Cryptographically Sealed Forensic Dossiers. Detailed evidence (CDP flags, virtual GPU strings, robotic mouse vectors, timestamps, and ad tracking IDs such as gclid, fbclid, or msclkid) is preserved. Legally required to assemble certified audit-grade refund claim dossiers for ad networks (Google Ads, Meta Ads, Reddit Ads). Governed by GDPR Article 6(1)(f) "Legitimate Interest" (Recital 47 fraud prevention).

Regulatory and compliance standards

  • GDPR & CCPA Clean: Because BotRefund never builds cross-site marketing profiles, sells visitor data, or handles PII, it operates cleanly within EU and US privacy laws under GDPR Article 6(1)(f).
  • Exemption from Cookie Consent Banners: Dedicated BotRefund deployments (botrefund.js) do not set marketing tracking cookies or process PII, allowing operation without user cookie banner consent prompts.
SECTION 07

Security controls and fail-open resiliency SLA

Enterprise infrastructure controls, multi-tenant isolation, cryptographic encryption standards, and fail-open availability guarantees.

Security dimension Implementation architecture Audit status
Multi-tenant isolation Cryptographic project key namespacing (projectId). Telemetry beacons, API tokens, and dossiers are strictly partitioned. Cross-tenant access is structurally impossible. PASSED / PARTITIONED
Encryption in transit and rest Ingress endpoints enforce TLS 1.3 only with strict HSTS. Stored forensic bot dossiers are encrypted at rest with AES-256. PASSED / TLS 1.3 + AES-256
Stateless edge sandboxing Telemetry processed in memory-safe edge runtimes (Cloudflare Workers V8 isolates, Fastly Lucet/Wasm). Zero disk I/O; tokens capped at 120-second TTL. PASSED / V8 ISOLATES
Client execution sandbox Unprivileged, read-only browser execution. Cannot access cookies outside its own token, cannot touch localStorage outside _btr_*, executes zero remote eval(). PASSED / READ-ONLY
Fail-open resiliency SLA Hardcoded 1,500ms circuit breaker timeout. Dispatched via navigator.sendBeacon. If upstream network degradation occurs, sensor silently drops. Origin site rendering and checkouts are never blocked. PASSED / 100% FAIL-OPEN
SECTION 08

Enterprise proof of concept (POC) framework

A structured, risk-free four-stage evaluation model for enterprise engineering and performance marketing teams to validate detection accuracy before commercial commitment.

1

Stage 1: Shadow audit

Deploy the sensor in passive Shadow Mode. Operates silently in the background: zero blocking, zero CAPTCHAs, and 0ms main-thread degradation to establish baseline invalid traffic.

2

Stage 2: First 100 bots CSV

Export certified forensic logs containing exact ad click tokens (gclid, fbclid), click timestamps, ASN routing, and triggered technical flags (CDP leaks, virtual GPUs).

3

Stage 3: Ad refund claim

Submit the forensic evidence package to your Google Ads or Meta Ads representative (or use 1-click packet generator). Our customers achieve an 83% claim approval rate.

4

Stage 4: Active defense

Activate real-time conversion pixel defense to stop invalid clicks from firing ad network conversion pixels, defending Meta and Google smart bidding algorithms.

Technical due diligence and security evaluation matrix

Audit dimension BotRefund architectural guarantee Evaluation verdict
Main-thread performance Initial bundle <6KB gzipped. Execution chunked via requestIdleCallback with <8ms CPU budget. 0ms impact on Core Web Vitals (LCP, INP, CLS). PASSED / ZERO IMPACT
System availability and blast radius 100% fail-open design. Circuit breaker times out at 1,500ms. If BotRefund network times out, customer site functions normally with 0 error throw. PASSED / ZERO BLAST RADIUS
PII and privacy compliance Zero PII collected. Human traffic telemetry processed ephemerally in-memory and discarded. Forensic dossiers retained exclusively for confirmed ad fraud under GDPR Art. 6(1)(f). PASSED / GDPR & CCPA CLEAN
Adblocker and Safari ITP defense First-party edge proxies (Custom Cloudflare Worker developed by BotRefund, Fastly cluster) route through your own domain, bypassing ad blockers and Safari 7-day storage caps. PASSED / FIRST-PARTY IMMUNITY
False-positive mitigation Synergistic ensemble combining deterministic heuristic veto with 25-feature ONNX ML scoring and 10-15s biomechanical voting. False positive rate <0.01%. PASSED / <0.01% ERROR RATE
Content Security Policy (CSP) Strict CSP compliant. Requires only connect-src https://ingress.botrefund.com (or 'self' if using edge proxy). No unsafe-eval required. PASSED / STRICT CSP READY
DIRECT CTO & ENGINEERING DIALOGUE

Need a bespoke Cloudflare Worker or architecture consultation?

Our fraud forensics engineering team is available to review your routing architecture, provide custom Cloudflare Worker configs, or sign mutual non-disclosure and data protection agreements.