32.1 Landing Page Forms and the Leads Workspace

Forms placed on an AIUNIFY Funnels Landing Page can collect visitor-submitted information and store the resulting submission as a Lead.

Each successful Landing Page form submission is associated with the Landing Page that received it.

32.2 The Form Submission Endpoint

The public form workflow sends a submission to the Landing Page form-submission operation using the Landing Page's unique code.

This lets AIUNIFY Funnels identify which Landing Page should own the submitted Lead information.

32.3 Submission Rate Limiting

The confirmed public form-submission route is protected by an application throttle of 60 requests per minute.

This is an application-level traffic control. It should not be treated as a substitute for thoughtful form design or other appropriate anti-abuse protections.

32.4 The Landing Page Must Be Found

When processing a form submission, AIUNIFY Funnels first searches for the Landing Page using the supplied Landing Page code.

If that Landing Page cannot be found, the submission workflow returns:

Not found page id

32.5 Form Fields Need Names

AIUNIFY Funnels collects submitted visitor fields by their form field names.

If the form does not submit usable named fields, the application can return:

Not found any fields submit. You need config name for fields in builder

When creating or editing a form in the Builder, make sure each field that should be captured has an appropriate field name.

32.6 Technical Request Fields Are Excluded

The submission workflow excludes several technical request values from the visitor information saved as Lead fields.

The confirmed excluded field names are:

1. _browser
2. _os
3. _lang
4. _timezone
5. _token

The remaining named fields are treated as submitted Lead information.

32.7 Email Field Normalization

AIUNIFY Funnels specifically recognizes these submitted email field names:

1. email
2. Email
3. EMAIL

These are normalized to the stored field key:

email

For the most predictable workflow, use email as the form field name.

32.8 At Least One Submitted Value Is Required

If the form sends field names but all collected field values are empty, AIUNIFY Funnels returns:

Not found any fields submit. Please enter some fields

Design forms so that the fields required for the campaign are clearly marked and validated appropriately for the visitor.

32.9 Duplicate Email Protection Is Per Landing Page

When a submitted form contains an email field, AIUNIFY Funnels checks existing Landing Page FormData for the same email address on that same Landing Page.

If that email has already been captured for the Landing Page, the form submission can return:

Your Email existed!

This duplicate check is tied to the specific source Landing Page rather than being described by the confirmed workflow as a global account-wide email prohibition.

32.10 What Is Stored for a Successful Lead

When the form contains usable submitted information, AIUNIFY Funnels creates a Lead/FormData record with the confirmed data structure below.

Name	The source Landing Page's name.
Type	landingpage
Source ID	The internal ID of the Landing Page that received the submission.
User ID	The user who owns the source Landing Page.
Field Values	The visitor-submitted named form fields and their values.
Browser	The detected browser family.
OS	The detected operating-system/platform family.
Device	The device classification returned by the application's tracking helper.

32.11 Browser, OS, and Device Are Detected by the Application

The form-submission controller invokes the application's browser-detection workflow when creating the Lead.

This is why the Leads workspace can display Browser, OS, and Device information separately from the form fields entered directly by the visitor.

32.12 Do Not Confuse Tracking Values with Form Fields

Browser, OS, and Device information are stored as Lead record attributes rather than as ordinary visitor-created form field keys.

For example, a visitor may submit fields such as:

1. Name.
2. Email.
3. Phone.
4. Company.

The Browser, OS, and Device values are then maintained separately by the application.

32.13 Autoresponder Processing Happens After Lead Creation

After a Lead record has been created, AIUNIFY Funnels checks whether the Landing Page's Autoresponder configuration qualifies for processing.

The Autoresponder requires the configured values to be present and a valid submitted email field.

When those conditions are satisfied, the application dispatches its Landing Page Autoresponder job.

32.14 Mailing Integration Processing Happens After Lead Creation

The application also checks whether a mailing integration is configured and whether the Lead contains a valid email address.

When the integration rules qualify, AIUNIFY Funnels dispatches its Landing Page integration job.

This is why the internal Lead record, Autoresponder, and mailing-platform contact are related but distinct parts of the submission workflow.

32.15 Successful Lead Capture Does Not Alone Prove an External Integration Worked

A Lead may be successfully stored inside AIUNIFY Funnels before the configured mailing-platform operation is processed.

When testing Mailchimp, Acellemail, or Mailwizz, verify both:

1. The Lead appears in AIUNIFY Funnels.
2. The contact appears in the intended external mailing list.

32.16 Form Next Action Is Returned Separately

After successful Lead creation and the applicable background-job checks, the submission response returns the Landing Page's configured:

1. type_form_submit
2. redirect_url

The public page uses this information for the visitor's configured post-submission journey.

32.17 Form Capture and Payment Capture Are Different Workflows

Normal Landing Page form submissions use the form-submission workflow documented here.

Payment components use the separate ecommerce order-submission workflow covered later in this manual.

Do not assume that testing one automatically validates the other.

32.18 Recommended Form Testing Workflow

1. Open the Landing Page Main Page in the Builder.
2. Confirm every required input has the correct field name.
3. Use email for the email field when email-based processing is required.
4. Save the Builder.
5. Confirm the Landing Page Settings for next action, Autoresponder, and mailing integration.
6. Open the actual published Landing Page.
7. Submit recognizable test information.
8. Confirm the expected post-submission action.
9. Open the Leads workspace and locate the test Lead.
10. Verify the submitted Lead Info.
11. Verify Browser, OS, and Device information.
12. Verify the Autoresponder when configured.
13. Verify the external mailing list when configured.

Operating principle: A reliable Landing Page form requires correctly named fields, meaningful submitted values, and end-to-end verification in both AIUNIFY Funnels and any connected email system.