File Hosting & Sharing

Lead Capture Form

Definition

A lead capture form turns a published address into a small exchange. Instead of the file, the first request returns a form — typically two or three fields, such as name, email and company — and the content appears once it is submitted. The submitted rows are stored against that file and listed in the owner's dashboard, usually with a timestamp, the referrer that sent the visitor and the country the request came from, and can be exported as CSV. It is a gate for attention, not a security control: nothing verifies the address typed in, and a determined visitor can often reach the underlying file once they have passed through. That is the honest distinction between this and a password-protected link, which withholds the content from anyone without the secret.

Why It Matters

Publishing a report tells you how many people opened it. Gating the same report tells you who they were. Four hundred views is a statistic; 145 named readers, with the referrers that sent them, is something a small team can act on this week. The cost is measured in the same currency, because every field added loses submissions — a two-field form routinely converts two or three times better than a six-field one asking for job title, company size and phone number. The judgement call is what deserves a gate at all: put one in front of a landing page or a getting-started guide and you have simply made the thing harder to use.

How It Works

The file is flagged as gated, so the edge answers the first request with the form page rather than the object. Submitting posts the fields to an endpoint that validates them, writes a row against the file, and issues a short-lived signed cookie recording that this session has passed. The content is then served normally, and every later request during that session — pages, images, the download itself — goes straight through without asking again. Because the cookie is the only thing standing in the way, this stops a casual visitor and not much more; pair it with a password-protected link or an expiring link when access genuinely has to be limited. Captured rows sit alongside the cookie-free view and download counts, so the owner can see both the total audience and the named part of it.

Real-World Example

A B2B software firm publishes a 3 MB benchmark report at harbourside-report.99helpers.site with a two-field form in front of it. Over six weeks 99helpers records 412 visits and 145 submissions — a 35 per cent completion rate — with LinkedIn and one newsletter accounting for most of the traffic. The team exports the rows to their CRM and drops the 'company size' field they had been considering, having watched a longer form on an earlier report convert at half the rate.

Common Mistakes

  • Asking for six fields when two would do — each extra question loses submissions, and job title rarely changes what anyone does with the lead
  • Treating the form as protection, when it only interrupts the first request and does not stop the file being passed on afterwards
  • Gating content that is meant to spread, such as documentation or a pricing sheet, which suppresses the sharing that made it worth publishing
  • Collecting rows into a dashboard nobody exports, so a fortnight of interest goes cold before anyone follows it up

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →