What Evidence Do You Need to Prove Invalid Traffic on Meta Ads? Complete Readiness Checklist

To prove invalid traffic on Meta Ads, you need three core categories of evidence: ad platform performance logs, independent website session data, and clear proof that interactions were automated rather than the result of genuine user interest. Meta’s automated systems only catch a fraction of invalid clicks and impressions, so proactive claims rely on session-level behavioral data, not just server-level IP lists or suspicious lead patterns. This readiness checklist outlines exactly what to gather before you file a refund request to maximize your approval odds.

Invalid traffic on Meta includes clicks from bots, accidental mobile taps, click farm activity, and impressions served to fake accounts. It is distinct from low-quality leads: a real person who fills out your form but never responds is not invalid traffic, even if they are a poor fit for your business. Proving invalid traffic requires showing the interaction was not human-driven, not just that the lead did not convert.

What Qualifies as Invalid Traffic on Meta Ads?

Meta’s Advertising Policies define invalid traffic as any click, impression, or conversion that is not the result of genuine user interest. This covers four common categories:

• Invalid clicks: Clicks generated by automated bots, click farms, malicious scripts, or accidental taps on mobile ads (common in fast-scrolling feed placements).
• Invalid impressions: Impressions served to fake accounts, automated page refresh tools, or non-human browsers that have no intention of engaging with your ad.
• Invalid conversions: Form fills, pixel triggers, or purchase events completed by bots, web scrapers, or automated scripts with no human input.
• Competitor click fraud: Coordinated clicks from rival advertisers intended to exhaust your daily budget or skew your campaign optimization data.

Not every poor-performing lead counts as invalid traffic. A real user who clicks your ad, visits your landing page, and fills out your form but never responds to follow-up is a low-quality lead, not invalid traffic. Meta’s refund system only covers non-human or accidental interactions, so your evidence must prove automation, not just low conversion value.

Why Generic Evidence Fails Meta’s Review Process

Most denied invalid traffic claims share a common flaw: they rely on suspicious patterns rather than proof of automation. Meta’s review teams are trained to reject claims that only include server-level IP lists, vague statements about "bad leads," or unsubstantiated accusations of fraud.

Server-side data like IP addresses and user-agent strings can flag unusual traffic, but they cannot prove a user was non-human. Real users often access the internet via VPNs, mobile networks, or corporate proxies that share IPs with other users. Without behavioral data showing that the traffic completed actions no human could (like filling a 10-field form in 1.2 seconds with no corrections), reviewers cannot confirm the traffic was invalid.

Meta’s refund process is also less structured than Google’s invalid activity credit system, which means there is more room for interpretation during reviews. Claims with clear, session-by-session evidence of automated behavior have a far higher approval rate than claims that only highlight suspicious trends.

Core Evidence Checklist for Meta Invalid Traffic Claims

Use this checklist to gather all required documentation before submitting your claim. Organize all files by date, campaign name, and evidence type to make review as easy as possible for Meta’s team.

• Ad Manager performance logs for the claimed period: Export full reports for clicks, impressions, spend, and conversions broken down by placement, ad set, creative, device, and timestamp. Include screenshots of any anomalous spikes in clicks or conversions that do not align with your campaign changes (e.g., a 300% jump in leads overnight with no new creative or targeting updates). This ties the suspicious activity directly to your Meta ad spend.
• Website session data for matching traffic: Pull session-level reports from Google Analytics or your equivalent tool for the same time period, including session duration, pages per session, bounce rate, and behavior flow. Flag sessions with 0-second duration, no page scrolling, or uniform click paths that do not match real user behavior.
• Screenshots of anomalous traffic patterns: Capture clear, dated screenshots from Ads Manager and your analytics tool showing sudden spikes in clicks or conversions, unusual concentration of traffic from a single placement or device type, or conversion rates that jump without corresponding campaign changes.
• Session recordings or behavioral logs for flagged interactions: If you use a session recording tool, export clips for suspicious sessions: look for instant form completion (under 2 seconds), no field corrections, identical input patterns across multiple leads, or no interaction with page content before conversion. This is the strongest possible proof of non-human activity.
• CRM data linking ad clicks to low-quality outcomes: Export lead records for conversions tied to the claimed period, including contactability status, call connect rates, demo bookings, and follow-up engagement. A high volume of leads with disconnected numbers, invalid email domains, or no follow-up activity supports the claim that traffic was not genuine.
• Meta click IDs (fbc parameters) for flagged interactions: If you store Meta click IDs tied to suspicious sessions, include them in your claim to eliminate any ambiguity about which ad interactions drove the invalid activity. These IDs let Meta’s team trace the click directly from their platform to your website session data.

