| Lists cookies on the current pageYour browser already carries your consent choice and your logged-in state; a first-time visitor's browser does not. | Yes, from your own browser session | Yes, from a clean browser in the US or Germany |
|---|
| Before vs after consentThe before-consent list is what regulators and lawsuits look at. | No. One snapshot of whatever is set when you click | Two phases: everything before the click, everything after |
|---|
| Which script set each cookieA developer cannot fix "_ga was set" without knowing which tag did it. | No. Name, domain and expiry only | Yes. The tag or script behind each cookie, with the request timeline |
|---|
| Trackers that set no cookieServer-side and cookieless tracking never show up in a cookie list. | Not visible | Captured: pixels, beacons and third-party requests, with timestamps |
|---|
| Consent banner checkInstalled is not the same as working. | No | 30+ platforms recognised; tests whether rejecting blocks trackers |
|---|
| Google Consent Mode v2 | No | Default state, four signals and the update after the click, read off the network |
|---|
| Multiple pages and scheduling | One page at a time, by hand | Up to 5 pages per scan; scheduled monitoring with alerts on Pro |
|---|
| Report you can hand to someone | Copy the list by hand | PDF, Notion and Confluence exports; a How to fix guide for the developer |
|---|