● High signal · if you run lead generation

You Can Complain About Fake Leads. What You Get Back Is a Click.

What Google announced

There was no announcement. A help page titled Prevent invalid leads now sits as the last item in the Google Ads "Reporting issues" topic, directly after About the Invalid Activity Credit Report. It carries no publication date and no changelog entry, which is worth stating plainly rather than dressing it up as news.

What makes it worth a brief is not that it is new. It is that it writes down, in Google's own words, where the company believes its responsibility ends. The opening is unusually direct: "Google Ads filters out invalid traffic to protect your ad budget. However, these filters don't prevent invalid leads on their own. Most traffic checks happen after your ad serves. Because of this, users or bots can still reach your website and submit fake or low-quality lead forms."

And then the division of labor: "You capture leads on your website or in your customer relationship management (CRM) system. Therefore, high lead quality is a shared responsibility. Google's defenses protect you from charges for invalid traffic, but you must also implement technical safeguards."

What it actually means

Start with what genuinely works, because the brief is worthless if it overstates the case. Invalid traffic filtering is a real service doing real work. Per Google's invalid traffic documentation, activity caught before the end of the month is "automatically removed from your billing and campaign reports, so no refunds are necessary." That is the good version: you are never billed, and your numbers never showed it. If you have seen an "Invalid activity" credit under Billing, Summary, Adjustments, the slower version also worked.

Now the part that gets misread across most of the agencies I know. The working assumption in a lot of shops is that Google's fraud systems cover lead quality and you dispute whatever they miss. Half of that is true, and the true half is narrower than it sounds.

You can absolutely raise bad leads. Google's own guidance asks for them: if your issue relates to invalid leads, supply "GCLIDs for each lead" and "Your assessment of each lead, such as outcomes from emailing or calling them." If the investigation turns up invalid traffic the filters missed, Google credits it. So the flat claim that fake leads get you nothing is wrong, and any practitioner who has filed one will know it.

The distinction that survives is the unit. The lead is evidence. The click is the currency. Google reimburses the media cost of the traffic it concludes was invalid, and nothing else, which means the credit never touches the part of the loss that actually hurts: the rep who called the number, the hour spent qualifying a fake, the CRM polluted with records your sales team now distrusts. In a lead gen account, media is frequently the smallest line in the cost of a bad lead. You are being made whole on the cheapest component.

The lead is the evidence. The click is the currency. You get reimbursed in the wrong unit.

Then there is the reconciliation problem, which is the most checkable thing in this brief and the one almost nobody has written down. Google states it under a heading that says exactly what it does: "Campaign metrics don't adjust for past activity credits." The text reads: "Google freezes campaign metrics at the end of the month so your data aligns with your monthly invoice. Therefore, credits for past invalid activity may appear on your invoice but won't retroactively adjust your campaign data in Google Ads. However, Google removes invalid traffic caught before the end of the bill cycle from your metrics."

Read that third sentence, because it stops the claim from being sloppier than the truth. Fast catches do clean your metrics. Slow catches do not. So a month that gets financially corrected in November for September activity keeps September's inflated click count and understated CPA permanently. If you have ever pulled a monthly report, set it beside the invoice, found a gap you could not explain, and quietly moved on, that is the mechanism. It takes five minutes to confirm in your own account.

This is the second reporting surface this quarter where the number you see and the number the system used are not the same object. The 7-day offline conversion gate splits attribution reports from Smart Bidding, and the Performance Max cross-network filter change returns empty rather than erroring. Add credits that never reach the metrics and you have three separate reasons a September number will not reconcile, none of which throws a warning.

One honest complication, since the site's credibility depends on including it: conversion data is not perfectly frozen either. Google notes it removes some invalid conversions "if they originate from invalid traffic, or if they remain invalid for longer than 13 months," and that this "might show as a small drop in conversions over time." So conversions can drift retroactively while clicks and cost do not. That asymmetry is its own small reporting hazard.

The last piece is the clock. Google limits investigations to the past 60 days, stated three separate ways in the documentation, including "Google limits investigations to the past 60 days." The limit is on the age of the activity, not on a deadline measured from an invoice. That distinction matters operationally: a quarterly cadence cannot protect the first month of the quarter, because by the time you look, it is out of range.

There is a structural reason this is getting worse rather than better for lead gen accounts specifically. Google is moving lead generation toward models where it defines and prices the unit, which is the whole point of the Local Services Ads move into Performance Max pay-per-lead. The more the platform owns the definition of a valid lead, the more the question in this brief stops being a billing footnote and starts being the commercial relationship. Feeding that machinery better data is the counterweight, which is what the journey-aware bidding audit is really about: if your offline conversion import cannot tell a qualified lead from a form submission, nothing downstream can either.

On the strategic side of this, Uncommon Move's essay The Seller's Unit argues the version of this that belongs in a leadership conversation: when the platform's AI defines what counts as a valid lead for billing, you have lost custody of your own denominator. A companion piece, Who Counts the Conversion?, extends it to what happens when two platforms each define and count their own. This brief stays on the mechanism. Those cover who gets to define the terms.

The bottom line

No setting changed and there is nothing to opt out of. What is worth knowing is that the boundary between Google's problem and yours is documented, it sits further toward you than most teams assume, and the only part you can still contest runs on a rolling 60-day clock that nobody will remind you about. The credit, when it comes, arrives in clicks. The cost was never denominated in clicks.

Frequently asked