How to Organize Your Evidence for a Strong Claim

Follow this step-by-step process to structure your submission for the highest chance of approval:

1. Isolate the exact time period and campaign you are claiming for. Do not mix data from multiple campaigns or date ranges, as this will confuse reviewers and lead to a denied claim.
2. Match each piece of evidence to a specific suspicious pattern: for example, pair a screenshot of a click spike with the corresponding session data showing 0-second sessions for those clicks.
3. Label all files clearly with dates, campaign names, and evidence type (e.g., "Campaign_X_July2024_AdsManager_Spike_Screenshot").
4. Write a short, factual summary of the pattern you found, avoiding emotional language or unproven accusations. Stick to observable, data-backed facts only.
5. Submit your claim through Meta’s official invalid traffic dispute form, attaching all organized evidence. Do not submit claims via general support channels, as they will be routed to teams that do not handle refund requests.

Common Mistakes That Void Refund Requests

Avoid these frequent errors that lead to automatic claim denials:

• Submitting only server-side IP logs: IP addresses alone do not prove invalid traffic, as real users often use VPNs or mobile networks that share IPs. Meta requires behavioral proof of automation.
• Claiming all low-quality leads are invalid: If a lead is from a real person who simply is not ready to buy, that is not invalid traffic. Only submit evidence for interactions that show clear automated behavior.
• Misaligning timestamps across data sources: If your ad platform data, session data, and CRM records do not line up by date and time, reviewers will not be able to connect the suspicious activity to your ad spend.
• Submitting claims for activity older than 90 days: Meta only accepts invalid traffic claims for activity that occurred in the last 90 days. Older activity is not eligible for review.
• Including unredacted sensitive customer data: Remove all personally identifiable information (PII) from CRM exports before submitting, to comply with privacy regulations and Meta’s data handling policies.

Frequently Asked Questions About Meta Invalid Traffic Evidence

1. Do I need to install special tracking to collect this evidence?: No, but you will get stronger evidence if you use a client-side session auditing tool that captures behavioral data like scroll depth, form completion time, and mouse movement. Basic Google Analytics data is sufficient for many claims, but session-level logs improve approval odds.
2. How long does Meta take to review a claim?: Meta does not publish a fixed timeline, but most claims are reviewed within 2–4 weeks. Complex claims with extensive evidence may take longer. You will receive a notification once a decision is made.
3. Can I claim refunds for invalid impressions as well as clicks?: Yes, Meta’s policy covers both invalid clicks and invalid impressions, as long as you can prove the impression was served to non-human traffic or fake accounts.
4. What if I don’t have session recordings for the suspicious traffic?: You can still file a claim with Ads Manager logs, analytics data, and CRM records, but approval odds are lower without behavioral proof of automation. Focus on patterns like 0-second sessions or instant form completions that are visible in standard analytics tools.
5. Does Meta refund the full amount for invalid traffic?: If your claim is approved, Meta will issue a credit for the full cost of the invalid clicks or impressions, minus any applicable taxes or fees. Credits are applied directly to your ad account balance.
6. Do I need to prove the invalid traffic caused lost revenue?: No. Meta’s policy states you are not responsible for charges from invalid traffic, regardless of whether the interaction led to a conversion. You only need to prove the traffic was non-human or accidental, not that it cost you sales.