Forms & leads
Validation and spam protection
Validate inputs, configure origins, and handle suspected spam safely.
AT A GLANCE
Drag to explore · use +/− to zoomOnly safe leads reach destinations
Validation and spam classification happen before delivery decisions.
- 1Apply configured validation and abuse checks.
- 2Route clean, accepted leads.
- 3Hold suspected submissions for review.
- 4Reject invalid high-confidence failures.
Form quality controls
- Configure required fields, type and length restrictions, and deduplication where appropriate.
- Set allowed origins for public browser integrations.
- Enable Turnstile with the correct site key and private verification secret when browser protection is needed.
Understand suspicious submissions
CLEAN leads follow normal delivery rules. SUSPECTED leads are stored for review while outbound work is held. Invalid high-confidence verification proof is rejected.
Inspect the spam reason before releasing a suspected lead. Some upstream verification outages preserve the lead as suspected rather than silently dropping it.
Didn't find the answer? Contact support. For endpoint descriptions, see the API reference.
