What is an alert?
When PingChange detects a meaningful change compared to your last snapshot, it can open an alert and send it through each channel linked to that monitor. A typical alert includes:
- Which monitor changed and the URL
- A short summary of what changed (and on many paid plans, a more readable AI-assisted line)
- A link to open the full comparison in the dashboard
- Sometimes a screenshot attachment when one was captured for that change
Exact layout depends on the channel (Slack card vs email vs Telegram message).
Where to read alerts and history
- Dashboard → Alerts — Cross-workspace list of recent notifications and states you can work through.
- Monitor detail — Change history (or equivalent) lists every diff for that URL so you can compare versions and share links with stakeholders.
Use history when you need an audit trail (“show me what the pricing page looked like last Tuesday”).
Reducing noise
If you get too many alerts:
- Narrow the page — In monitor settings or the preview flow, focus on a region that excludes rotating banners or footers.
- Tighten the AI prompt — On paid plans, say what counts as important and what to ignore (timestamps, blog sidebars, etc.). See AI-assisted monitoring.
- Slow the schedule — High-frequency checks on noisy pages multiply trivial diffs; sometimes daily is enough.
- Split monitors — One URL with two very different intents (pricing vs blog) may deserve two monitors with different prompts or regions.
Avoid pausing a monitor forever if the real fix is a better target or prompt.