Solutions

Fewer alerts. Each one worth opening.

Tracefox tests your checkout on a schedule and watches your tracking scripts, cookies and consent banners. Its alerts are built to avoid noise: failures are confirmed before you hear about them, repeats are capped, and minor site changes wait for the digest.

Tracefox is not an infrastructure monitoring tool. It doesn't ingest logs, metrics or traces.

How Tracefox keeps alerts quiet

Three rules decide when you hear from Tracefox.

Confirmed before alerting

When a scheduled checkout test fails, Tracefox re-runs it once. You're only alerted if the re-run fails too, so a one-off network blip doesn't page anyone. The confirming re-run doesn't use a run from your monthly allowance.

One alert per problem

While a test keeps failing, it sends at most one failure alert per hour. When it passes again, you get a recovery email, so you know the problem is over without checking.

Severity for site changes

Script, cookie and consent banner changes are graded HIGH, MEDIUM or LOW. HIGH changes, such as a tracking pixel disappearing, alert when the scan finds them. The rest roll into a digest.

Alerts you can act on

Each checkout alert says what broke, so the first minutes go into fixing it rather than finding it.

  • The step that failed and its error message
  • A screenshot of the page at that step
  • A link to the run, with its video
  • Email on every plan, Slack on Pro and Business, webhooks on Business

Hear about the breaks that matter

Start with one free checkout test, no credit card. Paid plans add scheduled runs and include a 7-day trial.

Start free