Seatext library / BotRefund evidence
How to Report Bot Traffic to Meta for a Refund: Step-by-Step Process
To report bot traffic to Meta for a refund, gather session-level evidence — click IDs, timestamps, behavioral signals — and submit a structured invalid traffic claim through Meta's Ads Manager or support channels. Meta...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
If you suspect automated traffic is draining your Meta ad budget, the path to a refund starts with evidence — not a support ticket. Meta's systems catch some invalid activity automatically, but the majority of bot traffic goes undetected unless you document it session by session and submit a claim in the format their review teams use. This article walks through the complete process, from identifying suspicious patterns to filing a claim that meets Meta's evidence standards.
To report bot traffic to Meta for a refund, open Meta Ads Manager, select the affected campaign, and submit an invalid traffic request through the Report a Problem or Invalid Traffic link, attaching session-level evidence. Keep the detailed steps below it.
Understand What Meta Considers Invalid Traffic
Meta divides traffic into valid and invalid categories. Valid traffic consists of human visitors. Invalid traffic consists of automated interactions — bots, scrapers, click farms, and publisher script engines that load pages but do not read, scroll, or convert. Source S3 notes that "Meta divides traffic quality into valid and invalid. Valid traffic consists of human visitors. Invalid traffic consists of automated interactions." This distinction matters because Meta's automated filters catch only a fraction of invalid traffic. The rest requires advertiser-initiated claims with specific evidence.
Recognize the Signals Worth Investigating
Before filing a claim, verify that the problem is actually bot traffic and not a campaign quality issue. Source S1 lists five signal categories to investigate: contactability (disconnected numbers, invalid email domains, repeated addresses), timing (leads arriving in short bursts, forms submitted immediately after landing), session behavior (no scrolling, no field corrections, uniform click paths), campaign patterns (sharp lead-quality differences by placement, creative, audience expansion, device, or landing page), and CRM outcomes (high reported lead count paired with no calls connected, demos booked, or qualified opportunities). Treat every unresponsive contact as fraud only after structured audit — excluding a valuable audience by mistake is costly.
Preserve Attribution Before Changing Anything
The first step in the investigation workflow from Source S1 is to "preserve attribution before changing the campaign." Keep campaign, ad set, creative, placement, and landing page identifiers intact. Do not pause, edit, or restructure until you have captured the click IDs (Meta's equivalent of GCLIDs), timestamps, and session recordings for the suspicious traffic. Changing the campaign destroys the evidence trail Meta's reviewers need to match your claim to specific billed events.
Collect Session-Level Evidence
Meta's review teams expect evidence structured around individual sessions. For each suspicious interaction, you need: the click ID, campaign/ad set/ad identifiers, timestamp, landing page URL, and a behavioral breakdown — time on page, scroll depth, field interactions, navigation path, and any conversion events triggered. Source S2 states that BotRefund "turns each finding into a refund-ready report with click IDs, campaign details, timestamps, session recordings, and signal-by-signal reasoning. The evidence is structured in the format platform teams use to review invalid traffic claims." Client-side tracking (browser-level) captures behavioral signals that server logs miss — mouse movements, scroll events, form field focus, and timing patterns that distinguish humans from automation.
Build the Claim in Meta's Expected Format
Meta does not publish a public claim template, but their reviewers consistently look for: a summary of the invalid traffic pattern, a table of flagged click IDs with timestamps and campaign mapping, session recordings or behavioral logs for each flagged click, and a signal-by-signal explanation of why each session is non-human. Source S2 emphasizes that their "83% approval rate comes from three things: 99% bot-detection confidence, reports built in a format their teams can review, and deep experience negotiating successful claims." The format matters as much as the data — claims that require reviewers to reconstruct the evidence are frequently denied or delayed.
Submit Through the Correct Channel
For most advertisers, the starting point is Meta Ads Manager: navigate to the campaign, open the reporting view, and use the "Report a Problem" or "Invalid Traffic" link (labeling varies by account type and region). Enterprise accounts with a Meta representative should route the claim through that contact. If no dedicated channel appears, open a Business Support case with the subject "Invalid Traffic Refund Request" and attach your evidence package. Do not use generic billing support — they lack the technical context to evaluate bot evidence.
Follow Up and Escalate When Necessary
Meta's initial response is often a template denial citing "automatic systems have already filtered invalid traffic." This is a standard first reply, not a final decision. Reply with your evidence package attached, referencing specific click IDs and the behavioral signals that distinguish the flagged sessions from the automatically filtered ones. Source S2 notes BotRefund has "worked through more than 2,500 audits and know how to present bot evidence to Google and Meta. We format the data, write the claim, and support the negotiation with the documentation and arguments their reviewers need to return money to advertisers." Persistence with structured evidence is what moves claims from denial to approval.
Common Mistakes That Delay or Kill Claims
- Submitting aggregate statistics instead of session-level data. "My CPL doubled" is not evidence. "Click ID 12345 spent 0.8 seconds on page, zero scroll, triggered lead event" is evidence.
- Changing campaign structure before evidence capture. This breaks the link between billed clicks and your documentation.
- Conflating low-quality leads with bot traffic. Real people who don't buy are not refundable. The distinction is behavioral — bots leave repeatable technical patterns.
- Using server logs only. Server-side data (IP, user agent, headers) misses advanced botnets that mimic residential browsers. Client-side behavioral signals are required for high-confidence claims.
Limitations and When This Process Does Not Apply
Meta's refund policy covers invalid traffic — automated, non-human interactions, accidental mobile clicks, and competitor click fraud intended to exhaust your budget. It does not cover: low-intent human clicks, ordinary poor campaign performance, or targeting mistakes. Source S4 (referencing Google's parallel system) lists examples of invalid activity: "Repeated manual clicks from the same user, clicks generated by automated tools, bots, or other deceptive software, accidental clicks on mobile ads, clicks from known data center IP ranges, impression fraud from automated page refresh tools, clicks intended to exhaust an advertiser's budget." Meta's definitions are similar. If your traffic quality issue stems from broad targeting, weak creative, or a mismatched offer, the refund path will not work — fix the campaign instead.
Key Facts
| Metric | Detail | Source |
|---|---|---|
| Bot detection confidence | 99% confidence across 110+ behavioral, browser, hardware, network, and attribution signals | S2 |
| Claim approval rate | 83% of refund claims filed by BotRefund are approved by ad platforms | S2 |
| Brands audited | 2,500+ brands, from fintech enterprises to DTC brands | S2 |
| Wasted spend recovered | $100M+ in wasted ad spend recovered across client accounts | S2 |
| Automated traffic share | Industry audits consistently place automated traffic between 9% and 20% of paid clicks | S5 |
| Upfront cost | $0 upfront on enterprise recovery — fees come out of what we get back | S2 |
FAQ
How long does Meta take to review an invalid traffic claim?
Typical first response: 5–10 business days. Full review with evidence: 2–6 weeks depending on claim complexity and whether escalation is needed. Claims with complete session-level evidence packages move faster.
Can I get a refund for bot traffic from months ago?
Meta's manual claim window is limited. Advertisers should file promptly once suspicious traffic is identified to maximize the chance of recovery.
Do I need to install tracking code before the bot traffic occurs?
Yes. Client-side behavioral evidence requires a script on your landing page at the time of the visit. Retroactive detection is limited to server logs, which lack the behavioral signals Meta's reviewers weigh heavily. Source S5 notes: "One script tag · ~1 minute" for installation.
What if Meta denies my claim?
Denial is common on first review. Reply with the same evidence package, explicitly mapping each flagged click ID to the behavioral signals that prove automation. Reference Meta's own invalid traffic definitions. Escalate through a Meta representative if you have one. Persistence with structured evidence is the standard path to approval.
How much budget should I expect to recover?
Recovery varies by account. Source S5 shows an illustrative summary: $7,612 recovered in a single quarter. Industry audits place automated traffic at 9–20% of paid clicks. Your actual recovery depends on traffic volume, bot share, and evidence quality.
Can I do this myself without a service?
Yes, if you can implement client-side tracking, capture session recordings, extract click IDs, and format the evidence package to Meta's reviewer expectations. The technical barrier is significant — most marketing teams lack the development resources to build and maintain the detection and reporting pipeline. Source S2 notes BotRefund provides "reports in the format Google and Meta accept" and "experience negotiating with Google and Meta."
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
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 with one script tag in about a minute and begins capturing 110+ behavioral, browser, hardware, network, and attribution signals per session. The system flags automated traffic with 99% confidence and automatically builds refund-ready reports structured in the exact format Meta's review teams use — click IDs, campaign details, timestamps, session recordings, and signal-by-signal reasoning. Across 2,500+ audited brands, 83% of filed claims are approved. There is no upfront cost on enterprise recovery; fees come only from recovered funds. If you want to see how much of your Meta spend may be recoverable, run a free bot audit first — it shows the scope before you commit.