Forms

How Lead360 helps

Lead360 Forms collects structured information into the correct sub-account and can connect submissions with contacts and follow-up workflows. Field controls, validation, consent language, publication, and submission records help teams replace unstructured intake with reviewable data.

When to use this area

Use Forms when a visitor or staff member should submit a defined set of information that Lead360 can store and route.

Before you begin

• Collect only fields required for the stated purpose.
• Map each value to the correct standard or custom field.
• Add necessary consent, privacy, confirmation, spam, and notification settings.

Configure fields and mapping

1. Choose standard contact fields or the exact custom fields required for the conversion goal.
2. Set each label, placeholder, option list, width, required state, hidden state, and custom-field mapping deliberately.
3. Use a query-string key only for an approved prefill and verify that hidden values cannot be manipulated into unsafe data.

Configure conversion and redirect

1. Add clear consent and privacy wording appropriate to the channel and data collected.
2. Choose the standard or custom Meta event only when required, include value and currency where applicable, and avoid firing the same conversion twice.
3. Enter the full post-submit redirect URL. In a Funnel step, choose Use the form or survey redirect when this form should own the destination.

Install and test

1. Use the direct link for a hosted form or the embed code for an approved website.
2. Test desktop and mobile validation, required fields, duplicate contact behavior, field mappings, tracking, successful submission, error handling, and the final redirect with a controlled record.

Use Ask360 here

Ask360 can explain every builder control and prepare one reviewed form create or update when supported. It waits for Accept and never publishes a funnel, messages a contact, invents a field, or exposes submitted customer data.

Confirm the result

A completed Forms workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.

• Submit valid, invalid, duplicate, and mobile test cases.
• Confirm the contact and submission records contain the expected values.
• Check confirmation, notification, automation, and attribution behavior.

Troubleshooting

A field value is missing from the contact

Review field mapping, field type, validation, conditional visibility, and whether an existing contact update rule rejected the value.

Spam submissions increase

Review verification, rate limiting, hidden-field traps, source traffic, and publication placement without blocking legitimate accessibility tools.