TL;DR
- Google published a help page, 'Prevent invalid leads', stating its invalid-traffic filters do not stop fake form submissions on their own and lead quality is a shared responsibility, reported by PPC Land on 20 September 2026.
- The reason is timing: most traffic checks run after the ad serves, so a bot or user can submit junk before a click is judged invalid.
- Google recommends three advertiser-side checks: reCAPTCHA on the form, double opt-in email confirmation, and server-side validation.
- Junk leads are false conversions that train Smart Bidding to buy more of the same, so cleaning forms also protects the bidding.
- The stronger fix is to count only qualified leads as conversions and pass them back via offline conversion import or enhanced conversions for leads.
Google has published a Google Ads help page stating plainly that its invalid-traffic filters do not, on their own, stop fake submissions reaching your lead forms, and that keeping lead quality high is a shared responsibility between Google and the advertiser. PPC Land reported the document, titled "Prevent invalid leads", on 20 September 2026. The page puts three checks on the advertiser's side: reCAPTCHA, double opt-in email confirmation, and server-side validation.
The reason Google gives is timing. Most of its traffic checks run after an ad has served, so a bot or a careless user can still reach your site and submit junk into a contact form before any filter applies. For anyone paying Google to generate leads, that is the whole problem in one sentence: the money is spent, the click is filtered later, and the bad form entry is already in your pipeline.
What Google actually put in writing
The page sits under the Fix issues and Reporting issues sections of the Google Ads Help Centre, carries a 2026 copyright line and no publication date, and was surfaced by PPC News Feed, which credited Hana Kobzová with spotting it. Google's wording is blunter than most of its help material.
| What Google says | What it means for you |
|---|---|
| Invalid-traffic filters "don't prevent invalid leads on their own" | Do not assume Google's automatic protection keeps junk out of your forms. |
| "Most traffic checks happen after your ad serves" | Filtering is retrospective; a submission can land before a click is judged invalid. |
| Lead quality is a "shared responsibility" | Google expects you to add form-level defences, not rely on the platform alone. |
| Recommended checks: reCAPTCHA, double opt-in, server-side validation | Three specific defences to put on your own forms. |
Why junk leads cost more than wasted time
A fake form fill wastes more than the sales team's time. If you count form submissions as conversions, and most lead-gen accounts do, then every junk lead is a false conversion, and Smart Bidding optimises toward more of exactly that. The bidding system cannot tell a real enquiry from a bot fill unless you tell it; it sees a conversion and bids to find more like it. Feed it junk and it learns to buy junk.
That is the mechanism that turns a form-spam problem into a budget problem. The wasted spend goes beyond the clicks that produced the fake leads. It is also the future spend Smart Bidding directs toward the sources and audiences that generate them, because it was taught those were good. Cleaning the forms is therefore also protecting the bidding, which is the part that compounds.
The three checks, and what each one stops
Google's three recommendations sit at different points in the submission, and they catch different things.
- reCAPTCHA sits on the form itself and filters automated bots at the point of submission. It is the first line, and it stops the crude, high-volume automated fills before they ever become a lead.
- Double opt-in email confirmation requires the submitter to click a link in an email before the lead is treated as real. It filters fake or mistyped email addresses and low-intent submissions, because a bot or a careless user rarely completes the confirmation step.
- Server-side validation checks the submission on your server rather than trusting the browser, verifying that fields are well-formed, that the email and phone resolve, and that the submission was not forged. It is the defence that catches what gets past the first two.
None of the three is new technology, and that is the point. Google is not announcing a feature; it is telling advertisers that standard form hygiene is now their job, and writing it into the help centre so the expectation is on the record.
The step Google did not spell out: keep junk out of your conversions
Blocking submissions is half the job. The other half is making sure the junk that still gets through does not train your bidding. The durable fix is to stop counting a raw form fill as the conversion Smart Bidding optimises toward, and instead count a lead only once it has cleared a quality bar.
In practice that means treating a verified or qualified lead as the conversion, not the form submission itself, and passing that qualified signal back to Google through offline conversion import or enhanced conversions for leads. When the bidding optimises toward leads your sales team actually accepted, rather than toward form fills, the incentive to buy junk disappears at the source. The form-level checks reduce the junk; the conversion definition decides whether the junk that remains poisons your bidding.
What this means for Thai advertisers
Lead-form spam is heavy in the Thai market, where a large share of paid traffic is mobile and form-farming is common, so the retrospective-filtering gap Google describes bites harder here than the help page's neutral tone suggests. A Thai lead-gen account that trusts Google's invalid-traffic protection and counts every form fill as a conversion is very likely training its bidding on a diet that includes a lot of junk.
Two local adjustments help. First, add the three checks, with a particular note on phone numbers: many Thai lead forms collect a phone number rather than an email, so server-side validation of Thai mobile formats and, where possible, a verification step matter as much as email double opt-in. Second, and more important, define the conversion as a qualified lead and pass that back, because in Thailand the real qualification often happens in a following LINE conversation rather than on the form, and that is the signal worth optimising toward. This is core Google Ads hygiene, and the measurement side of it belongs with a clean analytics and conversion tracking setup so the qualified-lead signal actually reaches the bidding.
How to tell whether you already have a junk-lead problem
Before adding defences, confirm the problem is real in your account, because the fix has a cost in friction and you want to aim it. Three checks surface it quickly.
- Compare lead-to-sale rate by source. If one campaign or keyword produces many form fills but almost no accepted leads, that is the signature of junk, not of a weak sales follow-up.
- Look for form-fill spikes with no matching calls or replies. A jump in submissions that your team never manages to reach on the phone or on LINE is usually bots or incentivised fills, not demand.
- Watch for a conversion rate that looks too good. A landing page suddenly converting far above its history, especially from broad or display placements, often means the form is being farmed rather than that the page improved.
If those checks come back clean, the three form defences are cheap insurance. If they come back dirty, the conversion-definition fix below is the one that actually stops the bleeding.
What Google did not say
The page is guidance, not a fix. Google did not commit to catching invalid leads before they are submitted, and its framing of the problem as a shared responsibility is, in effect, a statement that it will continue to filter after the fact. It did not say whether it will offer any pre-submission protection natively, nor did it quantify how many invalid leads slip through the existing filters. And it did not address refunds for spend on clicks that produced only junk leads, which leaves the cost of the gap with the advertiser. Treat the page as confirmation that form defences are your responsibility, not as a promise that the problem is being solved upstream.
Frequently asked questions
Do Google Ads invalid-traffic filters stop fake leads?
No. Google's own help page states the filters "don't prevent invalid leads on their own", because most traffic checks happen after the ad serves, so a bot or user can submit junk to a form before a click is judged invalid. Google calls lead quality a shared responsibility.
What three checks does Google recommend?
reCAPTCHA on the form to stop bots at submission, double opt-in email confirmation so a lead counts only after the submitter clicks a link, and server-side validation to verify the submission on your server rather than trusting the browser. All three sit on the advertiser's side.
Why do junk leads hurt more than wasted time?
If you count form fills as conversions, each junk lead is a false conversion, and Smart Bidding optimises toward more like it. The bidding then directs future spend toward the sources that produce junk, so cleaning the forms also protects the bidding.
How do I stop junk leads from training my bidding?
Count a lead as a conversion only after it clears a quality bar, and pass that qualified signal back with offline conversion import or enhanced conversions for leads. When bidding optimises toward accepted leads rather than raw form fills, the incentive to buy junk disappears.
Is this a new Google feature?
No. The three checks are standard form-hygiene techniques, not a product. Google published the guidance to put on the record that keeping invalid leads out is the advertiser's responsibility, since its filters act after the ad has served.
The bottom line
Google has said in writing what experienced advertisers already suspected: its invalid-traffic filters do not keep fake submissions out of your lead forms, and defending the form is your job. Add reCAPTCHA, double opt-in and server-side validation to stop the junk, and, more importantly, count only qualified leads as conversions so the junk that slips through cannot teach Smart Bidding to buy more of it. For Thai lead-gen accounts, where form spam is heavy and qualification often happens later on LINE, that conversion definition is the difference between bidding toward customers and bidding toward noise.
