Capability

Confirm the lead actually arrived, not just that the form said thanks.

Most "form monitoring" stops at the submit button. Formitor follows each tagged test lead all the way to a real inbox and verifies the notification email was delivered, so a silent mail failure can't quietly cost your client every enquiry.


The gap nobody watches

"Submitted" is not the same as "delivered."

A form can accept an entry, store it, and show a cheerful confirmation while the notification email never leaves the building. SMTP timed out, the relay changed, the mailbox bounced. The visitor saw success. Your client saw nothing.

Formitor closes that gap on every run: it submits, then watches for the tagged notification to genuinely arrive, and treats the inbox, not the thank-you page, as the source of truth.

One submission · what actually happened
09:14:02 Tagged test lead submitted
09:14:02 Entry stored in WordPress
09:14:03 "Thank you" shown to the visitor
09:14:33 Notification email deliveredSMTP silently rejected the message. Nothing on the page said so.
09:15:01 Formitor confirmed the failure & alerted you

Escalating depth

Three verification tiers, one per level of doubt.

Every form gets the delivery check. When something looks off, Formitor escalates automatically to deeper, browser-level verification.

Delivery check

A tagged test lead goes through the form and Formitor waits for the notification to land in a real, monitored inbox over real SMTP. The default check on every run.

Render check

A headless browser loads the page and confirms the form actually renders: fields present, submit button visible, no JavaScript error eating the markup.

Deep check

A real browser fills the form field by field and submits it like a visitor would. If anything fails, you get a screenshot of exactly what the visitor saw.


What this catches

The silent failures that don't show up anywhere else.

None of these break the page. The form keeps saying "thanks", which is exactly why they go unnoticed until a client asks where their leads went.

  • An SMTP credential or relay change. A rotated password or swapped provider that quietly stops mail from going out.
  • An SMTP-plugin update that breaks sending. A "routine" update that resets config or throws on send, with no visible error on the front end.
  • The notification address on a block or spam list. Mail accepted by your server but refused or dropped at the destination.
  • A full or bouncing mailbox. The recipient inbox is over quota or the address no longer exists, so nothing lands.
  • A DNS or MX change. A migration or registrar edit that points mail at the wrong place and silently swallows it.

Delivery-verified vs the alternatives

Not all "form monitoring" watches the same thing.

Uptime tools tell you the page loaded. Submission checks tell you the form accepted the entry. Neither follows the lead to the inbox, exactly where it goes missing.

Checks Formitor Uptime / ping · Form-success only
Confirms the email was delivered Yes No
Catches silent SMTP drops Yes No
Screenshot of what the visitor saw on failure Yes No
Tells you which form & which site Yes Varies
Multi-site view across clients Yes Varies

"Form submission-success" tools sit one step short of the inbox. They confirm the entry was accepted, then stop right where leads actually disappear.

Put a delivery check on every client's lead form.

Install the spoke, set a cadence, and let Formitor confirm each lead lands, not just that the form said thanks.