Native Forms Overview

Convertly native forms collect lead information on your website and send it to the CRM without exposing a tenant API key.

What a form controls

A form defines:

Visitor-facing fields and validation
Success message or redirect behavior
Styling and consent text
Whether the form is active
Lead defaults such as source, stage, categories, owner, value, and custom fields
Selected users who receive new-lead alerts from that form
Tracking and embed settings

Submission behavior

A valid public submission is processed by Convertly’s protected form intake route. Depending on form settings, it creates a CRM lead or updates an existing matching lead.

Duplicate matching by email or phone does not create unlimited copies. Convertly appends duplicate-submission context to the existing lead and returns that lead as the result.

Lead defaults and alerts

Lead defaults fill supported fields that are missing from the visitor submission. Disabling lead defaults does not disable the form’s new-lead alert recipients.

Assignment alerts are separate: when a form assigns an owner, that owner can receive the normal lead-assignment notification even when they are not selected as a form-alert recipient.

Campaign context

Generated embeds can forward available click IDs, UTM parameters, ad context, landing page, referrer, and consent markers. Capture depends on the page, URL, configured tracking, and visitor consent.

Current scope

Convertly supports inline embedded, single-step forms. Hosted public form pages, multi-step flows, and conditional-logic builders are not currently available.