How to Use BotRefund: Configuration, Detection, and Refund Workflows

Direct answer: BotRefund has no "cadence" control

BotRefund does not expose a scheduling or cadence setting for its detection engine. The system monitors every paid session continuously from the moment the tracking script loads. You do not choose how often it scans; it evaluates each visit in real time using 110+ behavioral, browser, hardware, network, and attribution signals. What you can configure are the workflows around that detection: which campaigns to protect, how often you pull refund-ready reports, and when you file claims with Google or Meta.

What BotRefund actually does

BotRefund is a client-side bot detection and ad-refund evidence platform. It installs a lightweight script on your landing pages. That script collects browser-level evidence — pointer movement, scroll behavior, timing, rendering quirks, and dozens of other signals — and feeds them into a prediction model that scores each session as human or automated with up to 99% confidence. The output is not a block list; it is a structured, session-by-session report formatted for Google and Meta invalid-traffic review teams.

Key capabilities documented in the source pack:

• Real-time scoring of every paid click across Google and Meta campaigns.
• Refund-ready reports that include click IDs (GCLID, FBCLID), campaign details, timestamps, session recordings, and signal-by-signal reasoning.
• Negotiation support: BotRefund has worked through 2,500+ audits and knows how to present evidence so platform reviewers approve credits.
• Conversion-signal protection: you can suppress bot conversion events so your pixel and bidding algorithms train only on verified humans.

How the detection engine works (continuous, not scheduled)

Because there is no cadence knob, it helps to understand the detection loop:

1. Script loads on the landing page after the ad click.
2. Signals fire throughout the session: mouse tremor, scrollbar width, iframe context, input speed, pointer path geometry, session duration patterns, and 100+ other checks.
3. AI weighs the full pattern rather than relying on any single rule. A single anomaly (e.g., a scrollbar width leak) is kept as evidence, not a verdict.
4. Session classified as bot or human with a confidence score. Only sessions where the complete evidence cluster supports it reach the 99% confidence threshold.
5. Report entry created with all raw signals, the classification, and the campaign attribution data needed for a refund claim.

This loop runs for every visit. You cannot slow it down, speed it up, or run it in batches. If you need a periodic review rhythm, you build that on top of the continuous data — for example, pulling a weekly report and filing a monthly claim.

Setting up your audit and reporting workflow

Since the detection is always on, your "cadence" is really a reporting and claim-filing rhythm. A practical workflow used by BotRefund clients:

1. Preserve attribution before changing anything

Keep campaign, ad set, creative, placement, and click identifiers intact while you investigate. Changing UTM structures or pausing campaigns mid-audit breaks the evidence chain.

2. Define a review interval

• High-spend accounts ($50k+/mo): pull the BotRefund dashboard weekly, export the refund-ready report, and submit to Google/Meta within the platform's claim window (usually 60 days for Google, 90 for Meta).
• Mid-market accounts ($10k–$50k/mo): bi-weekly review is usually sufficient.
• Smaller accounts (<$10k/mo): monthly review works, but watch the claim deadlines.

3. Export the refund-ready report

The report includes click IDs, campaign hierarchy, timestamps, session recordings, and a signal-by-signal explanation. This is the exact format Google and Meta reviewers expect. Do not rewrite it; attach it as-is.

4. File the claim

• Google Ads: use the Invalid Activity Credit request form in the billing section. Attach the BotRefund report. Google's automated systems catch some invalid clicks, but the source pack notes they miss a significant portion — hence the need for your own evidence.
• Meta Ads: submit via the Meta Business Help Center "Invalid Traffic" form. Include the FBCLIDs and the BotRefund session evidence.

5. Track outcomes

Log each claim: date filed, platform, spend covered, credit received, and any follow-up required. BotRefund's historical data shows an 83% recovery rate across 2,500+ audits, but individual results vary by traffic mix and claim quality.

Configuring detection scope and suppression rules

While you cannot schedule detection, you can control where it runs and what happens to flagged sessions:

Campaign selection

Add the BotRefund script only to landing pages used by paid campaigns you want audited. Organic, direct, and email traffic will still be scored, but you only pay for (and claim refunds on) paid clicks.

Conversion suppression

BotRefund can suppress conversion events for sessions it classifies as bots with high confidence. This prevents pixel poisoning — where bot conversions train Google's or Meta's bidding algorithms to chase more bot-like traffic. The source pack notes this is critical: "Suppressed conversion events for automated browser emulation signals, ensuring Facebook & Google AI trained only on verified bank accounts."

Confidence threshold

The 99% confidence figure applies to sessions where the full evidence cluster supports the classification. You cannot lower this threshold in the UI; the model is calibrated to minimize false positives. If you see sessions you believe are bots but they are not flagged, the evidence did not meet the corroboration standard.

Integrating with Google and Meta claim processes

BotRefund's value is not just detection — it is the handoff to the platforms. The source pack emphasizes three things that drive the 83% approval rate:

Factor	What it means for you
99% bot-detection confidence	Reports only include sessions the model is highly certain about. Reviewers see fewer borderline cases.
Refund-ready report format	Click IDs, timestamps, session recordings, and signal reasoning are pre-structured. No manual reformatting.
Negotiation experience	BotRefund has filed 2,500+ claims. They know the language, evidence thresholds, and escalation paths each platform uses.

Your job is to submit the report within the platform's claim window and respond to any follow-up questions. BotRefund's team can assist with the negotiation step if you are on a plan that includes it.

Common configuration patterns (what teams actually do)

Pattern A: "Set and forget" with monthly claim batch

