Transaction monitoring that catches a broken checkout.
A broken checkout costs you orders by the minute. Uptimia clicks through your login and checkout flows like a real customer, around the clock — and the moment a step breaks, you know which one, with a screenshot.
Response time by step
avg run 6.39 s · last 24 hStep breakdown
All 7 steps passedFailed at step 46.39 s · 14:229.52 s · 14:32AveragesLast runA dead Pay button, caught
A real checkout failure at 14:32 — detection, screenshot, fix, recovery.
Flows you can monitor
Each journey runs in a real Chrome browser on a schedule, one step after another. Any step that fails opens an incident and names itself.
Build the journey in your browser
Click together the steps a real user takes — go to a page, click a button, type into a field, check the result. A live screenshot updates as you build.
- Start from a template — Login, Sign-up, Search or Checkout skeletons, or a blank flow
- 18 building blocks — go somewhere, do something, check the result. Chain as many as your flow needs
- Test all steps live — a failing step turns red and jumps the preview to its screenshot
No Playwright or Selenium scripts
Synthetic checks usually live in a script that someone re-fixes every time the interface moves. Here the builder is the script.
A script your team maintains
Someone opens the repo, tracks down the selector that changed, and ships the test again — work that produced a green build and no monitoring.
Steps you click together
Every step targets its element by CSS selector, so a moved button is one field to edit — and "Test all steps" proves the fix against a live browser before you save.
How Uptimia runs your flows
The failing step, with a screenshot
When a flow fails, you get the run laid out step by step, the failing one in red, and a screenshot of exactly what the browser saw — evidence, not guesswork.
- A screenshot per step — open the exact frame the failing step captured
- Failed step in red, and every step after it clearly marked "not run"
- See where the time went — each step's bar starts where the one before it ended
The slow step, not the slow page
"Checkout feels sluggish" is a hunch. Uptimia ranks every step by how long it takes — so you can see it's the payment call dragging, and fix the right thing.
- Every step ranked by average duration — with its share of the total run
- The 5 slowest steps charted over time, each with its own trend line
- Slowest runs shown beside the average — what a bad day looks like, not just the typical one
Status, run time and slowest step
Three questions answered without clicking anything: is it working right now, how reliable has it been this month, and which step is dragging it down.
- Status, availability and incidents up top — the health of the flow in one line
- Average and slowest run times and the step count for the whole journey
- Slowest step called out by number and action, next to how often it's run
Alerts that name the failing step
The alert lands where your team already looks, and it says which step broke and why — not just "something is down". Once the next run completes all steps, a recovery notice follows on the same channels.
- The same contacts and channels as every other Uptimia monitor — set once
- The failing step in the message — which one, and why
- Recovery notice when the next run passes all steps
The next broken step should page you.Not a customer.
Every flow, every screenshot, every alert channel — free for 30 days, and none of it is a paid add-on.
Built in three steps
No code and nothing to install — the checks run from Uptimia's browsers, not your servers.
Build your flow
Start from a Login, Sign-up, Search or Checkout template, then click together the steps — navigate, click, type, verify.
Test it, then save
"Test all steps" runs the whole flow live against a real browser. A failing step turns red and shows you its screenshot — fix it before you save.
Get alerted when a step breaks
Uptimia re-runs the flow on schedule. Any failed step opens one incident and alerts your team — with a screenshot of the exact step.
Every deploy gets a smoke test
The flow you built re-runs from a real browser every 10 minutes — a continuous smoke test against production. A release, a config change or a third-party script that breaks checkout is caught by the next run.
Runs after every release
Nobody has to remember to click through the checkout after a deploy. The next scheduled run walks it end to end and names the step that broke.
A canary for production
The run hits your live site from Uptimia's browsers, so what it reports is what a customer would have hit. Point a second monitor at a canary release to watch that the same way.
Catches third-party breakage
A payment widget or tag script that stops loading fails the step that depends on it — even when nothing in your own code changed.
Nothing to run in CI
No agent, no runner, no pipeline job to keep alive. The checks come from Uptimia's browsers, so each run exercises DNS, TLS, your CDN and your app the way a visitor does.
Also included
Click, fill and verify — no code
Go to a URL, click, fill in fields and passwords, tick checkboxes, pick from dropdowns, submit forms — then check the URL, status code, elements and text that came back.
Assertions
Verify the result of a step, not just that a page loaded.
Templates to start from
Login, Sign-up, Search and Checkout skeletons pre-fill the steps.
Public status pages
Show customers your key flows are working — and speak up when they're not.
Maintenance windows
Deploys and planned work never page anyone.
One dashboard for everything
Transaction monitors sit beside uptime, SSL, speed, DNS and heartbeat checks — one login, one contact list, one plan.
Where your alerts land
One contact list across every monitor you create — set the channels once, every flow uses them.
Microsoft Teams12 channels, one contact list — set it once, every monitor type uses it.
Browse the full integrations directory →What is transaction monitoring?
Transaction monitoring is an automated service that runs through a multi-step user journey — like logging in, searching or checking out — from a real web browser on a schedule, and alerts you when any step fails. It is also called synthetic monitoring, or synthetic transaction monitoring (STM) — synthetic because Uptimia drives the journey itself in a real Google Chrome browser instead of waiting for a visitor to find the broken step. It confirms the whole flow actually completes — not just that a page loads, as a simple uptime check would.
How does transaction monitoring work?
Each run executes your ordered steps one after another, recording how long every step took and a screenshot along the way.
Capture, then alert
step 5 · check text "Order confirmed" · not found → incident opens, alerts go out
Uptime check vs. transaction check
A page can load fine while the flow on it is broken. An uptime check sees the page load and calls it healthy; a transaction check clicks through the journey and catches what a loading page hides.
Compare uptime & transaction monitoring →| What happens | Uptime check | Transaction check |
|---|---|---|
| Home page loads fine | ✓ Up | ✓ Up |
| Login button throws a JavaScript error | ✓ Looks up | ✗ Caught |
| "Add to cart" element is missing | ✓ Looks up | ✗ Caught |
| Payment fails after the click | ✓ Page loads | ✗ Caught |
| Search returns zero results | ✓ Looks up | ✗ Caught |
Synthetic vs. real user monitoring
Synthetic monitoring drives the journey itself on a schedule, so a broken checkout is caught at 04:00 when nobody is shopping. Real user monitoring measures the pages your visitors actually loaded. Most teams run both.
See real user monitoring →| What you get | Synthetic monitoring | Real user monitoring |
|---|---|---|
| Who triggers the check | Uptimia, on your schedule | Your visitors, as they browse |
| Works when nobody is on the site | ✓ Yes | Nothing to measure |
| Names the step that broke | ✓ With a screenshot | Only once a visitor hits it |
| Load times by country, browser and OS | Step durations from one location | ✓ From real sessions |
Transaction monitoring FAQ
01What is transaction monitoring?+
02What is synthetic monitoring?+
03How is it different from uptime monitoring?+
04How is synthetic monitoring different from real user monitoring?+
05Do I need to write code or install anything?+
06Do I need to write Playwright or Selenium scripts?+
07Can I use it as a continuous smoke test?+
08How often does it check my flows?+
09Where do the checks run from?+
10Can it monitor flows that require a login?+
11What happens when a step fails?+
12How many steps can a transaction have?+
13Which alert channels are supported?+
14Is transaction monitoring on the free plan?+
Know the moment your checkout breaks.
Build your checkout or login journey in minutes — and be the first to know the next time a step breaks.