Skip to main content
A broken CTA button or a failed form submission doesn’t announce itself — it just quietly stops converting prospects into leads. TYAN monitors your entire prospect journey around the clock so you catch broken steps before they drain your pipeline.

​
Map Your Prospect Journey

Before you build anything in TYAN, write out every step a prospect takes from first touch to captured lead. A typical journey looks like this:
  1. Landing page loads completely
  2. CTA button is visible and clickable
  3. Lead form or booking widget opens
  4. Form submits successfully
  5. Confirmation message is displayed to the prospect
  6. Follow-up email arrives in the test inbox
Each of these steps is a potential point of failure. Your goal is to assert that every one of them works, end to end, continuously.

​
Build the Journey in TYAN

1

Create a Flow for Each Stage

Break the journey into logical stages and build a separate flow for each one. For example:
  • Flow 1: Landing Page Loads — navigate to your landing page URL and assert that key elements (headline, CTA button) are visible.
  • Flow 2: Lead Form Submits — navigate to the form, fill test data, submit, and assert a 200 response and confirmation message.
  • Flow 3: Confirmation Email — assert that a follow-up email arrives in your test inbox within the expected time window.
Keeping flows modular makes it easier to pinpoint exactly which stage broke when an alert fires.
2

Chain Flows into a Journey

Once your individual stage flows are saved, open the Journeys tab and click New Journey. Add your flows in order from first touch to lead capture. TYAN will run them in sequence, passing context between steps so the full path is validated as one continuous run.
3

Set a Monitor Schedule

Open the Journey, click Add Monitor, and choose a run frequency. For critical prospect pipelines, set the schedule to every 15 minutes — a broken form that goes undetected for hours costs you real leads. Less time-sensitive journeys can run every 30 or 60 minutes.
4

Connect Slack or Email for Alerts

Go to Settings → Integrations and connect your Slack workspace or add alert email addresses. Assign the alert channel to your Journey monitor. When the monitor fails, you’ll receive an instant notification with a screenshot showing exactly where the journey broke — no log diving required.

​
What to Assert at Each Stage

Strong assertions are what separate a useful monitor from a false-confidence one. Add these assertions to the corresponding flows in your journey:
  • Landing page: “CTA button text is visible” and “Page title matches expected value”
  • Form interaction: “Form submission returns 200” and “No error message is displayed”
  • Confirmation screen: “Confirmation message contains ‘Thank you’” and “Next-step CTA is visible”
  • Follow-up email: “Email subject contains expected text” and “Email arrives within 5 minutes”
The more specific your assertions, the faster you’ll identify exactly what broke and where.

​
Alerting and Failure Details

When a monitor run fails, TYAN sends an alert that includes:
  • The name of the Journey and the specific flow that failed
  • The step number where execution stopped
  • A screenshot captured at the moment of failure
  • A link to the full run log in your dashboard
This means your on-call engineer gets actionable context immediately, not just a generic “something broke” notification.
If your lead form relies on a third-party service — such as HubSpot, Calendly, or a payment processor — make sure your flow includes the steps that interact with that service. Downstream failures in third-party embeds are among the most common silent pipeline killers, and they won’t surface unless your journey tests them explicitly.

Monitors Concept

Understand how monitors work, how run history is stored, and how to manage monitor schedules.

Slack Integration

Connect TYAN to Slack to receive real-time failure alerts in the channels your team already monitors.