Overview
Input Validation allows creators to enforce custom rules on form fields to capture only the data that matters. From restricting email submissions to specific domains (e.g., only @brand.com) to validating phone formats or even password-protecting landing pages, you're now in full control of your data quality and audience access. These capabilities empower marketers to ensure cleaner inputs, protect gated content, and engage only high-intent users.
Key Benefits
Higher-quality leads: Filter submissions so you’re engaging the audiences that matter most to your campaign goals.
Protected, gated content: Limit access to exclusive pages, offers, or downloads to the right users only.
Accurate, consistent data: Enforce valid formats and eliminate typos or fake entries before they hit your CRM.
Compliance readiness: Apply rules like age checks (e.g., 21+) to meet legal or brand requirements.
How it Works (Step-by-step)
Add or select your form
In the flow editor, create a new form or select an existing form block (e.g., “Email,” “Phone,” or a numeric field for age).
Open Advanced configurations
In the form field settings, see Advanced Configurations and toggle Define valid input (or the equivalent Input Validation control).
Choose your rule(s)
Set the error message
Write a clear, friendly message that appears when inputs don’t meet your rule (e.g., “Please enter a valid work email” or “You must be 21+ to continue.”).
Preview and test
Use Preview to try valid and invalid inputs. Confirm the form blocks incorrect entries and displays your error message as expected.Publish and monitor
Publish your page. As submissions come in, review your downstream tools (CRM, email, analytics) to confirm cleaner data and improved lead intent.
Example use cases
Gated access for exclusive campaigns: Restrict submissions to approved domains for employee, partner, or VIP programs.
Compliance & age verification: Enforce age gates (e.g., 21+ for alcohol brands, 18+ for sweepstakes).
Data hygiene: Require valid formats to reduce bounces and bad records (proper emails/phone numbers).
Best practices
Be explicit in your UI copy: Tell users what qualifies (e.g., “Use your company email to access this offer”).
Keep error messages concise: State what’s wrong and how to fix it in one line.
Start simple, iterate: Launch with a single high-impact rule (like domain allowlist or age ≥ 21) and expand as needed.
Test edge cases: Try subdomains, uppercase/lowercase emails, and off-by-one values (e.g., age 20, 21, 22).
FAQs
Can I combine multiple rules? Yes—pair domain restrictions with format checks or age gates for tighter control.
Will this affect conversion? Validation may reduce volume but typically increases quality and downstream performance.
Where do I see errors? Errors display inline on the form; users must correct their input before submitting.




