Seatext library / BotRefund evidence

How to Report Invalid Traffic to Meta and Get a Refund: Step-by-Step Process

Meta refunds invalid clicks and impressions when you file a claim with behavioral evidence showing automated traffic. Go to Ads Manager > "Report issue" > "Bad clicks," attach click IDs, session recordings, and signal-by-signal...

Built for advertisers who need clear, refund-ready traffic evidence.

Quick answer: To report invalid traffic to Meta, go to Ads Manager > select the campaign/ad set > click "Report issue" > choose "Bad clicks" > attach evidence (click IDs, session recordings, signal-by-signal reasoning) > submit for review.

Meta has a formal policy stating advertisers should not be charged for clicks or impressions it determines are invalid, including automated bots, click farms, accidental taps, and malicious scripts. However, Meta's automated detection catches only a fraction of invalid activity. Sophisticated bot traffic using realistic fake accounts, residential proxies, and browser automation routinely bypasses filters. To recover spend, you must proactively file a claim with evidence that proves the traffic was automated rather than merely suspicious.

What Counts as Invalid Traffic on Meta Ads

Meta defines invalid activity broadly across several categories. Invalid clicks include those generated by automated bots, click farms, or malicious scripts targeting your ads. Invalid impressions cover impressions served to fake accounts or generated by automated scripts. The platform also considers accidental clicks — unintentional taps on mobile ads — as invalid. Critically, 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 valuable audiences.

Why Meta's Automated Detection Misses So Much Invalid Traffic

Meta's systems analyze click frequency, IP addresses, and conversion-gap patterns at the server level. These catch basic scraper bots and known bad IP ranges but struggle against advanced botnets that mimic human behavior. Bots using residential proxies, browser automation, and realistic fake accounts appear as legitimate users in server logs. The platform has no incentive to flag its own revenue, so refunds happen only when advertisers prove the case session by session. Industry audits consistently place automated traffic between 9% and 20% of paid clicks.

Evidence You Need for a Successful Refund Claim

Behavioral logs showing traffic was automated — rather than just suspicious — make the difference between an approved and denied claim. Meta's reviewers need click IDs (fbclid), campaign details, timestamps, session recordings, and signal-by-signal reasoning. Server-side data alone (IP addresses, user agents, request headers) rarely suffices because advanced bots spoof these. Client-side audits that capture browser behavior — no scrolling, no field corrections, uniform click paths, zero meaningful time on page — provide the forensic evidence Meta accepts. BotRefund combines 110+ behavioral, browser, hardware, network, and attribution signals to identify automated traffic with 99% confidence and formats findings into refund-ready reports.

Step-by-Step: How to Report Invalid Traffic in Ads Manager

  1. Preserve attribution before changing anything. Keep campaign, ad set, creative, and placement IDs intact. Do not pause or edit the campaign until you've exported the data.
  2. Gather behavioral evidence. Collect session recordings, click IDs, timestamps, and client-side signals (mouse movements, scroll depth, form interaction timing) that show automated patterns: instant form submissions, no scrolling, identical field structures, bursts of conversions at unusual hours.
  3. Correlate with CRM outcomes. Match ad-platform leads to downstream results: disconnected numbers, invalid email domains, no calls connected, zero qualified opportunities. A high reported lead count paired with no sales engagement is a strong signal.
  4. Open the reporting flow. In Ads Manager, navigate to the campaign or ad set, click "Report issue," then select "Bad clicks" or "Invalid traffic."
  5. Attach your evidence package. Upload the refund-ready report with click IDs, campaign details, timestamps, session recordings, and signal-by-signal reasoning. Structure the data in the format Meta's review teams expect.
  6. Submit and track the case. Save the case ID. Meta's review timeline isn't published; credits typically appear within 5–10 business days after approval, but the review itself can take weeks.

Common Mistakes That Get Claims Denied

  • Submitting only server-level data (IPs, user agents) without client-side behavioral proof.
  • Confusing low-quality leads with invalid traffic — real humans who don't convert aren't bots.
  • Filing too late after campaign changes have overwritten attribution data.
  • Providing generic "invalid traffic estimates" instead of session-by-session explanations.
  • Not correlating ad clicks to CRM outcomes, leaving reviewers no way to verify the waste.

What Happens After You Submit a Claim

Meta's review team evaluates your evidence against their internal signals. If approved, the credit appears on your billing statement. The process is less structured than Google's invalid activity credit system, so evidence quality is even more critical. Across 2,500+ brands audited, 83% of BotRefund clients recover funds from Google and Meta, driven by 99% bot-detection confidence, reports built in the format platform teams review, and deep experience negotiating claims. If denied, you can escalate with additional evidence, but the first submission is your strongest chance.

Limitations and When This Advice Doesn't Apply

This process covers invalid clicks and impressions as Meta defines them. It does not cover poor targeting, creative fatigue, landing page issues, or genuine low-intent traffic. If your campaign attracts real humans who don't convert, that's a performance problem, not a refund case. Meta does not automatically credit accounts for invalid traffic — you must file a claim. The platform also doesn't publish a fixed review timeline or guarantee approval. Claims for traffic older than 60–90 days are rarely considered. No ad-account access is required for BotRefund's audit; a single script tag installs in about one minute.

Key Facts

FactDetailSource
Meta's refund policyAdvertisers should not be charged for clicks or impressions Meta determines are invalid, including bots, accidental clicks, and non-genuine interactionsS6
Automated detection coverageMeta's systems catch only a fraction of invalid activity; sophisticated bots routinely bypass filtersS6
Evidence standardBehavioral logs proving automation (not just suspicion) are required; client-side signals > server-side dataS6, S3
BotRefund detection confidence99% confidence using 110+ behavioral, browser, hardware, network, and attribution signalsS2
Client recovery rate83% of refund claims filed by BotRefund are approved by ad platforms across 2,500+ brandsS2, S7
Industry invalid traffic range9%–20% of paid clicks are automated per industry auditsS7
Report formatRefund-ready reports include click IDs, campaign details, timestamps, session recordings, signal-by-signal reasoningS2
InstallationOne script tag, ~1 minute, no ad-account access requiredS7

FAQ

Does Meta automatically refund invalid traffic?

No. Meta's policy says advertisers shouldn't be charged for invalid activity, but the platform does not automatically credit your account. You must file a proactive claim with evidence.

What's the difference between low-quality leads and invalid traffic?

Low-quality leads are real humans who aren't ready to buy. Invalid traffic is automated — bots, scripts, click farms. Treating every bad lead as fraud can make you exclude valuable audiences. Start with a structured audit comparing ad-platform data, website sessions, and CRM outcomes.

How long does Meta take to review a refund claim?

Meta doesn't publish a fixed timeline. Once approved, credits typically appear within 5–10 business days, but the review itself can take weeks. File as soon as you have evidence.

Can I get a refund for accidental mobile clicks?

Yes. Meta classifies accidental clicks (unintentional taps) as invalid activity. You still need behavioral evidence showing the pattern — e.g., immediate bounce, zero scroll, no engagement.

What if my claim is denied?

You can escalate with additional evidence, but the first submission is your strongest chance. Most denials come from weak evidence — usually server-level data that shows suspicious patterns but fails to prove automation.

How far back can I claim invalid traffic?

Claims for traffic older than 60–90 days are rarely considered. Preserve attribution data immediately when you suspect a problem.

Do I need to give BotRefund access to my ad accounts?

No. BotRefund installs via a single script tag on your site (~1 minute) and analyzes visitor behavior client-side. No ad-account credentials required.

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.

Learn more