Synthetic checks are thorough, but they test the path Formitor knows about. What about the failure mode nobody predicted? The ad campaign that got paused, the redirect that quietly dropped the form page out of Google, the third-party script that hides the form from half of all visitors?
None of those break the form. The checks keep passing. The leads just stop.
How it works
Formitor learns each form’s normal lead volume: what a typical day and week look like for that specific form. When actual volume falls off that baseline, you get a warning that enquiries have dried up, even though every technical check is green.
It’s the monitoring equivalent of a shopkeeper noticing the bell over the door hasn’t rung all morning. Nothing is visibly broken. But the silence itself is the signal.
Privacy: counting without reading
The obvious question: doesn’t learning lead volume mean reading leads? No. Formitor counts submission events; it never stores your lead data. The content of real enquiries stays on your client’s site where it belongs. Volume is a number, and a number is all the anomaly detection needs.
Paired with the integration heartbeat
The same release family added the integration heartbeat: for forms wired to a CRM or automation, Formitor watches that real leads keep reaching the integration and warns you if they stop. Between the two, both ends of the pipe are covered: leads arriving at all, and leads arriving where they’re supposed to end up.
Synthetic checks catch what broke. Anomaly alerts catch what nobody thought to check.