[HTMLPub] Collecting Form Submissions – Leadpages Knowledge Base

Overview

HTMLPub automatically detects HTML <form> elements in your published pages and collects submissions without any extra configuration. Every page that contains a form appears in the Forms section of the dashboard.

The Forms Dashboard

Go to Forms in the left sidebar to see all pages where a form was detected. The table shows:

Page — The page that contains the form.
Tags — Any tags you have applied to the page.
Submissions — Total number of form submissions received.
Last Submission — When the most recent submission arrived.
Collection — Whether form collection is Enabled or Disabled for that page.

How Form Detection Works

When you publish or update a page, HTMLPub scans the HTML for <form> tags. If any are found, the page is added to the Forms dashboard automatically. You do not need to add any scripts or modify your HTML — it just works.

For submissions to be captured, your form's action should point to HTMLPub's submission endpoint: /api/forms/submit. If your form uses a third-party action URL (e.g. a Mailchimp or Typeform endpoint), HTMLPub will not intercept those — they go directly to the third-party service.

How Field Names Are Determined

When HTMLPub captures a form submission, each input is assigned a field key — the name that appears as a column in your CSV export and in any integration field mappings. HTMLPub resolves each field's key using the following order of priority:

name attribute — <input name="email"> uses email.
id attribute — <input id="email-field"> uses email-field.
data-field or data-name attribute — <input data-field="subscriber_email"> uses subscriber_email.
Semantic input type — If none of the above are present, an <input type="email"> is keyed as email, type="tel" as phone, and type="url" as url. This ensures email fields are always recognized even when the page's HTML omits explicit name attributes.
Sibling label — If the input is immediately preceded by a <label> element (e.g. <label>Your name</label><input ...>), the label text is slugified and used as the key (e.g. your_name).
Placeholder text — For non-semantic types (e.g. type="text") without any of the above, the placeholder is slugified (e.g. placeholder Company Name becomes company_name).
aria-label attribute — Used as a fallback when no other identifier is available.
Type and index fallback — If nothing else is found, HTMLPub falls back to a generated key like text_0 or email_1.

For the most predictable field names — especially when setting up integrations — add a name attribute to each input in your HTML.

Viewing Submissions

Click on any page name in the Forms list to open its submission detail view. You will see:

Date — When the submission was received.
Form — The identifier of the specific form on the page (useful if a page has multiple forms).
Data Preview — A truncated preview of the first few fields (e.g. email, name).

Click the expand arrow on any row to see the full submission data as key-value pairs.

Exporting Submissions

From the submission detail view, click Export CSV to download all submissions for that page as a CSV file. The file includes a column for each unique field name found across all submissions, making it easy to open in a spreadsheet.

Deleting Submissions

Click the trash icon on any submission row to delete it. The exact effect depends on the type of row:

Form submission rows — The submission record is permanently deleted. This action cannot be undone.
Identified visitor rows (shown with a sparkle icon and labeled Identified visitor in the Form column) — Deleting one of these rows performs a full data erasure for that visitor's cookie identity. This removes the visitor profile, all associated page-view and click analytics events, and severs the cookie link on any related form submissions (the submission data itself is retained because it was legitimately captured, but it is no longer tied to that visitor's identity). All four operations complete together — if any step fails, none of the data is changed.

Note: Deletion of identified visitor rows is permanent and cannot be undone. It is designed to satisfy data-erasure requests (e.g. GDPR right-to-erasure or CCPA deletion requests) from individual visitors.

Rate Limits

To prevent abuse, HTMLPub limits form submissions to 10 per IP address per minute. Submissions that exceed this limit receive a 429 Too Many Requests response.

Next Steps

To automatically forward form submissions to tools like HubSpot, Mailchimp, Google Sheets, or Slack, see Connecting Integrations.

Need more help?

You can always get in touch with our support team—just click Support in your Leadpages navigation menu, or submit a ticket ↗