Content teams can gate a PDF without HubSpot on day one. The form captures who asked, then send the link from email so the file is not a public Direct-S3 URL in the HTML source.
Notify marketing ops.
Or use one Form ID per PDF.
The button submits; it does not serve the file.
Manually at first, then Zapier plus a signed URL.
A download request form is a gate in front of a file: white paper, rate card, CAD pack, or investor deck. US demand-gen teams call it a content form; UK B2B marketers do the same with slightly more ICO anxiety. The signup pack fits because you want email, company, and what they care about.
It is not a store checkout. If the file is a purchased asset, use an order flow. This page is for permissioned marketing files you are willing to email after a human or an automation checks the address.
Every extra field increases [email protected]. Ask for what sales will actually use.
Do not put the PDF URL in the page HTML. Email it, or use a signed link that expires.
HubSpot, Marketo, and a naked PDF link are the three poles. HTML plus email is the middle.
Works on static sites. You control the file host.
Use when scoring and nurture exist. This form is the bootstrap.
Best for SEO. Use when you do not need the lead.
Correct for customer-only docs. Wrong for a first white paper.
A /resources page on Webflow can host one form per asset or one form with an interest select.
UK GDPR: say why you want the email and how long you keep it. US: be ready for state privacy opt-outs if you sell the list—which you should not do silently.
Not built into A form on your site. That needs a thank-you page you control plus a non-public URL.
Use the interest select or separate pages for reporting cleanliness.
Often yes for the PDF itself. Gate the file, keep an ungated summary indexed.
Yes. Accept it or add a friction question in the message field.
Capture repro steps, severity, and environment from users on your site.
Let customers pitch product ideas with context, not a one-line tweet.
A lighter intake than a feature request for culture, process, or UX niggles.