Skip to main content
On paid traffic, a share of every form fill is worthless: bots, typo’d numbers, throwaway inboxes. Qualification tells you whether a real lead was a good lead. Validation stops the fake ones getting through at all. The controls live in the funnel’s settings under Validation, and they’re independent, so you can run one, all, or none.

​
The four controls, cheapest friction first

The first three are silent: the visitor sees nothing unless what they typed fails, in which case they get a quiet inline note under the field rather than a banner.
Every validation path fails open. A missing vendor key, an outage, or an exhausted credit balance lets the lead through unvalidated rather than blocking it. Validation can cost you accuracy; it will never cost you a lead.

​
2FA phone verification

Enabled per variant, so it’s A/B testable like anything else: run one arm with verification and one without, and read the difference in qualified rate against the drop in raw submissions.
  • 1 credit per successful verification. Every workspace gets 100 free, then prepaid packs at 10 cents each from Settings → Billing.
  • Out of credits means verification fails open, and the leads keep flowing unverified.
  • The sender name in the text is derived from your funnel’s domain and brand on first enable.
  • Skipped on test-drive links, so test it with a real visit.
Your agent toggles it with set_sms_verification, which returns the credit balance so it can warn you when the pool is low.
Variant table showing a 70/30 traffic split and per-variant SMS 2FA toggles

The variant table carries the SMS 2FA toggle next to the traffic split

​
Work emails only

Set per variant too, and bulk-settable for the whole funnel. Worth turning on for B2B offers where a personal address usually means an unqualified lead, and worth leaving off for consumer offers where it just costs you conversions.

​
TrustedForm certification

For funnels selling leads onward, TrustedForm (ActiveProspect) certification can be switched on per funnel. granvl injects the official snippet, which records the capture session and drops the certificate URL into the form as a hidden field. It fans out to your destinations like any other field, and the buyer claims the certificate on their own ActiveProspect account.

​
Where this sits in the pipeline

Validation and qualification answer different questions and stack cleanly. Validation asks is this real. Qualification asks is this worth your time. Only qualification data feeds CPQL; validation just stops the noise before it counts.
Zero-PII holds throughout. Checks run at submit time against the value in the browser or a bounded server-side call; granvl records whether the check passed, never the phone number or the address. See How zero-PII works.