What Evidence Do You Need for an Invalid Click Refund?

Google and Meta do not issue refunds on suspicion alone. They require a structured evidence package that ties each disputed click to technical signals proving the visitor was automated, fraudulent, or otherwise invalid. The core items are click identifiers (GCLID for Google, fbclid for Meta), precise timestamps, IP addresses, and client‑side behavioral data — mouse paths, scroll behavior, form interaction timing, and session replays — that demonstrate the absence of human intent.

What Counts as Invalid Click Evidence

Ad platforms categorize invalid traffic into buckets they will credit if you prove the clicks belong there. Google lists three main categories: competitor click activity, publisher click fraud, and bot traffic or web scrapers. Meta focuses on lead‑quality signals — disconnected numbers, invalid email domains, burst submissions, and sessions with no scrolling or field corrections. In both cases the evidence must link a specific paid click to a specific technical anomaly.

Raw server logs are not enough. Platforms want client‑side proof captured in the browser: pointer tremors, scrollbar interactions, iframe context checks, and timing patterns that automation tools fail to replicate. BotRefund runs 106 independent browser checks — such as scrollbar width leaks and clean‑context iframe tests — and feeds each signal into an AI model that weighs the full pattern rather than relying on any single rule.

Platform‑Specific Requirements

Google Ads

Google’s Click Quality team asks for GCLID logs, the formal investigation form, and a narrative that explains why the automated filters missed the traffic. The guide on BotRefund’s blog notes that Google’s real‑time filters often miss modern residential proxy networks and competitor click fraud, so advertisers must compile client‑side behavioral proof logs themselves.

Meta Ads

Meta’s review looks for placement‑level spikes, conversion events with no meaningful page engagement, and CRM outcomes that contradict reported lead counts. The Meta invalid traffic guide recommends preserving attribution before changing the campaign, then comparing ad‑platform data, website sessions, and CRM results side by side.

Technical Evidence Types That Platforms Accept

• Click identifiers: GCLID (Google) or fbclid (Meta) captured on landing‑page load.
• Timestamps: Millisecond‑precision visit start, click, and conversion times.
• IP and network context: IP address, ASN, proxy/VPN flags, geolocation mismatches.
• Behavioral biometrics: Mouse tremor, scrollbar interaction, click‑path curvature, typing cadence.
• Browser fingerprint consistency: Canvas, WebGL, audio context, and iframe context checks that reveal automation frameworks.
• Session replay: Video‑style reconstruction of the visit for human reviewers.

Each signal is an independent fact. BotRefund’s documentation emphasizes that a single anomaly is not a verdict; privacy tools, corporate networks, and unusual devices can create outliers for real people. The platform cross‑checks every signal against browser, network, device, and behavior data before scoring a visit.

Building a Complete Evidence Package

1. Preserve attribution. Do not pause campaigns or change UTM parameters until you have exported click IDs and session data.
2. Collect client‑side logs. Deploy a script that records the 106 behavioral checks on every paid visit.
3. Map clicks to spend. Join GCLID/fbclid data with your ad‑platform billing export so each disputed click shows its cost.
4. Filter for high‑confidence sessions. Use the AI score (BotRefund reports up to 99% accuracy when evidence supports it) to isolate visits the model flags as bot.
5. Export a platform‑ready report. Format the evidence as a readable PDF or CSV that Google’s Click Quality team or Meta’s support can review without translating security logs.
6. Submit the formal request. File Google’s investigation form or open a Meta support case with the report attached.

Common Mistakes That Weaken Refund Claims

• Submitting only server‑side logs without browser‑level behavioral data.
• Changing campaign structure before exporting click IDs, breaking the attribution chain.
• Treating every low‑quality lead as fraud instead of separating bad targeting from automation.
• Providing raw JSON or security‑tool output that reviewers cannot interpret quickly.
• Failing to connect each disputed click to a specific dollar amount in the billing export.

How BotRefund Automates Evidence Collection

BotRefund adds a lightweight script to your site in about one minute. It captures the 106 behavioral checks on every visit, associates each session with its click ID and campaign metadata, and continuously scores visits with an AI model trained on corroborated patterns. When the model reaches high confidence, the platform builds a refund‑ready report that includes session replays, signal breakdowns, and a spend map — formatted for Google and Meta review teams. The homepage states that BotRefund proves bot clicks, negotiates with Google and Meta, and gets money back, with a reported refund approval rate across client claims and average ad spend recovered from billing disputes.

Limitations and When Evidence Falls Short

Platforms reserve the right to deny claims even with strong evidence. Google may reject clicks it classifies as accidental (double‑clicks, fat‑finger mobile taps). Meta may treat burst leads as low‑intent human traffic if no technical automation signals appear. Evidence older than the platform’s lookback window (Google allows disputes back to 2017 per BotRefund) may be excluded. Corporate VPNs, privacy browsers, and accessibility tools can create false positives that require manual review. No third‑party tool can guarantee a refund; the decision always rests with the ad platform.

Key Facts

Metric	Detail	Source
Detection checks per visit	106 independent browser, network, device, and behavior signals	S4, S6
Model accuracy claim	Up to 99% when session evidence supports the prediction	S4, S6
Setup time	About one minute to add script and start free bot audit	S2
Refund lookback (Google)	Recover bot‑click refunds from Google Ads spend dating back to 2017	S2
Platforms supported	Google Ads and Meta (Facebook/Instagram) billing disputes	S2, S3, S7
Report output	Refund‑ready PDF/CSV with session replays, signal breakdown, spend map	S3, S5

FAQ

How far back can I claim invalid clicks on Google Ads?

Google allows disputes on spend dating back to 2017, but you must have the click IDs and behavioral logs for those periods. Most advertisers only retain recent data, so ongoing collection is essential.

Does Meta require different evidence than Google?

Yes. Meta weighs lead‑quality signals — contactability, CRM outcome, placement‑level patterns — more heavily than pure click‑level behavioral data. You still need fbclid, timestamps, and session replays, but the narrative must connect to downstream sales results.

Can I use Cloudflare or WAF logs instead of client‑side tracking?

Edge logs show network‑level anomalies but lack the browser behavioral signals (mouse tremor, scrollbar interaction, iframe context) that ad platforms explicitly request for refund reviews. They complement but do not replace client‑side evidence.

What if my site already uses Google Analytics 4?

GA4 does not capture the micro‑behavioral signals (pointer paths, scrollbar width, clean‑context iframe) needed to prove automation. It also strips GCLID after the landing page unless you configure cross‑domain linking carefully. A dedicated evidence layer is still required.

How long does a refund investigation take?

Google’s Click Quality team typically responds in 2–4 weeks. Meta support timelines vary. Submitting a complete, platform‑formatted report upfront reduces back‑and‑forth delays.

Is there a minimum spend threshold to file a claim?

No published minimum. However, the effort of compiling evidence pays off most when monthly ad spend is high enough that a 10–20% invalid‑click rate represents meaningful dollars. BotRefund’s pricing tiers start at under $10,000/mo ad spend.

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

• What evidence should I collect before requesting a refund? | ...
• A Guide to Google Ads Refunds: How to Handle Invalid Clicks and ...
• How to Claim Your Google Ads Refund for Invalid Clicks | ClickSambo ...

Learn more

Visit the website for more information.