Pathway Monitoring

A lead pathway is the specific route a real visitor takes to become an enquiry. On most service-business websites there are only a handful of them: the primary contact form, a quote form, a booking link, a click-to-call button, an email link, and the confirmation that follows a successful submission. When one of those quietly breaks, the site keeps loading, general analytics keeps counting sessions, and uptime monitors keep reporting the page as available. The pipeline slows before anyone notices.

Pathway Monitoring is designed for that exact failure mode. It discovers those pathways, gives each a stable identity, and continuously checks that the pathway is present, visible, reachable and verifiable.

What LeadGuard treats as a pathway

LeadGuard supports pathway types that reflect how real service-business websites actually convert:

• Submission forms: contact, quote, enquiry, consultation, subscription and support forms.
• Click-to-call and click-to-email links, including the mobile sticky variants.
• Booking and appointment pathways, both native pages and third-party embeds.
• Checkout actions on sites that accept small purchases as an initial engagement.
• CTA elements that lead to any of the above, including primary buttons on landing pages and repeated hero CTAs.

Each pathway is assigned a canonical identity so that a form which reappears after a temporary hiccup is treated as the same pathway rather than a new one. This is what makes issue history, recovery and monitoring confidence meaningful over time.

The six check families

Every scheduled scan of a protected pathway walks through six families of technical health. The families are ordered so an early failure short-circuits later checks that would produce meaningless noise.

Active checks combined with passive evidence

The check families above are active. They are performed by LeadGuard's own browser environment on a schedule appropriate for the account's plan. They do not submit real forms, dial real numbers, send real emails or complete real bookings on behalf of the customer's site.

Alongside the active checks, the LeadGuard site tag records passive events from real visitors: pathway views, pathway interactions, form starts and progress, and confirmed conversions. Passive evidence is used to confirm that a pathway which passes active checks is also being used successfully by real people, and to distinguish a genuinely broken pathway from one that is simply unused during a quiet period.

Issues, false-positive controls and recovery

When an active check fails, LeadGuard opens an issue against the pathway rather than firing an alert on the first anomaly. Issues carry a category (which family failed and how), evidence from the check run, and a state that changes as subsequent runs either confirm the failure or clear it.

False-positive controls include:

• Blocked or uncertain responses (network errors, bot walls, captcha screens) are treated conservatively and do not automatically escalate to a critical alert.
• A single failing run does not close a healthy pathway; recovery requires repeated successful checks and, where available, corroborating real-visitor evidence.
• Issue history is kept per canonical pathway so recurring failures on the same form are not counted as unrelated events.

Critical alerts

When a protected pathway is failing in a way that is likely to prevent enquiries, LeadGuard creates a critical alert. Delivery of that alert depends on the account's current plan and alert policy: not every warning generates an email, and some are surfaced only in the dashboard's Alerts view. This is documented on the pricing page and the Alerts view itself.

Recovery events are recorded on the same pathway, so the timeline shows both the failure and the transition back to a healthy state.

Monitoring confidence

Each protected pathway has a monitoring-confidence rating: Good, Fair, Limited or Pending. The rating reflects how much evidence LeadGuard currently has, combining active check coverage and passive real-visitor signals. It is deliberately banded rather than expressed as a false-precision percentage.

Safety boundaries

Pathway Monitoring is designed to be safe to run on a live customer website:

• Active checks run from LeadGuard's own environment and are rate-limited per site.
• No form field is filled with real customer data, and no submission is sent to the customer's endpoint.
• No call is placed to a tel: target and no message is sent to a mailto: target.
• Bookings and appointments are never created against third-party providers.
• The LeadGuard site tag captures event metadata for pathway activity; it does not capture the values typed into form fields.

Who Pathway Monitoring is for

Pathway Monitoring is designed for enquiry-driven websites: service businesses, agencies, professional-services firms and clinics. It is most valuable where a small number of pathways generate most of the leads and where any hour of pathway downtime is directly commercial.

What Pathway Monitoring is not

• It is not a substitute for general web analytics; it does not report traffic acquisition or page-level engagement.
• It is not a substitute for uptime monitoring across every URL on a site.
• It is not a lead capture system, a CRM or a revenue attribution product.
• It does not guarantee that every pathway on a site will be discovered, or that every possible failure will be detected.

How to start

The free protection check discovers the pathways on a submitted URL, applies the initial round of checks and shows the results in a shareable report. No card is required to protect the first pathway continuously.