# Build and Test a Lead Form

Create a form, choose fields and consent, place it on a site, test validation and completion, and verify the lead destination.

Reviewed 2026-09-02

## Define the form outcome

Open **Marketing**, then **Lead Builder**. Confirm the site, audience, intended lead destination, owner, and follow-up before adding fields.

Collect only what the current purpose requires. Use synthetic information for every test.

## Build the steps and fields

Create or open the form, then add the needed steps, fields, choices, and explanatory content. Use clear labels, mark only truly required fields as required, and review conditional behavior in every path.

Add the approved consent language and make the action clear before submission. Do not place internal instructions or private record details in public form copy.

## Configure completion and destination

Set the completion message or destination, lead owner, status, notifications, and any visible form settings. Save, reopen, and confirm the full step order.

Place the form through **Website Builder** when it belongs on a page. Verify that the page uses the intended form rather than a similarly named draft.

## Test the public form

Open the private test site. Complete every major path with synthetic information. Check required-field messages, conditional steps, consent, mobile layout, back and next behavior, final submission, and confirmation.

Then open **Leads** and confirm the test lead's site, form, time, source, answers, owner, and CRM relationship. A public confirmation and a saved lead are separate results; verify both.

## Configure incomplete-form recovery

Open **Recovery** and confirm which forms and partials are eligible, the timing, exclusions, and stop conditions. Keep recovery paused while testing.

Activate only after a synthetic partial reaches the expected state. Verify queued, sent, completed, skipped, and stopped states separately. Honor consent and opt-out status before any message.

## Stop conditions

Stop if the destination, owner, required consent, notification audience, public page, or recovery eligibility is uncertain.