GuideForms
Login GuideForms PRO

Lead Form Step

The Lead Form step captures visitor contact information before showing results. It’s ideal for qualifying leads, gating results behind a signup, or collecting data for follow-up. The Lead Form step is a Pro feature, and only one lead form is allowed per guide.

When to use a lead form

Add a Lead Form step when you want to collect contact details alongside the visitor’s guide selections. Common scenarios: generating qualified leads for a sales team, building a segmented email list based on answers, or gating premium recommendations behind a signup. Place the lead form as the last step — right before results — so visitors have already invested time in the guide and are more likely to complete it.

Default fields

Every new Lead Form step starts with two system fields that cannot be deleted:

  • Name — A text field for the visitor’s full name. Required by default.
  • Email — An email field with built-in validation. Required by default.

These two fields are marked as system fields in the editor (they have no delete button). You can reorder them and change their labels, but you can’t remove them.

Name field split

A toggle checkbox lets you split the single Name field into First Name and Last Name — two separate half-width fields side by side. Enable this when your CRM or email tool expects separate first/last name fields. Toggling it off merges them back into a single full-width Name field.

Adding fields

A toolbar at the top of the editor shows buttons for each available field type. Click one to add it to the form:

  • Text — A single-line text input for short answers (company name, job title, etc.).
  • Email — An email input with format validation.
  • Textarea — A multi-line text area (4 rows) for longer responses.
  • Radio — A vertical group of radio buttons for single-choice questions. You define the options (label + value) in the editor.
  • Checkbox — A group of checkboxes for multi-choice questions. You define the options the same way as radio buttons.
  • Privacy — A consent checkbox for privacy policy agreement. Required by default.

New fields are appended to the bottom of the form. You can drag them to any position using the drag handle.

Field settings

Click any field in the list to expand its settings. The available options depend on the field type:

All fields (except Privacy)

  • Label — The text shown above the field (e.g. “Your Email”, “Company”).
  • Width — How much horizontal space the field takes, from 20% to 100% in steps of 5. Set two fields to 50% each to place them side by side on the same row. Defaults to 100% (full width).
  • Required — Whether the field must be filled in. If enabled, validation blocks navigation until the visitor provides a value.

Text, Email, and Textarea

  • Placeholder — Ghost text shown inside the empty field as a hint (e.g. “john@example.com”).

Radio and Checkbox

  • Options — A list of choices, each with a label (what the visitor sees) and a value (what gets stored). Click the add button to add more options. Each option has a delete button.

Privacy

  • Consent text — The text next to the checkbox, for example “I agree to the privacy policy”. Defaults to this phrase.
  • Privacy policy URL — An optional link. If provided, the consent text becomes a clickable link that opens in a new tab. Leave it empty to show plain text.

Privacy fields are always full width and don’t have a separate width or placeholder setting.

Reordering fields

Every field — including system fields — can be dragged to a new position using the drag handle icon. The order in the editor matches the order on the frontend. Fields with a width less than 100% will flow side by side if there’s room, wrapping to a new row when the total exceeds 100%.

How the form looks on the frontend

The form renders in a centered container (max width 400 px) with a flexible layout. Fields wrap automatically based on their width — two 50% fields sit side by side, a 100% field takes a full row. There’s a 12 px gap between fields.

There is no separate submit button inside the form. The guide’s main Continue navigation button handles submission. When a visitor clicks Continue, the form validates all required fields. If anything is missing or invalid, error messages appear below the relevant fields and navigation is blocked until the issues are fixed.

Validation rules

  • Required fields — Must have a non-empty value.
  • Email fields — Must match a standard email format.
  • Checkbox groups — If required, at least one option must be checked.
  • Privacy checkbox — If required, must be checked.

Where lead data is stored

When the visitor submits the form and moves to results, the lead data is sent to the GuideForms REST API and stored in the WordPress database as part of the visitor’s session record. The data is associated with the guide ID and session ID, and includes all form field values along with the visitor’s guide selections.

You can view submitted leads in the GuideForms analytics area. If you have CRM integrations enabled (HubSpot, Mailchimp, FluentCRM, or a webhook), the lead data is forwarded automatically after submission. See Integrations Overview for details.

Anti-spam protection

The form includes a hidden honeypot field that is invisible to real visitors but gets filled in by bots. A timestamp is also sent with each submission. These measures help filter out automated spam without requiring a CAPTCHA.

Tips

  • Place the form last. Visitors are more likely to fill out a form after they’ve already invested time answering guide questions. Put the lead form as the final step before results.
  • Keep it short. Name and email are often enough. Every additional field reduces completion rates. Only add fields you’ll actually use.
  • Always include a privacy checkbox. If you’re collecting personal data, a consent checkbox helps with GDPR compliance and builds trust.
  • Use the width setting. Put First Name and Last Name at 50% each, or Company and Job Title side by side, to keep the form compact without sacrificing information.
  • Mark the step as skippable if results should still be visible. If the form is optional (a nice-to-have rather than a gate), enable the “Allow skipping” option so visitors can jump straight to results.

Next steps

  • Cards Step — Visual selection cards for categorical choices.
  • Slider Step — Numeric range selection for prices, distances, and more.
  • Integrations Overview — Send lead data to HubSpot, Mailchimp, FluentCRM, or webhooks.