Judge how much to trust a finding
In the Check log, a change carries a badge: high confidence, medium confidence, low confidence or suspected decoy. Hover it to see why — which service fetched the page, whether that service counts as datacenter or human-like, and whether a second check agreed:
Agreement between two checks raises confidence; it doesn’t prove a change is real. Treat a high-confidence finding as trustworthy, not certain.
Which pages count as high-stakes, and which services count as human-like, is set in Connect web scrapers.
Resolve a finding held for review
A low-confidence change on a high-stakes page, such as pricing, waits for you instead of flowing into automatic re-evaluation or the comparison. On most pages you still get an Inbox notification marked suspected decoy — needs review; a held pricing change sends none. Find the change in the Check log: open the run’s details, and on the change choose:- Confirm — it’s a real change. Processing carries on, including automatic re-evaluation if you have it on.
- Dismiss — discard it. It’s never used as a baseline or acted on.
Tell Vector a finding was wrong
Open a finding from your Inbox. Under Your feedback, pick a verdict:- ✗ False positive — nothing really changed on the site.
- ✓ Correct — the change is real.
- ~ Noise — real, but not worth flagging.
Fix the mistakes that keep coming back
On the Proposals tab of Monitoring, click ✦ Generate proposals. Vector reads the false positives you’ve marked and suggests changes to how detection works — the recurring mistakes, stated as something you can act on. Nothing is applied on its own. Accept a proposal or Reject it, with an optional reason. Accepting also adds a regression test, so the same false positive can’t quietly come back.Where to go next
Read check results
Where findings arrive.
Connect web scrapers
Setting how strictly pages are checked.