Seatext library / BotRefund evidence
How to Use BotRefund to Review Traffic Consistently: A Step-by-Step Process
BotRefund reviews traffic consistently by installing its onsite script, connecting ad accounts, and running scheduled audits that combine 110+ behavioral and technical signals into refund-ready reports. The platform cross-checks each signal across browser, network,...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
To review traffic consistently with BotRefund, install the tracking script on your landing pages, link your Google and Meta ad accounts, and set a recurring audit schedule. The system collects click IDs, timestamps, session recordings, and 110+ independent signals — such as scrollbar width leaks, clean-context iframe mismatches, robotic mouse paths, and superhuman input speed — then cross-references them through an AI model that only flags a visit as bot traffic when the full pattern supports it at 99% confidence. Each audit produces a refund-ready report structured for Google and Meta review teams, so you can file claims without translating raw logs.
Prerequisites before the first audit
- Website access: Ability to add a JavaScript snippet to every landing page that receives paid traffic.
- Ad account permissions: Admin or standard access on the Google Ads and Meta Ads accounts you want to monitor, so BotRefund can pull click IDs (GCLID, FBCLID) and campaign metadata.
- Conversion events defined: Clear mapping of which onsite actions (form submit, purchase, sign-up) count as conversions, so the platform can suppress bot-triggered events and protect pixel training data.
- Team ownership: One person responsible for reviewing the weekly or bi-weekly report and initiating refund requests.
Step-by-step implementation
- Create a BotRefund account and start the free bot audit. The initial scan establishes a baseline bot rate across your paid campaigns.
- Install the onsite script. Paste the provided snippet into the
<head>of every landing page. The script begins collecting behavioral, browser, hardware, network, and attribution signals immediately. - Connect ad platforms. In the dashboard, authorize Google Ads and Meta Ads access. This links each session to its originating click ID, campaign, ad set, creative, and placement.
- Configure conversion protection. Select the conversion events you want BotRefund to monitor. The platform will suppress automated events so Google and Meta optimization algorithms train only on verified human actions.
- Set the audit cadence. Choose weekly or bi-weekly automated reports. Each run preserves attribution data before any campaign changes, a practice the Meta invalid-traffic guide recommends.
- Review the first report within 48 hours. Verify that click IDs, timestamps, and session recordings align with your CRM outcomes (e.g., connected calls, booked demos). Flag any discrepancies for the next claim cycle.
- File refund claims using the generated reports. BotRefund formats evidence — click IDs, campaign details, signal-by-signal reasoning — in the structure Google and Meta reviewers expect. Submit through each platform's invalid-activity or invalid-traffic claim flow.
- Track claim outcomes and adjust. Record approval rates and refunded amounts. Over 2,500 audits, BotRefund clients have seen an 83% success rate recovering funds.
Key signals BotRefund evaluates every session
Consistency comes from the breadth of independent checks. No single signal triggers a verdict; the AI model weighs the complete pattern. Representative checks include:
- Scrollbar Width Leak: Detects mismatches between reported and actual scrollbar dimensions that automated browsers often reveal.
- Clean Context Iframe: Flags when browser APIs behave differently inside an iframe, a common artifact of automation tools patching or hiding APIs.
- Ghost Click Detection: Catches click activity that occurs without the natural sequence of human intent.
- Honeypot Trap Interactions: Watches for bots that respond to hidden or deceptive page elements.
- Robotic Linear Mouse Movements: Flags unnaturally straight pointer paths rarely seen in real sessions.
- Absence of Humanlike Mouse Tremor: Looks for the tiny imperfections and jitter typical of human movement.
- Superhuman Input Speed (<1ms): Identifies interactions faster than a person could realistically perform.
- Grid-Aligned Movement Patterns: Detects movement snapping to precise lines or blocks instead of natural curves.
- Absence of Clicks or Scrolling: Highlights sessions that stay too static to match a real browsing journey.
- Unnatural Session Durations: Catches visit lengths that are too short, too long, or too uniform to be human.
Each signal adds one objective fact. BotRefund cross-checks it against independent browser, network, device, and behavior data before the AI prediction weighs the complete picture.
Setting a recurring review cadence that sticks
- Weekly for high-spend accounts (>$10k/mo): Bot traffic can shift quickly when new placements or audiences launch. A weekly report catches placement-level spikes early.
- Bi-weekly for moderate spend: Balances workload with detection freshness.
- Align with campaign changes: Run an extra audit 48 hours after any major targeting, creative, or budget adjustment. The Meta invalid-traffic guide stresses preserving attribution before changing the campaign.
- Calendar the review: Block 30 minutes on the same day each cycle. The report arrives with a consistent structure: summary bot rate, top offending placements, session recordings for the highest-confidence flags, and a claim-ready evidence package.
Interpreting the refund-ready report
Each report contains:
- Executive summary: Overall bot percentage, estimated wasted spend, and refundable amount.
- Placement breakdown: Bot rate by placement (Facebook Feed, Instagram Stories, Audience Network, Google Search Partners, etc.).
- Signal cluster view: Which of the 110+ checks fired most often and in what combinations.
- Session recordings: Replay of flagged visits showing mouse paths, scroll behavior, and timing.
- Claim package: Click IDs, campaign metadata, timestamps, and signal-by-signal reasoning formatted for Google's invalid activity credit process and Meta's invalid traffic review.
Focus first on placements where the bot rate exceeds your account average by a wide margin. Those are the fastest wins for both suppression and refund claims.
Taking action on findings
- Suppress conversion events for flagged sessions. This stops pixel poisoning immediately and protects bidding algorithms.
- Exclude high-bot placements or audiences. Use the placement breakdown to adjust targeting in Google Ads and Meta Ads Manager.
- File the refund claim. Upload the BotRefund claim package through each platform's support or invalid-activity flow. BotRefund's team can assist with negotiation; their experience across 2,500+ audits informs the arguments reviewers need.
- Update negative audience lists. Export flagged click IDs or device fingerprints to exclusion lists where supported.
- Monitor the next cycle. Verify that bot rates drop on adjusted campaigns and that conversion quality (CRM contact rate, demo bookings) improves.
Limitations and when the advice does not apply
- Not a WAF or CDN replacement: BotRefund operates at the marketing layer, observing the visitor journey after the paid click. It does not provide DDoS mitigation, edge caching, or infrastructure-level firewall rules.
- Requires onsite script installation: If you cannot add JavaScript to landing pages (e.g., some marketplace or affiliate setups), the behavioral layer cannot be collected.
- Refunds are not guaranteed: Google and Meta make final credit decisions. BotRefund's 83% historical success rate reflects cases where evidence met platform standards; some claims are denied.
- Privacy tools and corporate networks can create anomalies: The platform treats single anomalies as evidence, not verdicts, but unusual device configurations may require manual review.
- Enterprise pricing applies above $10,000/mo ad spend: The self-serve tier covers budgets under that threshold; larger accounts move to custom plans.
Key facts at a glance
| Capability | Detail | Source |
|---|---|---|
| Detection confidence | 99% when session evidence supports it | S2, S3, S5, S7 |
| Independent signals | 110+ behavioral, browser, hardware, network, attribution checks | S2, S3, S5 |
| Refund success rate | 83% of clients recover funds across 2,500+ audits | S2, S8 |
| Report format | Click IDs, campaign details, timestamps, session recordings, signal-by-signal reasoning | S2 |
| Conversion protection | Suppresses bot-triggered events so pixels train on verified humans | S2, S4, S8 |
| Platform coverage | Google Ads (invalid activity credits) and Meta Ads (invalid traffic) | S1, S4, S6, S7 |
| Case study result | FinTrust recovered $140,000, 14% average bot click rate, 18% conversion rate increase | S8 |
Frequently asked questions
How long until the first meaningful report?
The free baseline audit runs immediately after script installation. A full refund-ready report with statistical significance typically requires 7–14 days of traffic, depending on volume.
Can I use BotRefund alongside Cloudflare or another WAF?
Yes. BotRefund adds a marketing-focused evidence layer — behavioral investigation, conversion-signal protection, and refund-ready reporting — while your edge provider handles infrastructure security. The two jobs coexist.
What if Google or Meta denies the claim?
BotRefund's team supports negotiation with additional documentation and arguments. Historical data shows an 83% approval rate, but final decisions rest with each platform.
Does the script slow down page load?
The snippet is lightweight and loads asynchronously. It collects signals without blocking rendering or interfering with Core Web Vitals.
How does BotRefund differ from server-side log analysis?
Server-side logs capture IP, headers, and user-agent data. BotRefund's client-side approach observes actual browser behavior — mouse movement, scroll timing, API consistency — catching advanced botnets that mimic legitimate headers.
What ad spend level justifies the cost?
Accounts spending under $10,000/month use the self-serve tier. Above that, custom enterprise pricing applies. The break-even point depends on your current bot rate; the free audit quantifies it before you commit.
Can I export raw signal data for my own analysis?
Reports include session-level evidence and signal clusters. Full raw-data export options are available on enterprise plans.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
How BotRefund can help
BotRefund installs a lightweight script on your landing pages, connects to your Google and Meta ad accounts, and runs scheduled audits that turn 110+ behavioral and technical signals into refund-ready reports. The platform suppresses bot-triggered conversion events so your pixels train only on verified humans, and it formats evidence — click IDs, timestamps, session recordings, signal-by-signal reasoning — in the exact structure Google and Meta reviewers expect. Across 2,500+ audits, 83% of clients have recovered ad spend, with one neobank client reclaiming $140,000 and lifting conversion rates 18%. You need the ability to add JavaScript to your pages and admin access on the ad accounts you want to monitor. The free baseline audit quantifies your current bot rate before any commitment.