The dashboard says everything is fine. Sales says the leads are trash. One of them is lying.

Completion rate is submit events divided by views. That is the entire definition. It has no access to who submitted and no access to what happened next. Definitionally, a bot fill and a $50,000 deal are the same row in the same table.

This is not a bug in anyone’s implementation. The metric is doing exactly what it says on the tin. The problem is that it is also the number the category reports, optimizes, and — this is the part that stings — meters you by.

One practitioner drew the distinction better than any vendor has:

Five events. Your form builder can see the first three and stops. The two that decide whether the month was any good happen somewhere it has never looked.

Four numbers. These are the only ones I am going to use, and each one is a published third-party figure from 2025 or 2026, not a measurement of your account and not a measurement of mine.

57.5%

of HTML requests are automated, not human.

40%

of internet traffic was bad bots in 2025, up from 37%.

30%

of purchased leads are outright fake.

13%

of MQLs ever become a real opportunity.

This is the angriest thing in the research, and the resolution is uniform: none of it works any more. Not according to me — according to the people running it.

One of them ended it the only way left: “We ended up taking down the page after 600 submissions.”

Now notice what every item on that list has in common. CAPTCHA, honeypots, hidden fields, geo-blocking at Cloudflare, paid anti-spam APIs — they are all attempts to block bad submissions at the door. Not one of them tells you what the submissions you accepted turned out to be. You can win the entire defensive war and still have no way to answer which of your forms made money.

An incomplete report tells you less than you wanted to know. This one tells you something false and pleasant. Cost per lead is down. Conversions are up. The line on the chart goes the right way.

And the structural version of the same thing, which is the best sentence anyone in this research wrote:

The tool is not neutral about that gap. It is congratulating you for the exact thing that is hurting you. That is the enemy in this essay — not a competitor, a convention. Every product in the category made the same design decision, and it was a reasonable one at the time.

Once your conversion action is form submitted, every junk fill becomes a training example. You are paying an optimization engine to go and find more of the traffic that just wasted your sales team’s morning. The dishonest number does not sit still. It compounds, and it compounds on your card.

Every response cap in this category meters the one thing nobody can control: how many things submitted the form. A customer put it more sharply than I would have.

Spam times response caps means you pay per response for traffic that will never buy anything, and then you pay again in sales time. That formulation is a customer’s, not mine, and it is the sharpest statement of the problem I have found anywhere.

These come from practitioners, and I think all three are partly right. Weakening them here would only mean losing to them later.

1. “If unqualified people are booking, the form isn’t what’s broken. The page is.”

They are right, and it should be the first thing you do. A price on the page costs nothing, it works, and it filters better than four more required fields. I am not going to argue that a form can fix a page that never said who it was for.

Three things it doesn’t do.

It doesn’t work on bots. A price range disqualifies a human who reads it. Bots don’t read, and about 57.5% of the requests hitting the page are automated. Nobody who took a page down after 600 submissions was going to be saved by a price range.

It is one act of judgment with no feedback. You put the price on the page. Then what? You have a hypothesis and no instrument — and next month’s vibe check on the sales calls is not an instrument.

It doesn’t scale across accounts. An agency running 20 clients can’t hand-tune 20 pages on intuition every month. It can instrument all 20 and let the outcome data say which ones need the intervention.

So I am not competing with the page fix. I am how you find out the page fix worked.

2. “Every form element is a barrier to submission.”

I agree with all of it, and it isn’t an objection to this — it’s an objection to a product I am deliberately not building. “Add three more fields to filter people out” is a pitch I will never make.

Here is the substantive part. This objection and the category’s default behaviour are both unevidenced, and they point in opposite directions. Completion-rate optimization pushes you to strip fields. The lead-quality instinct pushes you to add them. Nobody in the research had data on which was right for their own account; the researcher flagged the multi-step-versus-single-step question as an open contradiction with no clean recent test behind it. The category’s central design belief is a guess.

Outcome-weighted measurement is agnostic about the direction. If the shorter form produces more closed deals — and it very often will, because Mike is right — the outcome data says so and tells you to cut fields. This objection is an argument for an instrument, made by someone who doesn’t have one.

3. “Offline conversion import already does this.”

Fully conceded. The ad-platform loop is solved, commoditized, and posted on r/PPC as assumed knowledge in a one-line reply. Anyone claiming to have invented it should be ignored, and that is exactly why this product does not lead with closing the loop to your ad platform.

The residual is small and exact: that loop teaches Google, and it teaches your form nothing. The variant, the question and the field are untouched by it. So if you already run offline conversion import — good, you’re ahead of most — here is the question it can’t answer: which of your form variants produced those closed deals?

I am a form builder in a category drowning in form builders, writing about how the category is dishonest. That deserves some symmetry, so here are the three things most likely to sink this, written down before launch rather than after.

Provenance may not beat a CAPTCHA in practice. The mechanism cleanly identifies a cooperating agent: software that calls the form’s tool surface announces itself by doing so. It does not obviously catch a residential-IP bot filling in the human page while mimicking mouse movement. If our stamp turns out to be no better than reCAPTCHA plus a honeypot against sales-verified junk, the headline collapses — because then ours can’t tell either. We say unverified, not bot, for exactly this reason. It is a suspicion, not a verdict.

Outcome data may be too thin to test on. Closed deals are a much rarer event than form fills, and split testing on a rare event needs volume most accounts don’t have.

He’s right, and the honest answer is that at low volume the useful product is a ledger, not a test. Seeing that 200 fills produced 3 deals from one source and 0 from another is useful at any n. Declaring a winner from n=12 is the same lying dashboard in a different font, so we won’t.

People may not file this under “form”. The tracking complaints in the research all land one layer up — GA4, GTM, the pixel, the CAPI event — not on the form tool. The pain is real. Whether anyone currently locates it in the form is an open question, and if the answer is no, then this essay is the education bill and I am paying it.

Every quote here is verbatim from a public thread, with the handle and the month attached. I have not paraphrased anyone into agreeing with me, and where a quote cuts against the argument it is in the section where it cuts.

Two widely-repeated figures about a competitor’s pricing are missing on purpose. I could not reconcile either against that company’s live pricing page, so they are not in here — which is a shame, because both would have helped. If a number in this essay is wrong, tell me and I’ll correct it in public. The whole argument is that reporting should be honest even when it’s unflattering; it would be strange to exempt my own.

One more, for completeness: the agent half of this rests on WebMCP, which Google announced at I/O 2026 with an early preview in Chrome Canary in February 2026. Real agent traffic on your forms today is probably close to zero. The provenance argument has to stand on the bot half alone, and it does.