Starting a scan
Open the Detected Cookies tab
Navigate to Cookie Banner → Detected Cookies for the site you want to audit.
Click Run New Scan
The scanner queues immediately. Your site URL and page limit come from the site’s scan settings.
Scan lifecycle
| Status | Meaning |
|---|---|
pending | Queued, waiting for a scanner worker |
running | Headless browser is crawling your pages |
completed | Results are available in the dashboard |
failed | The scan could not complete — the error reason is shown on the scan record |
Typical scans finish in under two minutes for a 10-page crawl. Larger page limits and slow origin servers extend this proportionally.
Last-scan summary
A summary card above the results shows at a glance:- Pages crawled — how many same-origin pages were visited (up to the configured limit).
- Engine — “Headless browser scan” for full browser scans, “Basic scan” for HTML-only scans (see Scanner Overview).
- Completion time — when the scan finished.
Reviewing detected cookies
The results table lists every detected cookie and storage item with:- Name, provider, and domain
- First-party or third-party (eTLD+1 based)
- Storage type (cookie, localStorage, sessionStorage)
- Humanized expiry (“Session”, “30 days”, “2 years”)
- Suggested consent category from the tracker database
Re-categorizing a cookie
To move a cookie to a different consent purpose:- Click the cookie row.
- Select the correct category from the dropdown (for example, move a misclassified cookie from Statistics to Marketing).
- Save. The change applies to the banner, preference center, and cookie declaration.