Seatext library / BotRefund evidence
How to Request a Refund for Invalid Traffic on Meta Ads: Step-by-Step Process
Meta does refund invalid clicks and impressions, but its automated systems catch only a fraction of bot traffic. To recover money, you must file a proactive claim with behavioral evidence — session recordings, click...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
Yes, Meta has a formal policy that says advertisers should not be charged for clicks or impressions it determines are invalid — including automated bots, click farms, and malicious scripts. However, Meta's automated detection catches only a portion of invalid activity. Sophisticated bot traffic using realistic fake accounts, residential proxies, and browser automation routinely bypasses those filters. To recover spend from that traffic, you need to proactively file a claim with evidence that shows the traffic was automated, not merely low-quality.
To request a refund, file a claim through Meta's support. You must include click IDs, campaign details, timestamps, session recordings, and signal-by-signal reasoning for each suspicious interaction. Then track your ticket until you get a decision.
How to Request a Refund at a Glance
- Preserve attribution — do not change campaigns before collecting evidence.
- Run a structured audit — compare Meta Ads reports, website analytics, and CRM outcomes.
- Identify behavioral patterns — look for fast form fills, no scrolling, uniform click paths, and unusual timing.
- Build a refund-ready report — include click IDs, timestamps, session recordings, and signal-by-signal analysis.
- Submit via Meta support — open a ticket, attach your evidence, and state the exact refund amount by campaign.
- Follow up — monitor the ticket, respond to questions, and escalate if needed.
What Counts as Invalid Activity on Meta Ads
Meta defines invalid activity broadly. The main categories that qualify for refunds include:
- 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 scripts that never represent a human view.
- Accidental interactions: Unintentional taps on mobile ads that Meta's systems can identify as non-genuine.
Not every bad lead is a bot. A weak campaign can attract real people who aren't ready to buy. Treating every unresponsive contact as fraud can make you exclude a valuable audience. Start with a structured audit that compares ad-platform data, website sessions, and CRM outcomes before changing targeting or making a refund request.
Why Meta's Automated Detection Isn't Enough
Meta's automated systems analyze traffic patterns at the server level — looking for rapid clicking, duplicate click signatures, known bad IP ranges, and abnormal patterns. These systems are sophisticated but far from perfect. They struggle to detect advanced botnets that use residential proxies, realistic browser fingerprints, and human-like behavior patterns.
Because Meta's refund process is less structured than Google's, having the right evidence is even more critical. Behavioral logs showing that traffic was automated — rather than just suspicious — make the difference between an approved and denied claim.
Evidence You Need for a Successful Claim
Meta reviewers expect evidence in a specific format. The strongest claims include:
- Click IDs and campaign details for every flagged interaction
- Timestamps showing when each click occurred
- Session recordings that reveal non-human behavior (no scrolling, no field corrections, uniform click paths, zero meaningful time on page)
- Signal-by-signal reasoning across 110+ behavioral, browser, hardware, network, and attribution signals
- Attribution preserved before any campaign changes — keep campaign, ad set, creative, and placement data intact
Client-side tracking is essential here. Server-side logs (IP addresses, user agents, request headers) catch basic scrapers but miss advanced botnets. Client-side audits analyze the visitor's actual browser behavior — mouse movements, scroll depth, form interaction timing, and device fingerprinting — which is what Meta's reviewers need to see.
Step-by-Step Process to File a Refund Request
- Preserve attribution before changing anything. Do not pause campaigns, adjust targeting, or modify creatives until you've captured the full data trail. Changing the campaign destroys the evidence trail Meta needs.
- Run a structured audit. Compare three data sources: Meta Ads Manager reports, your website analytics (session-level), and CRM outcomes (contactability, qualification, revenue). Look for discrepancies — high reported leads but zero calls connected, demos booked, or qualified opportunities.
- Identify repeatable technical patterns. Focus on signals that bots leave: unusually fast form completion, identical field structures across submissions, sudden placement-level spikes, conversion events with no meaningful page engagement, bursts of leads at unusual hours.
- Build a refund-ready report. Format each finding with click IDs, campaign details, timestamps, session recordings, and signal-by-signal reasoning. The report must match the format Meta's review teams use to evaluate invalid traffic claims.
- Submit the claim through Meta's support channel. Open a support ticket, attach your evidence package, and clearly state the refund amount requested with a breakdown by campaign, ad set, and placement.
- Track and follow up. Meta's process has no public SLA. Monitor the ticket, respond promptly to any requests for additional information, and escalate if the initial review misses key evidence.
Common Mistakes That Get Claims Denied
| Mistake | Why It Fails | What to Do Instead |
|---|---|---|
| Submitting only Ads Manager screenshots | Shows reported metrics, not proof of automation | Include session recordings and client-side behavioral logs |
| Changing campaigns before preserving data | Destroys the attribution trail Meta needs | Freeze campaign structure until audit is complete |
| Treating all bad leads as bots | Weakens credibility; real low-intent traffic exists | Distinguish automated patterns from human quality variation |
| Using only server-side logs | Misses advanced bots with residential proxies | Deploy client-side tracking for browser-level evidence |
| Vague refund amount without breakdown | Reviewers can't verify specific invalid interactions | Itemize by click ID, campaign, placement, and date |
Key Facts About Meta Ads Invalid Traffic Refunds
| Fact | Details |
|---|---|
| Meta's refund policy | Advertisers should not be charged for clicks/impressions Meta determines are invalid (bots, click farms, malicious scripts, accidental clicks) |
| Automated detection coverage | Catches only a fraction of invalid activity; sophisticated bots routinely bypass filters |
| Claim requirement | Proactive filing with behavioral evidence is required for traffic that bypasses automated detection |
| Evidence format | Click IDs, campaign details, timestamps, session recordings, signal-by-signal reasoning in platform-review format |
| Process structure | Less structured than Google's; evidence quality is the primary determinant of approval |
| BotRefund approval rate | 83% of filed claims approved across 2,500+ audits |
| Detection confidence | 99% confidence in flagged bot traffic using 110+ behavioral, browser, hardware, network, and attribution signals |
Limitations and When This Advice Doesn't Apply
- Genuine low-intent traffic: Real humans who click but don't convert are not eligible for refunds. The distinction is evidence of automation, not poor lead quality.
- Campaigns already modified: If you've paused campaigns, changed targeting, or swapped creatives before preserving attribution, the evidence trail may be unrecoverable.
- No client-side tracking installed: Without browser-level session data, you cannot produce the behavioral evidence Meta reviewers require for sophisticated bot traffic.
- Small spend thresholds: The effort of building a forensic evidence package may not justify the potential recovery for very small budgets.
- Non-Meta inventory: This process applies only to Meta Ads (Facebook, Instagram, Audience Network). Google Ads has a separate invalid activity credit system.
Frequently Asked Questions
How long does Meta take to review a refund claim?
Meta does not publish a service-level agreement for invalid traffic reviews. Resolution time varies from a few days to several weeks depending on claim complexity and reviewer workload. Prompt responses to follow-up questions help avoid delays.
Can I get a refund for invalid impressions, not just clicks?
Yes. Meta's policy covers invalid impressions served to fake accounts or generated by automated scripts. The evidence requirements are similar — you need to show the impressions were delivered to non-human viewers.
What if Meta's automated system already credited some invalid activity?
Automated credits only cover what Meta's systems caught. You can still file a claim for additional invalid traffic that bypassed automated detection. The two processes are independent.
Do I need to give Meta access to my ad account?
No. You submit evidence through a support ticket. Meta reviewers evaluate the documentation you provide. They do not require direct account access for the claim process.
How much evidence is enough for a claim?
There's no fixed threshold, but claims with session-level behavioral data (recordings, 110+ signal analysis) for each flagged click have significantly higher approval rates than claims with only aggregate metrics or server logs.
Can I file a claim for past months, or only recent activity?
Meta's policy doesn't specify a strict lookback window in public documentation, but older claims are harder to substantiate because session data and attribution trails degrade over time. File as soon as you identify the pattern.
What happens if my claim is denied?
You can appeal with additional evidence. The most common reason for denial is insufficient proof of automation — reviewers saw suspicious patterns but not conclusive behavioral evidence. Strengthening the client-side data package and resubmitting often changes the outcome.
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.
Learn more
Visit the website for more information.