Mystra Revenue-Path Monitoring Setup (Client Onboarding)

Mystra Revenue-Path Monitoring Setup (Client Onboarding)

1. 01

   Create the Mystra account and verify the client's domain

   Add the DNS TXT record Mystra issues so the monitoring service is bound to the client's web app domain. This needs DNS access, so request it from the client's IT contact before the kickoff call rather than during it.

2. 02

   Add the client app URL and wire the deploy webhook

   Register the app inside Mystra, then connect the deploy webhook so runs fire after each release. For Vercel or Next.js pipelines the hook drops into the existing build step; confirm one run appears in the dashboard before moving on.

3. 03

   Configure the Mystra-provided inbox for email and magic-link capture

   Point the signup flow at the inbox Mystra supplies so the tool can receive the welcome email and follow magic links. If the client sends from a custom domain, add that sender to the allowlist or the email step will read as broken when it is not.

4. 04

   Map the three revenue paths: signup, email delivery, checkout

   Walk each flow once in Mystra and confirm the throwaway-account signup, the welcome email arrival, and the Stripe Checkout reach without payment. Verify the paid area stays locked for the unpaid account, since that lock check is what separates a real pass from a false one.

5. 05

   Confirm evidence capture on every step

   Check that screenshots, video, HAR file, and console log are recorded for each run. The Free plan holds 7-day run history and 1 GB of evidence, so on a Starter account at $29/month with 3 apps and 500 runs you have 2 GB to work with before old runs roll off.

6. 06

   Set alert routing to Slack, email, and webhook

   Mystra alerts only when it has proof of breakage: a 5xx error, timeout, missing email, or locked paywall. Route those alerts into the client's Slack channel and your own delivery inbox so the agency sees the failure at the same time the client does.

7. 07

   Write the runbook and hand off to the delivery pod

   Document how to read an alert, which evidence file to open first, and the escalation path for a revenue-blocking failure. This is the artifact the retainer is billed against, so keep it in the client workspace, not a personal drive.