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
Find where a test lead stops.
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.
02
WHAT LEADUPTIME CHECKS
Specific, not vague.
WordPress and tracking answer different questions.
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.
The CRM check seeks an exact match.
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.
Agencies get a usable result.
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.
03
FAQ
Common questions
Is this the same as an HTTP uptime check?
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.
Does a passing WordPress response prove CRM or inbox delivery?
No. CRM arrival needs its own configured check. Recipient email inbox arrival is not currently verified.
What happens when the CRM provider is unavailable?
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