Scan Findings
A finding is a single detected script, cookie, or network request from a scan. Each finding needs to be reviewed and assigned to a vendor in your policy.
Finding types
| Type | Description |
|---|---|
script | External JavaScript file loaded on the page |
cookie | Cookie set during page load |
iframe | Third-party embed detected |
beacon | Tracking pixel or network request to a third-party domain |
Finding statuses
| Status | Meaning | Action needed |
|---|---|---|
| Matched | Linked to a vendor in your library | Review assignment |
| Unmatched | No vendor match found | Assign to vendor or create custom vendor |
| Ignored | Manually marked as not relevant | None |
| New | Appeared in a recent scan, not seen before | Review urgently |
Reviewing findings
Property → Scanner → Findings
Filter by: status, type, vendor, scan date.
For each unmatched finding:
- Click the finding to see details (script URL, cookie name, domain)
- Search for a matching vendor in the library
- Assign or create a custom vendor
- The finding is now tracked under that vendor
"New" findings
A finding is marked New if it was detected in the most recent scan but not in the previous scan. This typically means a new third-party script was added to your site. Review new findings promptly — they may represent scripts loading without proper consent.
ConsentForge can send email alerts when new findings are detected. Configure in Scanner → Settings → Alerts.
Ignoring findings
If a finding is a known false positive (e.g. a first-party script or an internal analytics tool that doesn't need consent), you can ignore it:
Finding → Mark as Ignored
Ignored findings are excluded from future scan comparisons.
Finding details
Click any finding to see:
- Full URL or cookie name
- Domain it originates from
- Whether it was detected before or after consent simulation
- Which scans detected it
- Assigned vendor (if any)