Skip to Content
Lead FormsConsent & Validation

Consent & Validation

Lead forms should be easy for visitors to complete and safe to publish.

This page explains the main validation rules to keep in mind.

Required fields

You can mark fields as Required.

ResultFly treats field types differently on purpose:

  • required text-like fields are validated on submit
  • required checkboxes must be checked before submit can continue

This makes checkbox-based confirmations, such as consent, more explicit.

Consent is a special kind of checkbox used for legal or policy confirmation.

A proper consent field usually includes:

  • required enabled
  • a clear consent sentence
  • a privacy policy link

Example:

  • I agree to the privacy policy

Use the dedicated Consent field tile whenever possible instead of building this manually from a plain checkbox.

Publish checks

Before publishing, ResultFly may block a campaign if a lead form is missing required compliance pieces.

Typical example:

  • a form is missing a required consent checkbox with a privacy policy link

These checks help catch problems before the campaign goes live.

Input validation

Fields with semantic meaning, such as email or phone, can validate the entered format.

For example:

  • an email field should contain a valid email address
  • a phone field should contain a phone number

This helps prevent broken or unusable submissions.

After submit

After a successful final submit:

  • the submit button can show a loading state while processing
  • the form can show a success state such as Thank you!
  • if a transition is connected, the user can be moved to the next page automatically

Best practice checklist

Before publishing a lead form, confirm:

  • the important fields are marked correctly
  • field behavior toggles are logical (Required, Hidden, Readonly) — if a field is Required and also Hidden or Readonly, it must be pre-filled (e.g., via query parameters), otherwise the visitor cannot complete the form
  • email and phone fields use the right field type
  • consent is present when required
  • the privacy policy link is correct
  • the final step uses Final Submit
WebhooksOverview