• Install script on all paid landing pages.
• Enable conversion suppression for high-confidence bot sessions.
• Calendar reminder: first Monday of each month, export last month's report, file Google and Meta claims.
• Best for: stable campaigns, consistent spend, team with bandwidth for monthly admin.

Pattern B: Weekly review, rapid claim

• Same install and suppression setup.
• Weekly dashboard check: any campaign showing a sudden bot-rate spike gets an immediate claim filed.
• Monthly roll-up claim for the rest.
• Best for: volatile traffic sources, new campaign launches, agencies managing multiple clients.

Pattern C: Agency white-label workflow

• Script deployed via GTM across client accounts.
• Agency pulls reports from BotRefund dashboard, brands them, files claims on client behalf.
• Client sees only the credit line item in their ad account.
• Best for: agencies that want to own the ad-quality narrative.

Limitations and what BotRefund does not do

• No scheduling/cadence control — detection is continuous. You cannot run it only on weekdays, only during business hours, or in daily batches.
• No server-side log analysis — BotRefund is client-side only. It does not ingest your CDN logs, WAF logs, or server access logs.
• No automatic claim filing — you (or your agency) must submit the report to Google/Meta. BotRefund provides the evidence and negotiation guidance, not an API that files claims for you.
• No traffic blocking — it does not serve a WAF challenge, CAPTCHA, or IP block. It observes and reports. If you want to block bots at the edge, you need a separate layer (Cloudflare, Akamai, etc.).
• No guarantee of refund — platforms decide. The 83% historical approval rate is an aggregate, not a promise for any single claim.
• No pricing in public docs — the source pack shows an "Under $10,000/mo" tier selector and an "Enterprise" tier, but exact pricing requires a quote.

Key facts from BotRefund source documentation

Fact	Source
110+ behavioral, browser, hardware, network, and attribution signals	S2
99% confidence in flagged bot traffic	S2
83% of clients recover funds from Google and Meta across 2,500+ audits	S2
Refund-ready reports include click IDs, campaign details, timestamps, session recordings, signal-by-signal reasoning	S2
Conversion suppression prevents pixel poisoning	S8
FinTrust case study: $140,000 refunded, 14% average bot click rate, 18% conversion rate increase	S8
Detection signals include scrollbar width leak, clean context iframe, ghost click, honeypot trap, robotic mouse movement, superhuman input speed, grid-aligned movement, absence of human tremor	S3, S5, S2
Google invalid activity credits cover repeated manual clicks, automated tools, accidental mobile clicks, data center IPs, impression fraud, competitor click fraud	S6
Meta invalid traffic includes automated web crawlers, search scrapers, click farms, publisher script engines	S4

Terminology quick reference

• GCLID / FBCLID: Google Click ID / Facebook Click ID. Unique identifiers appended to landing-page URLs that tie a session to a specific paid click. Required for refund claims.
• Pixel poisoning: When bot conversions feed the ad platform's optimization algorithm, causing it to bid more aggressively for similar (bot-like) traffic.
• Invalid activity credit (Google): A refund applied to your Google Ads account for clicks Google deems invalid. Not automatic for all invalid traffic.
• Invalid traffic (Meta): Automated interactions — crawlers, scrapers, click farms, publisher scripts — that Meta classifies as non-human.
• Refund-ready report: BotRefund's structured export containing every evidence field the platform review teams expect.
• Signal: One independent check (e.g., scrollbar width leak, pointer tremor). No single signal is a verdict; the AI weighs the full cluster.

FAQ

Can I run BotRefund detection only once a day?

No. The script evaluates every session in real time. There is no batch or scheduled mode.

Does BotRefund automatically file refund claims with Google or Meta?

No. It produces the evidence report. You or your agency submit the claim through each platform's support flow. BotRefund can advise on the negotiation.

What if I want to adjust the sensitivity — flag more sessions as bots?

You cannot lower the confidence threshold. The model is fixed at a high-specificity operating point to keep false positives near zero. Sessions that don't meet the 99% corroboration standard remain unflagged.

How long do I have to file a claim after detecting bot traffic?

Google typically allows 60 days from the click date. Meta allows up to 90 days. Check the current policy in each platform's help center; windows can change.

Can I use BotRefund on organic traffic to clean my analytics?

The script will score any session on pages where it's installed, but refund claims only apply to paid clicks with valid GCLID/FBCLID. You can use the bot flags to filter your own analytics, but that's a secondary use case.

What happens if a real user gets flagged as a bot (false positive)?

The 99% confidence target is designed to make this extremely rare. If it happens, the session evidence (recording, signals) is available for review. You can choose not to include that session in a refund claim.

Is there a minimum spend requirement to make BotRefund worthwhile?

The source pack shows an "Under $10,000/mo" tier, so accounts below that threshold are supported. The ROI calculation is simple: if your bot click rate is near the 14% average seen in the FinTrust case, a $5k/mo spend with a 14% bot rate wastes ~$700/mo. A successful claim recovers that.

Next steps

1. Request a free bot audit from BotRefund to see your actual bot rate before committing.
2. Install the script on a high-spend campaign's landing page first. Verify data flows in the dashboard.
3. Enable conversion suppression for that campaign.
4. Set a calendar reminder for your first claim-filing window (30–45 days out).
5. Export the refund-ready report, attach it to the platform claim form, and track the outcome.

There is no cadence knob to turn. The rhythm you build is the review-and-claim cycle that fits your team and your platform deadlines.

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

• How to Automate Refunds and Exchanges with AI in Ecommerce | Retell AI
• Add a Cadence for Your Sales Prospecting Bot | Salesforce Help
• Cadence Commands | Discord Bot List

Learn more

Visit the website for more information.