If you count every form submission as a conversion, spam gets fed back to Google as a success signal. Smart Bidding then optimises toward the traffic that produced it, which produces more spam, which reinforces the signal. The fix is to validate before the conversion is reported and feed back only the real leads.
The loop
Most Google Ads accounts count a form submission as a conversion. It is the default setup and it is sensible right up to the moment some of those submissions are not real.
Smart Bidding learns from conversions. It looks at which queries, placements, audiences and times produced them, and buys more of that. Feed it spam and it does the same thing: identifies the traffic that produced the junk, and goes looking for more of it.
More of that traffic produces more junk. More junk is reported as more conversions. The account looks like it is improving while the phone stops ringing.
| Stage | What happens |
|---|---|
| 1 | A bot or a click farm fills your form |
| 2 | The submission is counted as a conversion |
| 3 | Smart Bidding treats that traffic as valuable |
| 4 | Spend shifts toward the sources producing it |
| 5 | More spam arrives, and the signal gets stronger |
The account metrics improve at every step. Conversion rate climbs. Cost per conversion falls. None of it is real.
The tell
A campaign showing an unusually strong conversion rate while the business reports that none of the leads are any good is the classic shape. One PPC manager running roofing and plumbing accounts described campaigns converting at 20 to 30 percent with clients saying not one lead was genuine, and found that enabling captcha protection did not stop them. Disabling Search Partners did.
That last detail matters, because it points at where a lot of this traffic comes from and at why a form-side fix alone is incomplete.
Fix the traffic first
Before touching your forms, there are ad-side settings that cause more of this than most accounts realise.
| Setting | What to check |
|---|---|
| Search Partners | Turn it off and compare lead quality. It is the single most common source of junk conversions on service accounts |
| Location targeting | Google’s default targets people in or interested in your locations, which includes anyone searching about your area from anywhere in the world. Switch to presence only |
| Display Network | Automatically included on some campaign types. Separate it or exclude it |
| Match types | Broad match with loose negatives buys traffic with no purchase intent |
| Negative keywords | “Free”, “jobs”, “salary”, “download”, “template” and similar filter out wrong-intent searches |
| Content exclusions | Parked domains and low-quality placements are worth excluding outright |
None of this is a Lead Source feature. It is the first thing to do and it is free.
Then stop feeding the loop
The traffic fixes reduce the volume. They do not solve the reporting problem, because whatever spam still arrives is still counted.
The approach PPC specialists advocate is to validate each lead before the conversion is reported, then send only the validated ones back to Google. Smart Bidding then optimises on real customers instead of form fills, and the account starts buying the traffic that produces revenue rather than the traffic that produces submissions.
Google’s own mechanism for this is enhanced conversions for leads, described in its documentation as an upgraded offline conversion import that uses user-provided data such as email addresses to supplement imported conversion data and improve bidding performance. Hashed customer data is matched back to the campaign against the same data collected on your lead form.
Two 2026 changes are worth knowing before you set this up, because plenty of guidance still online predates both. From April 2026, enhanced conversions for web and for leads became a single on/off setting, with user-provided data accepted from website tags, Data Manager and API connections, and from 15 June 2026, offline conversion imports and enhanced conversions for leads uploads moved to the Data Manager API and are blocked in the Google Ads API.
Google also recommends naming the conversion action for the real event, “lead qualified” or “contract signed” rather than “form submitted”, and using Qualified or Converted lead goals. That is the shape of the whole fix in one setting: the thing you report should be the thing you want more of.
That requires three things working together:
| Requirement | What it means |
|---|---|
| Detection | Something decides whether a submission is real, at submission |
| Attribution | The real leads carry the source, campaign and click that produced them |
| Feedback | Only the validated leads go back to the ad platform as conversions |
A captcha plugin gives you the first and nothing else. Analytics gives you a version of the second at session level, which is not granular enough to validate individual leads. The three are usually stitched together from different tools, badly.
Where Lead Source sits
Spam is quarantined at submission, so it never enters your lead counts or your attribution, which is what form spam protection covers in full. Every enquiry that passes carries its real source, campaign and page journey on the individual record, which is the layer the ad platform needs back. See how the attribution works, or how Google Ads attribution looks specifically. There is a shorter version for PPC attribution if that is the whole of your question.
The junk stops being a conversion signal, and what goes back to Google is a real lead. The distortion it was causing in your own reporting before any of it reached Google is covered in what spam leads do to your marketing numbers.