Skip to content
Pathly
Sign inStart free
Docs / Lead path monitoring / Getting started
DISCOVER · RECORD · MONITOR

A clear path from
setup to evidence.

Learn how to find lead paths, configure safe checks and understand what happens when a journey fails.

Your first monitored lead path

  1. Create an account and add a website.

    Enter the public URL of the client website. Pathly scans it for forms, booking widgets and calls to action.

  2. Review the suggested checks.

    Choose the paths you want to monitor. Discovery does not turn on monitoring until you choose.

  3. Choose the device and schedule.

    Start in observe mode, select the check interval available on your plan, and run a check to review the result.

  4. Record a custom journey if needed.

    Open the Extension section in your account for recorder setup. Walk the flow in your browser and review the captured steps.

Observe and test modes

Start safely with observe mode

Observe mode checks whether the form and its controls are present and usable without submitting it. Use this for your first checks.

Test mode performs the configured submission with your test data. It requires domain ownership verification using a DNS TXT record or a meta tag. Coordinate test submissions with the website owner so they can recognize test leads.

Journey step primitives

A journey is an ordered sequence of browser actions and assertions. Recorded flows carry the target information needed to replay each interaction.

navigate

Open the specified page.

fill / select

Enter a value or choose an option.

click

Interact with a target element.

assert

Check a URL, text or element condition.

Example: inspect a contact form

This illustrative step sequence opens a page, checks that its form is visible, and checks that the submit control is usable. It does not submit the form.

Journey steps / JSON
[
  {
    "type": "navigate",
    "url": "https://example.com/contact"
  },
  {
    "type": "assert",
    "condition": "element_visible",
    "target": {
      "primary": "form"
    }
  },
  {
    "type": "assert",
    "condition": "element_clickable",
    "target": {
      "primary": "button[type=\"submit\"]"
    }
  }
]

Selector resilience

A target can contain a primary selector, alternative selectors and an element fingerprint. This gives the engine more context when markup changes.

01Primary selector

Locate the intended element directly.

02Alternative selectors

Try the recorded fallback targets.

03Element fingerprint

Use recorded element context to help resolve the target.

If a target cannot be resolved, review the failing step and update or re-record the journey.

Devices and schedules

Run checks with desktop, phone or tablet profiles. Mobile checks can reveal overlays and layout changes that leave desktop flows working. Each device check has its own results and alerts.

Available intervals depend on your plan, from daily on Free to every five minutes on Agency Pro. See the plan comparison for the current limits.

From failure to recovery

A single failed check begins a watch. Repeated consecutive failures confirm an incident—three by default, adjustable per check. The alert includes the failing step and screenshot evidence.

Open the run to inspect step timings, captured network failures and console errors. When the path recovers, Pathly sends a recovery notification.

Explore a sample journey →
Documentation · Pathly