Seatext library / BotRefund evidence
Which Kinds of Invalid Traffic Does Meta Refund? A Decision Guide for Advertisers
Meta refunds clicks and impressions it classifies as invalid: automated bot traffic, click farms, malicious scripts, and accidental interactions. It does not refund low-quality leads, competitor clicks you cannot prove were automated, or traffic...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
Meta refunds invalid clicks and impressions that fall into specific categories: automated bot traffic, click farms, malicious scripts, and accidental clicks. The platform does not refund traffic simply because leads are unqualified, contacts are unreachable, or a competitor may have clicked your ads — unless you can prove that traffic was automated. The deciding factor is behavioral evidence that shows non-human interaction patterns, not campaign performance metrics.
This guide separates refund-eligible invalid traffic from the categories Meta treats as valid spend. Use the trade-off table below to match your situation to the right category, then follow the evidence requirements for each type.
| Traffic category | Refund eligible? | What Meta looks for | Evidence you need | Common confusion |
|---|---|---|---|---|
| Automated bots (scripts, headless browsers) | Yes | Non-human navigation: no scroll, no mouse movement, instant form fills, identical timing patterns | Client-side session recordings, click IDs (fbclid), behavioral signal logs showing automation | Often mistaken for "low-quality leads" — but bots leave technical fingerprints humans don't |
| Click farms (paid human workers clicking repeatedly) | Yes | Repeated clicks from same device/IP clusters, unnatural session duration, no downstream engagement | IP and device fingerprint clusters, conversion gap data (clicks with zero site activity) | Can look like real users at first; distinguished by volume and lack of meaningful actions |
| Malicious scripts / publisher script engines | Yes | Background clicks, forced redirects, impression stacking, auto-refresh loops | Placement-level anomaly reports, referrer analysis, timestamp patterns | Often hidden in partner network placements; check placement breakdowns |
| Accidental clicks (mobile mis-taps, overlay interference) | Yes | Immediate bounce, zero scroll, session duration under 1 second, no subsequent page views | Landing page engagement metrics tied to specific click IDs | Not the same as "low intent" — accidental means zero engagement, not weak engagement |
| Competitor clicks (manual, human-driven) | No — unless proven automated | Human-like behavior: scroll, dwell, navigation — even if motive is malicious | Behavioral proof of automation (bot signatures), not just IP ownership | Advertisers often assume competitor = refundable; Meta requires automation proof |
| Low-quality or unqualified leads | No | Real humans who filled forms but don't buy, wrong demographic, fake contact info entered by people | Not applicable — this is a targeting/creative issue, not invalid traffic | Biggest source of wasted refund requests; CRM outcomes don't prove invalid traffic |
| Async validation / delayed conversion gaps | No | Legitimate delay between click and conversion (e.g., B2B sales cycles) | Not applicable | Confused with bot traffic because conversion doesn't appear immediately |
How Meta Defines Invalid Traffic
Meta splits traffic into two buckets: valid (human visitors) and invalid (automated interactions). According to its Advertising Policies, advertisers should not be charged for clicks or impressions Meta determines are invalid. The policy covers several concrete categories: clicks generated by automated bots, click farms, or malicious scripts targeting your ads; impressions served to fake accounts or generated by automated tools; and accidental clicks such as unintentional mobile taps.
The key phrase is "Meta determines." The platform's automated systems catch a fraction of invalid activity — mostly obvious patterns like rapid-fire clicks from data-center IPs. Sophisticated traffic using residential proxies, real browser engines, and human-like behavior routinely bypasses those filters. When that happens, the burden shifts to you: you must file a proactive claim with behavioral evidence proving automation.
Why the Distinction Between Automated and Low-Quality Matters
Treating every unresponsive lead as fraud wastes time and weakens legitimate claims. A weak campaign can attract real people who aren't ready to buy. Bot traffic and form spam leave repeatable technical patterns: unusually fast form completion, identical field structures, sudden placement-level spikes, or conversion events with no meaningful page engagement. Low-quality leads show human behavior — scrolling, hesitations, corrections — even if they never become customers.
Meta's reviewers look for automation signatures, not business outcomes. A claim built on "these leads didn't close" gets denied. A claim built on "these 200 clicks share the same canvas fingerprint, zero scroll depth, and sub-second form submit times" gets reviewed.
Signals That Separate Refundable from Non-Refundable Traffic
- Contactability anomalies: Disconnected numbers, invalid email domains, repeated addresses, or unusual country-code concentrations — when paired with behavioral automation signals.
- Timing patterns: Several leads arriving in short bursts, forms submitted immediately after landing, or conversions concentrated at unusual hours.
- Session behavior: No scrolling, no field corrections, uniform click paths, no meaningful time on the offer page.
- Campaign-level anomalies: Sharp lead-quality differences by placement, creative, audience expansion, device, or landing page.
- CRM outcome mismatch: High reported lead count paired with zero calls connected, demos booked, qualified opportunities, or repeat engagement — only when combined with the technical signals above.
None of these signals alone proves invalid traffic. They become evidence when they cluster around specific click IDs and placements.
Investigation Workflow Before Filing a Claim
- Preserve attribution before changing the campaign. Keep campaign, ad set, creative, placement, and landing-page identifiers intact. Changing targeting or creatives breaks the link between the click ID and the evidence.
- Collect client-side behavioral data. Server logs (IP, user-agent) catch basic scrapers but miss advanced botnets. You need browser-level signals: mouse movement, scroll depth, focus/blur events, canvas fingerprint, WebGL renderer, timing of each interaction.
- Match click IDs to sessions. Capture the fbclid (or gclid for Google) on landing and tie it to the full session recording. This is what Meta's review team asks for.
- Segment by placement and creative. Invalid traffic often concentrates in specific placements (Audience Network, Reels, Instant Articles) or creative formats. Isolate the worst offenders first.
- Build a refund-ready report. Structure findings in the format Meta's invalid-traffic team expects: click IDs, timestamps, campaign hierarchy, session recordings, and signal-by-signal reasoning for each flagged interaction.
- Submit through Meta's support channel. Use the "Report Invalid Activity" flow or your account representative. Attach the structured evidence package. Expect follow-up questions; respond with additional session data, not opinions.
Key Facts from Platform Policy and Detection
| Fact | Detail | Source |
|---|---|---|
| Refund policy basis | Meta's Advertising Policies state advertisers should not be charged for clicks or impressions Meta determines are invalid | S6 |
| Explicit invalid-click categories | Automated bots, click farms, malicious scripts targeting ads | S6 |
| Explicit invalid-impression categories | Impressions served to fake accounts or generated by automated tools | S6 |
| Accidental clicks covered | Unintentional mobile taps and overlay interference | S6, S1 |
| Automated detection coverage | Catches only a fraction; sophisticated bots with residential proxies and real browsers bypass filters | S6 |
| Evidence standard | Behavioral logs proving automation (not just suspicious patterns) make the difference between approved and denied claims | S6 |
| Traffic quality division | Valid = human visitors; Invalid = automated interactions (crawlers, scrapers, click farms, publisher script engines) | S4 |
| Bot behavior signatures | No scroll, no field corrections, uniform click paths, instant form fills, zero meaningful page engagement | S1, S4 |
| Industry invalid-traffic range | 9%–20% of paid clicks across audits | S5 |
| Claim approval rate with structured evidence | 83% of filed claims approved across 2,500+ brand audits | S2, S5 |
Limitations: When This Guidance Does Not Apply
- Brand awareness / reach campaigns: Invalid-impression refunds follow similar rules but require impression-level evidence (viewability, render completion), which is harder to capture without client-side tracking.
- WhatsApp / Messenger click-to-message ads: The click happens inside Meta's surface; you have no landing page to instrument. Refunds depend entirely on Meta's internal detection.
- Advantage+ Shopping / Performance Max equivalents: Automated placement expansion can mix valid and invalid inventory. You must segment post-hoc by placement breakdowns.
- Agency-managed accounts without pixel access: You cannot collect client-side behavioral data without the pixel or a first-party script on your domain.
- Historical claims beyond Meta's lookback window: Meta does not publish a fixed lookback period; older clicks become harder to substantiate as platform logs age out.
Terminology Quick Reference
- fbclid: Facebook Click Identifier — the query parameter appended to your landing URL that ties a click to a specific ad, placement, and auction.
- Pixel poisoning: When bot traffic fires conversion events, teaching Meta's optimization algorithm to find more traffic that looks like bots.
- Client-side audit: Behavioral analysis running in the visitor's browser (JavaScript), capturing mouse, scroll, focus, fingerprint, and timing data.
- Server-side audit: Log analysis of IP, user-agent, headers — misses bots that rotate residential IPs and spoof headers.
- Conversion gap: Clicks recorded by Meta with zero corresponding session activity on your site.
- Refund-ready report: Evidence package formatted to Meta's review specifications: click IDs, timestamps, campaign hierarchy, session recordings, signal-by-signal reasoning.
Practical Scenarios: Match Your Situation to the Right Path
Scenario A: Sudden lead spike from Audience Network, zero sales calls
Placement report shows 80% of leads from Audience Network. CRM shows zero connected calls. Session data reveals 90% of those clicks had zero scroll, sub-second form submit, identical canvas fingerprints. Action: Build placement-specific evidence package; file claim for invalid clicks from automated scripts on Audience Network.
Scenario B: Competitor IP range clicking brand terms daily
You identify a competitor's office IP clicking your brand ads 20 times/day. Sessions show normal scroll, dwell time, navigation to pricing page. Action: Not refundable as invalid traffic. Add IP exclusion in Ads Manager; consider bid adjustment. Only refundable if you prove those sessions were automated (they weren't).
Scenario C: High CPL, leads have fake names but human session behavior
Leads enter "John Smith" / "test@test.com" but sessions show scrolling, field corrections, 45-second dwell. Action: Targeting/creative problem. Tighten audience, add qualifying questions, improve creative clarity. Do not file invalid-traffic claim.
Scenario D: Mobile campaign, 40% bounce under 1 second, no scroll
Creative has a sticky header that overlaps the CTA on certain devices. Sessions show immediate bounce, zero interaction. Action: Fix the UX issue first. Then file claim for accidental clicks on affected device/placement combos with session evidence.
FAQ: Next Questions Advertisers Ask
Does Meta automatically refund invalid traffic it detects?
No. Meta's automated systems catch a fraction and may issue credits silently, but the majority of sophisticated invalid traffic bypasses filters. You must proactively file a claim with evidence to recover that spend.
How far back can I claim refunds for invalid clicks?
Meta does not publish a fixed lookback window. In practice, claims are strongest within 30–60 days. Older claims face log retention limits and reviewer skepticism. Preserve data continuously.
What if my agency manages the ad account but I own the website?
You need the agency to share click IDs (fbclid) and campaign structure, and you need to install client-side tracking on your landing pages. Without both, you cannot match clicks to behavioral evidence.
Can I use Google Analytics 4 data as evidence for a Meta refund?
GA4 shows aggregated sessions, not click-ID-level behavioral fingerprints. Meta reviewers ask for session recordings tied to specific fbclids. GA4 alone is insufficient.
What's the difference between invalid traffic and click fraud?
Click fraud is a subset of invalid traffic — intentional, malicious automation (competitor bots, click farms). Invalid traffic also includes accidental clicks and non-malicious automation (scrapers, crawlers). Meta's policy covers both; the evidence standard is the same: prove automation.
How long does a Meta refund claim take?
No published timeline. Once approved, credits typically appear within 5–10 business days. The review period varies from days to weeks depending on evidence completeness and queue depth.
Should I block suspected bot IPs in Ads Manager while a claim is pending?
Yes. IP exclusions stop future waste. They don't affect the claim for past clicks — those are already billed. Keep the exclusion list updated as you identify new clusters.
Decision Rule: When to File vs. When to Fix
File a refund claim when you have click-ID-level behavioral evidence of automation clustered by placement or creative. Fix targeting, creative, or landing page when the traffic shows human behavior but poor business outcomes. The line is technical, not commercial: automation signatures = refund path; human signatures = optimization path.
If you're unsure which side your traffic falls on, start with a structured audit that compares ad-platform data, website sessions, and CRM outcomes before changing targeting or making a refund request. That audit is the foundation for either a successful claim or a smarter campaign adjustment.
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.