Forms and Lead Capture

Form definitions, spam protection, embed code, and — in some products — email notification of new submissions.

Some form builders are tied to your website CMS or a specific ad-platform integration. The Forge accepts submissions from any of them so intake stops depending on someone reading an inbox.

• Form-submission events with field values
• Form and page identifiers for attribution
• Source, campaign, and referrer metadata
• File attachments and consent flags

• Confirmation communications from an operational context
• Assignment of the intake to the correct owner
• Duplicate flags back to the form provider where supported

• New form submission
• Form submission classified as duplicate
• Form submission converted to a deal or appointment

• Copying form submissions into a CRM or scheduler by hand
• Emailing team members when a form arrives
• Attributing form submissions to the right campaign manually

• Office administrator
• Sales and marketing leader
• Operations manager

• Submission volume by form and campaign
• First-response time to inbound submissions
• Conversion rate from submission to opportunity

• Signed webhooks are required where the provider supports them.
• Duplicate-event protection guards against retried deliveries.

• Not every provider supports webhooks — some require polled exports.
• File-attachment size limits vary.

The Forge can absorb standalone form builders once the operating record is stable, keeping only the ones tied to a website CMS the customer already runs.