An uptime check gets HTTP 200 from a storefront whose checkout button does nothing. A
PylonMon customer journey opens a real browser every few minutes and does what a customer does: signs in,
adds to cart, checks out — and pages you the moment a step stops working, with the step that failed and a
screenshot of what the browser saw.
click Sign in fill Email = probe@example.com fill Password = hunter2 click Continue expect Welcome back click Add to cart click Checkout expect Order summary
No selectors to maintain unless you want them. Steps find things by the text a person sees — the button label,
the field's placeholder — and expect waits for the words that prove the step worked. Eight lines
cover most checkouts; css:#id is there for the awkward ones.
A broken checkout for three hours costs more than a year of this. Journeys are included on every plan — one on Free, five on Pro ($9), twenty on Team ($30), a hundred on Enterprise — next to uptime, server and cron monitoring, alerting and on-call, at flat prices that never count seats.
The browser runs from our infrastructure, identifies itself as PylonMon in its User-Agent so you can exclude it from analytics, and only ever does what your script says. Use a test account and a test payment method where money moves.
How it works, step by step: the docs. Watching sign-in rather than checkout? Login monitoring.