LensShift form monitoring

WPForms monitoring for WordPress agencies

Monitor configured WPForms enquiry forms with browser submission checks, matching monitoring email verification, incident history and client reporting.

Check the form your client actually uses

LensShift opens the public page in a real browser, fills the configured controls with synthetic values, and checks the submission result. The companion WordPress plugin adds a monitoring copy and a reference for an authorized test. LensShift then looks for the matching incoming email.

This gives your agency separate evidence for submission and monitoring email receipt. An online homepage alone cannot tell you whether an enquiry form still works.

Designed for repeatable agency checks

  • Choose a specific discovered WPForms form.
  • Set field values and the expected success message.
  • Run an on-demand check before scheduling.
  • Review confirmed incidents and subsequent recovery.
  • Include observed outcomes in client reports.

Connect WPForms to LensShift

  1. Prepare a safe test. Confirm you manage the website and agree on labelled test enquiries with the client. Check whether submissions create CRM records, email sequences or other side effects.
  2. Install and pair the companion plugin. Add the website in LensShift, download the plugin from the setup guide, then save the matching Site ID, monitoring address and shared secret in WordPress.
  3. Enable the intended form. Authorize the WPForms form in the companion plugin and refresh the connection in LensShift. Discovery identifies a form; it is not proof that every field or add-on is compatible.
  4. Configure one monitor. Use the real public page URL, map synthetic values to the discovered fields, and set the current success message.
  5. Verify before scheduling. Run a check now. Review the browser outcome, matching monitoring email and normal recipient inbox, then choose a schedule appropriate for the client.

Keep WPForms notifications enabled

In the WPForms builder, review Settings → Notifications. Confirm notifications are enabled, the relevant notification is active, and its recipient and message are correct. Notification settings and form confirmation settings serve different purposes: a visible confirmation does not establish inbox receipt.

Reference: WPForms notification setup documentation.

Which WPForms forms should I start with?

Start with a standard single-page enquiry form and supported controls. CAPTCHA, payments, file uploads, conditional fields and multi-step flows may be excluded or need separately validated integration. Do not remove visitor-facing protection merely to make an automated test pass.

Form versions, themes, extensions and mail providers can change behavior. Run a new on-demand check after a relevant change. If LensShift reports an unsupported control or cannot produce a reliable result, review the form manually rather than treating that as a confirmed customer-facing failure.

What a pass means: the configured browser submission succeeded and a matching email reached LensShift’s monitoring mailbox. It does not prove delivery to your client’s normal inbox, cover every visitor journey, or guarantee continuous uptime.

Choose capacity for your portfolio

Start with one website and one monitor in the free trial. Paid plans include 3, 10 or 20 websites, with the same number of included monitors. Compare plans and additional monitor pricing.