Landing page forms: what to fix before asking for more budget

Before you ask for more budget to generate leads, review your landing page form and the first screen of the page. Too many fields, questions in the wrong order, validation that lets bad data through and a fragile CRM integration make a company pay for clicks that never become contacts. Fixing that usually pays off more than buying more traffic, especially in complex sales, where the form has to qualify people without scaring them off.

Fewer visits, more contacts: the Orbenk case

On Orbenk's website, the form review came with more contacts, even with fewer people visiting. Between late April and June 2026, we made four changes to the site:

• we replaced the form with Salesforce Web-to-Lead, which sends the contact straight to the CRM;
• we added the blog to the menu;
• we added input masks and validation to the fields;
• we set which fields are required.

Form submissions recorded in GA4 went from an average of 60 a month, January to April, to 102 a month, May to July. Over the same period, average unique users dropped from about 12,500 to 9,900 a month.

There is no way to separate the effect of each change, and swapping the form calls for care in the comparison, because the number is the site's submission event. The final check happens in the CRM, as we show further down. The full story is in the Orbenk case study.

The fields on a landing page form

Ask only for what sales uses to take the next step, in an order people can answer without thinking. Three decisions cover most of it:

1. How many. For educational content, name, email and one qualifying question are usually enough. For a proposal request, questions about company size, role and need make sense, because whoever gets there already wants to talk.
2. Order. Start with the easy ones (name, email) and leave the qualifying question for last. People who have already filled in half the form tend to finish.
3. Field type. Prefer dropdowns to free text for role, company size and industry. A closed answer becomes a CRM filter and a scoring rule in lead scoring in RD Station.

Input masks, validation and a direct CRM integration

A contact with half a phone number or a mistyped email costs the same click and never turns into a conversation. An input mask shows the expected format while people type, and validation blocks impossible data from being submitted. Make a field required only where sales truly needs that information.

The path from each landing page form to the CRM deserves the same attention, and that is where many teams lose contacts without noticing. Every step in between (a spreadsheet, an email, a rushed integration) is a point where a lead can disappear, as we explain in our post on lead leakage. Salesforce Web-to-Lead, for example, generates an HTML form that creates the lead directly in the CRM and comes with reCAPTCHA to keep bots out.

The first screen in 3 seconds

Before anyone sees the form, the first screen has to answer three questions in seconds: what pain it solves, what the person gets and why act now. If the headline needs careful reading to make sense, the form never gets seen.

In a campaign we ran with Franq, the subheadline on the first screen was rewritten to pass this test. The final version opens with the reader's pain, says in one sentence what the content shows and closes with a reason to download now. The form next to it had three fields, one of them for qualification.

To test your own page, show the first screen to someone outside the project for three seconds and ask what it offers. If their answer does not match yours, the problem starts before the form. This is the kind of fix that goes into landing page review sprints.

Multi-step forms

When qualification takes many questions, split the form into two screens. Contact details on the first, qualifying questions on the second. People who have started tend to finish, and you still capture the contact of anyone who drops off halfway, if your tool saves the first step.

The same logic applies to forms inside ad platforms, such as LinkedIn Lead Gen Forms, which arrive pre-filled with profile data.

How to measure: site event vs CRM lead

The submission event shows that someone clicked the button, and the CRM lead shows that the contact arrived intact. GA4 records submissions with the form_submit event from enhanced measurement, but it does not know whether the data was valid or whether the CRM received it. Compare the two every month:

• if the site records more submissions than the CRM receives, the integration is leaking;
• if the CRM receives more, contacts are coming in another way or the event is undercounting;
• if the two match and quality drops, the problem is the offer or the qualifying fields.

This cross-check is part of what we do when we take care of a client's landing pages: page, form, integration and measurement reviewed together.

Talk to usWant help planning this at your company?Tell us what you need. We'll reply by email or WhatsApp and, if it makes sense, put together a quote.Contact us

Frequently asked questions

How many fields should a landing page form have?

The ones sales uses to take the next step. Educational content needs few fields; a proposal request can carry qualifying questions.

Does a required phone field scare leads away?

At the top of the funnel, it asks for a commitment people are not ready to make yet. Make it required where a call is the agreed next step, such as a demo request.

Is it worth connecting the form straight to the CRM?

Yes, because every step in between is a point of loss. Once it is connected, compare site submissions with CRM leads every month.