A signup form is a negotiation. The reader has a problem; you have a resource that might help. Every field you add is another reason to close the tab, and most of the fields are for your convenience, not theirs.
The two-field version is not a trick to collect less data. It is a decision to collect only what you will use before the first follow-up.
Which fields earn their place
Email is the delivery address. It is not optional.
The second field should qualify the reader in a way that changes what you send next. Good options:
- "What are you trying to fix?" — a short select: deliverability, conversions, list growth, something else.
- "Where do you send from?" — a domain or platform, if the resource is specific to it.
- "How big is your list?" — ranges, not an exact number, if the advice genuinely differs by size.
Bad options: phone number, company size, job title, "how did you hear about us", and a password. If the first email does not need it, the form does not need it yet.
Name is a borderline case. It personalises the email and makes the record human, but it is also a field people pause over. If you use it, make it optional and do not block the download on it.
The consent line is not a third field
The checkbox is a separate legal act, not another data field. It should be:
- unticked by default;
- specific about what will be sent and how often;
- separate from the download itself;
- recorded with the exact wording, the date, the source and the version.
"I agree to the privacy policy" is not consent to marketing. "Download the checklist" is not consent either. The reader can receive the file without joining a list; if you want to send more, ask for that separately.
For a B2B audience, the wording can say "occasional emails about deliverability" rather than "newsletter", because the first is what you will actually send. Specificity improves both trust and the quality of the consent record.
The page itself
A form with two fields still fails if the page is ambiguous.
- One promise in the headline. The same words as the ad, the link or the email that brought the reader.
- One proof element. A short example of the resource, a line about who made it, or a specific outcome. Not a carousel.
- One action. The button says what happens: "Send the checklist", not "Submit".
- The delivery expectation. "It arrives in a minute; check spam if it does not." This prevents the second email being "did you get it?".
Do not put a video above the form. Do not make the reader scroll to find the button. Do not use a pop-up on top of the landing page.