Fake form submissions are form entries with made-up or invalid details. Google splits the cause in two: bots reaching your form, and “real users submit fake contact details or other invalid information” (Google Ads Help).
Tell the cause
| sign | likely |
|---|---|
| hundreds of entries in minutes, same fields, nonsense names | bot script |
| plausible name, dead email or phone | real person, junk details |
| entries only from one ad campaign or keyword | ad traffic problem: fake clicks on ads |
Check how much of your traffic is bots first: anti-bot detector.
Controls
From Google’s lead-quality advice: protect forms with reCAPTCHA and server-side validation, and consider a double opt-in, where the user clicks a link in a verification email to confirm a real person owns a valid address.
From Stripe’s card-testing guide, which fights the same kind of script (Stripe):
- Validate the CAPTCHA on the server, on every request that matters.
- Limit access: login or session checks before the form.
- Rate limits, for example a cap on entries per IP per day.
- Watch for unusual behavior and filter on user agents or other parameters.
- Use a mix. Stripe: filters on one signal such as IP are usually not enough alone.
Judge leads by outcome
Google tells advertisers to pick lead goals like “qualified lead”, “converted lead” or “book appointment”, not raw form fills, and to connect first-party data.
Get credit for ad leads
Prepare a spreadsheet: GCLID per lead and your verdict on each (what happened when you emailed or called). File it with the Click Quality Form. Steps: fake clicks on ads.