Reading the scan report
Open a domain and select Cookie scan. The latest scan is shown in full; earlier ones are under History, each marked manual, automatic or “new cookies seen on visitors”. While a scan runs, the page updates by itself.
Summary
Section titled “Summary”| Figure | Meaning |
|---|---|
| Pages | Pages visited, out of your plan’s limit. |
| Cookies | Cookies and storage entries found. |
| Before consent | Non-necessary cookies set before the visitor agreed. Should be 0. |
| Unclassified | Not yet in the cookie database; our team will sort them. |
| “3 new, 1 removed since the previous scan” | Compared with the previous successful scan. |
The cookie list
Section titled “The cookie list”Cookies are grouped by category. For each: its name, provider, expiry, the page it was first seen on, and marks for Third party, Local storage and Before consent.
Fixing “before consent”
Section titled “Fixing “before consent””- Make sure the CookieDoo snippet is the first script in
<head>, withoutasyncordefer. - Move tags that set the cookie (often analytics or ad pixels) into Google Tag Manager with consent triggers, or mark them as blocked with
type="text/plain"anddata-cookiedoo-category(see Block scripts). - Select Scan now to check.
Cookies set by your own server, such as a session cookie, appear here too; they should be necessary ones.