Frequently Asked Questions

Questions about how Lead QA works, what it checks, and how it handles data.

Does Lead QA submit forms to check them?

By default, no. Lead QA fills fields with test data and checks the submit button state without clicking submit. This is called a "dry-run" check. For agencies who need full end-to-end verification, an authorized submit test can be enabled per monitor — but only with your explicit permission.

What form providers does Lead QA support?

Lead QA detects forms from: plain HTML, Contact Form 7, WPForms, Gravity Forms, Elementor, Webflow, HubSpot, Typeform, and JotForm. More providers can be added on request.

How quickly will I be alerted when something breaks?

When a check fails, Lead QA retries after 2 minutes, then again after 5 minutes. If the failure is confirmed, an alert is sent. On the Agency plan (every 6h checks), you can expect an alert within 7 hours of a failure occurring.

Does Lead QA work with password-protected pages?

Not currently. Lead QA monitors public-facing URLs. Password-protected staging environments are not supported in the current version.

What's the difference between Lead QA and uptime monitoring?

Uptime monitoring tells you if the server responds with an HTTP 200. Lead QA checks if the lead path actually works — form visible, CTA clickable, tracking pixels present, submit button enabled. A site can be 'up' while the form is completely broken.

Does Lead QA store visitor data or form submissions?

No. Lead QA never stores form submission content, real lead data, cookies, session tokens, or visitor data. Checks use synthetic test data only.

Can I use Lead QA for client reporting?

Yes. The Agency and Pro plans include monthly reports that you can share with clients as part of a care plan or retainer. The report shows monitor status, incident history, and check counts.

Is there a free plan?

Yes. The Free plan includes 1 monitored URL with daily checks and all 5 check types. No credit card required.