Seatext library / BotRefund evidence
Why Meta Denies Invalid Traffic Refund Requests — And What to Do Next
Meta denies most refund claims because advertisers submit weak evidence — usually server-level data that shows suspicious patterns but fails to prove automation. The platform's automated filters catch only a fraction of bot traffic,...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
Meta denies invalid traffic refund requests for three main reasons: the evidence doesn't prove the traffic was automated, the claim falls outside the policy window, or the submission relies on Meta's own automated filters — which the company admits catch only a fraction of invalid activity. If your claim was rejected, the most likely fix is stronger, session-level behavioral evidence tied to click IDs and campaign data.
How Meta's Invalid Traffic Refund Process Actually Works
Meta has a formal policy stating advertisers should not be charged for clicks or impressions it determines are invalid — including bots, click farms, accidental taps, and malicious scripts. But the process is less structured than Google's. There is no public claim form with a guaranteed review window. Instead, advertisers must proactively file a claim through support channels and supply evidence that the traffic was non-human.
Meta's automated systems do filter some invalid traffic before you're billed. However, sophisticated bots using residential proxies, real browser fingerprints, and human-like behavior routinely bypass those filters. When that happens, the burden shifts to you: you must prove the clicks were automated, not just low-quality.
Why Most Claims Get Denied: The Evidence Gap
The single biggest reason for denial is evidence that shows suspicion but not automation. Server logs — IP addresses, user agents, click timestamps — can flag anomalies. They cannot prove a visitor didn't scroll, didn't move a mouse, or completed a form in 0.8 seconds. Meta's reviewers look for behavioral proof: session recordings, click-path uniformity, missing engagement signals, and deterministic bot markers (e.g., headless browser attributes, missing browser APIs).
Claims built only on "high bounce rate" or "low conversion rate" get rejected because those metrics also describe bad targeting, creative mismatch, or landing-page friction. The distinction matters: a weak campaign attracts real people who don't convert. Bot traffic leaves repeatable technical patterns — identical field structures, zero scroll, instantaneous form submits, placement-level spikes.
What Counts as "Invalid Activity" Under Meta's Policy
Meta defines invalid activity broadly across several categories:
- Invalid clicks: Clicks generated by automated bots, click farms, or malicious scripts targeting your ads.
- Invalid impressions: Impressions served to fake accounts or generated by automated page-refresh tools.
- Accidental interactions: Unintentional taps on mobile placements.
- Competitor click fraud: Clicks intended to exhaust your budget.
Not every bad lead qualifies. A real person who fills a form but never answers the phone is a lead-quality problem, not invalid traffic. Treating every unresponsive contact as fraud can make you exclude valuable audiences. Start with a structured audit comparing Ads Manager data, website sessions, and CRM outcomes before filing.
The Difference Between Meta's and Google's Refund Systems
Google's Invalid Activity Credit system is semi-automated: credits appear in your account when Google's detectors catch something, and you can file a supplemental claim with a defined form. Meta's process is manual, less transparent, and has no published SLA. That makes evidence formatting critical. Google accepts GCLID-level reports; Meta expects click IDs, campaign/ad set/ad identifiers, timestamps, and signal-by-signal reasoning in a structure their review teams recognize.
Because Meta's process is less structured, the quality of your submission determines the outcome more than on Google. A claim that looks like a spreadsheet export gets denied. A claim that reads like a forensic report — session by session, with behavioral evidence — gets approved.
Building a Claim That Gets Approved: Evidence Standards
Approved claims share three traits:
- Client-side behavioral data. Server logs alone are insufficient. You need browser-level signals: scroll depth, mouse movement, touch events, form interaction timing, focus/blur events, and browser automation fingerprints (e.g.,
navigator.webdriver, missingchrome.runtime, headless User-Agent substrings). - Click-ID traceability. Every flagged session must link to a Meta click ID (fbclid or internal click ID) so reviewers can match your evidence to their billing records.
- Signal-by-signal reasoning. Don't just say "this looks like a bot." Show: "Session X had zero scroll, 12ms form completion, missing canvas fingerprint, and navigator.webdriver=true — consistent with headless Chrome."
BotRefund's platform automates this by capturing 110+ behavioral, browser, hardware, network, and attribution signals per session, then generating refund-ready reports with click IDs, campaign details, timestamps, session recordings, and per-signal explanations — the format Meta's teams use to review claims.
Common Mistakes That Lead to Denial
| Mistake | Why It Fails | What to Do Instead |
|---|---|---|
| Submitting only server logs (IP, UA, referrer) | Cannot prove automation; real users share IPs and UAs | Add client-side behavioral capture (scroll, mouse, timing, browser APIs) |
| Claiming "low conversion rate" as proof | Confuses lead quality with invalid traffic | Segment by placement/creative; show behavioral anomalies, not outcome metrics |
| Filing after changing campaign structure | Breaks attribution; reviewers can't match clicks to evidence | Preserve campaign, ad set, creative, and placement IDs before any changes |
| Using generic "invalid traffic" estimates | Meta rejects aggregate percentages without session-level proof | Submit session-by-session findings with click IDs and signal reasoning |
| Relying on Meta's auto-filters to catch everything | Filters miss sophisticated bots using residential proxies and real fingerprints | Proactively audit with client-side detection; file supplemental claims |
When to Escalate vs. When to Re-audit
If your claim was denied with a generic "insufficient evidence" response, don't just resubmit the same data. Re-audit first. Check whether your evidence covers:
- All placements where quality dropped (Audience Network, Reels, Explore, etc.)
- Device and browser segments where anomalies concentrate
- Time windows matching the claim period exactly
- Click-ID coverage for every flagged session
If the re-audit confirms automation with client-side proof, escalate through Meta's business support channel with a revised, forensic-grade report. If the evidence is thin, invest in client-side detection for the next cycle — the 83% approval rate BotRefund sees across 2,500+ audits comes from evidence that meets the platform's actual review standard, not from persistence alone.
Key Facts
| Metric | Detail | Source |
|---|---|---|
| Bot detection confidence | 99% confidence across 110+ behavioral, browser, hardware, network, and attribution signals | S2 |
| Client refund recovery rate | 83% of clients recover funds from Google and Meta | S2 |
| Audits completed | 2,500+ brand audits across fintech, DTC, enterprise | S2, S7 |
| Automated traffic share of paid clicks | Industry audits consistently place it between 9% and 20% | S7 |
| Meta's automated catch rate | Catches only a fraction; sophisticated bots bypass filters routinely | S6 |
| Evidence format for approval | Click IDs, campaign details, timestamps, session recordings, signal-by-signal reasoning | S2, S6 |
| Setup requirement | One script tag, ~1 minute, no ad-account access required | S7 |
| Data handling | GDPR-aligned | S7 |
Limitations & When This Advice Doesn't Apply
- Lead quality vs. invalid traffic: If your CRM shows real people who don't buy, that's a targeting or offer problem — not a refund case. This article addresses only non-human, automated interactions.
- Policy windows: Meta does not publish a fixed lookback window. Claims for spend older than 60–90 days face higher scrutiny. Check current policy before filing.
- Platform policy changes: Meta updates its Advertising Policies and refund processes without notice. The mechanics described here reflect the process as of the source pack's publication.
- Non-Meta inventory: This covers Facebook, Instagram, and Meta Audience Network. Third-party programmatic partners have separate policies.
FAQ
How long does Meta take to review a refund claim?
No published SLA. In practice, initial responses range from 5–20 business days. Complex claims with session-level evidence may take longer but have higher approval odds.
Can I get a refund for accidental mobile clicks?
Yes — Meta's policy includes accidental taps as invalid activity. But you still need evidence distinguishing accidental from intentional (e.g., zero dwell time, immediate back navigation, no scroll). Server logs alone rarely suffice.
Does Meta refund impression fraud the same way as click fraud?
Policy covers both, but impression fraud claims are harder to prove. You need evidence that impressions were served to automated browsers (no paint events, no viewport interaction) — which requires client-side measurement.
What if Meta says my traffic is "valid" but my CRM shows zero contactability?
That's a lead-quality signal, not proof of invalid traffic. Run a structured audit: compare placement-level lead quality, session behavior, and CRM outcomes. If behavioral signals show automation, file a claim. If they show real but unqualified users, adjust targeting.
Do I need to give Meta access to my ad account?
No. BotRefund's detection runs via a single script tag on your site. It captures behavioral data independently. You submit the generated report through standard support channels — no account credentials shared.
How much budget should I expect to recover?
Industry audits place automated traffic at 9–20% of paid clicks. Recovery depends on how much of that traffic your evidence proves was automated. BotRefund clients see an 83% claim approval rate, but absolute recovery varies by spend level and bot sophistication.
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.