Monitoring
Scheduled checks, the confirm re-run, alerts and the public changelog.
A monitor re-reads a URL on a schedule and tells you when its design really changes.
Add a monitor
- Open Monitors, or the Monitoring tab of a project.
- Enter the URL, pick a project and a cadence: daily, every 3 days or weekly. Your plan sets the shortest interval.
- Save. The first check sets the baseline.
How alerts stay quiet
- Differences below a visibility threshold are ignored.
- When something looks different, the worker reads the page again. The change is stored and alerted only if the second read agrees. The confirm re-run is free.
- An unchanged page stores nothing.
- After three failed checks in a row, the monitor shows “Can’t reach” and you get one email. After 14 days of failure it pauses.
Credits
Each check costs 1 credit. If credits run out, monitors pause and you get one email. They resume when credits return on the 1st (UTC). See billing and credits.
Public changelog
A project can publish its confirmed changes as a public page with an RSS feed, for clients or your own team. Each entry links to the compare view.
Slack and GitHub
Send alerts to Slack and gate pull requests with Preview Gate from the integrations page. The Gate is covered in GitHub Action.