Website Lead Capture: Connect Your Form to a Next Step

A website form is only the beginning of lead capture. The useful outcome is an enquiry your team can understand and act on: contact details, the request, an owner, and enough source context to know where it came from.

Convertly native forms send website submissions into the CRM without exposing a tenant API key in your page. Think about the visitor experience and the sales handover together when setting one up.

Ask for what the first conversation needs

Choose fields that help your team begin a useful conversation. A contact method and a clear request may matter more than collecting every possible qualification detail at the first touch.

Decide which fields are required and what the visitor sees after submission. Use the form’s supported success message or redirect behavior to explain what happens next. Do not promise an immediate callback unless your team can actually provide one.

Configure consent text to match your organization’s approved process rather than copying unrelated wording into every form.

Decide where the enquiry should go

Supported lead defaults can fill missing values such as source, stage, category, and owner. They help make intake consistent, but incoming values can take priority where supported.

Choose who receives the form’s new-lead alerts. These recipients are separate from lead assignment: assigning an owner can create its own notification even when the person is not a form-alert recipient.

A useful test is to ask, “If this enquiry arrives while I am away, who knows it exists and who owns the response?” Notification and responsibility should have distinct answers when your process needs them.

Preserve the context available from the website

Generated embeds can pass available campaign and capture context, including supported click identifiers, UTM values, landing page, and referrer. What arrives depends on the page, tracking configuration, supplied data, and visitor consent.

Use the documented embed rather than assuming any custom form will send the same information. A source label such as “Website” is useful, but it is not a replacement for campaign-level context.

Test a real journey through the page

Use a controlled, privacy-safe test submission and inspect the resulting lead. Check:

1. Contact details and the visitor’s request.
2. Expected source and available campaign context.
3. Stage, categories, and ownership.
4. The intended recipients’ alerts.
5. The success message or destination shown to the visitor.

Test a repeat submission too. Depending on settings and matching information, Convertly can update an existing lead and retain duplicate-submission context instead of creating another copy. Your team should understand that result before judging lead counts.

Keep the first follow-up close to capture

Agree on a response routine, or use a tested event-driven automation to create the next task. A successful form submission is not the same as a completed sales response.

Native forms currently support inline embedded, single-step forms. They are not a hosted multi-step or conditional-logic form builder.

Start with creating and publishing a form, follow the embedding guide, and review submission results before relying on the form for a campaign.