The browser performs the journey.
A configured check opens a public HTTPS page, interacts with the form and sends a marked test submission once. An ambiguous submission is reported without automatically sending another copy.
SYNTHETIC LEAD MONITORING
A page can load while a lead path fails later. LeadUptime submits one marked synthetic enquiry and reports the evidence from the browser, WordPress, tracking and connected CRM as separate stages.
Updated

WHAT LEADUPTIME CHECKS
A configured check opens a public HTTPS page, interacts with the form and sends a marked test submission once. An ambiguous submission is reported without automatically sending another copy.
The companion plugin links processing to that exact test. LeadUptime separately observes configured GA4, Google Ads or Meta Pixel browser events. A tracking event does not prove ad-platform attribution.
Where an integration is configured, bounded polling looks for the synthetic contact by deterministic identity or marker. HubSpot, Pipedrive, GoHighLevel and Salesforce adapters exist; external qualification is still pending.
The run can pass, fail, degrade, remain inconclusive or report a configuration error. An unavailable CRM is inconclusive, not proof of a lost lead. The portfolio view groups affected websites and incidents.
SETUP
Start with a repeatable form interaction. Add tracking or CRM verification only when the expected signal, access and scope are agreed for that journey.
Agree the public form, required fields and a recognizable synthetic identity. Keep the test destination controlled. A deterministic marker helps distinguish this check from an unrelated submission or contact.
Review the public interaction, visible result and matching site acknowledgement first. A broken field mapping or unavailable form must be resolved before interpreting a later integration stage.
For tracking, specify the expected browser-observable event. For a configured CRM check, agree the exact synthetic identity to find and required provider access. An observed event is separate from advertising attribution, and a CRM lookup is separate from email receipt.
Read each stage rather than assuming that every incomplete result means a real lead was lost. Provider unavailability can leave a CRM outcome inconclusive. Review the run, integration state and qualification before deciding how to respond.
READING A RESULT
| Stage | Expected evidence | When evidence is missing |
|---|---|---|
| Browser submission | One marked test is submitted through the public form. | Investigate the interaction and required fields. |
| WordPress confirmation | The site acknowledges the matching test. | Check the connection and form configuration. |
| Configured tracking | The expected browser signal is observed. | Investigate that signal independently of submission. |
| Configured CRM | The intended synthetic contact is matched. | Check provider availability; an unverified result remains inconclusive. |
FAQ
No. An HTTP check establishes whether a configured response is available. A synthetic journey uses a browser to test form interaction and its configured downstream evidence.
No. CRM arrival needs its own configured check. Recipient email inbox arrival is not currently verified.
LeadUptime reports the CRM stage as inconclusive. It does not turn a provider outage into a claim that a real customer lead was lost.
PRIVATE PILOT
