Understand results and evidence
Read consent paths, coverage, priority, and limitations before deciding what to change.
6 min readOn this page
What a check measures
| Path | What to inspect |
|---|---|
| First load / observe | Cookies and banner behavior before the visitor chooses a consent option. |
| Accept | Whether the accept control works and the stored consent state matches the requested choice. |
| Reject | Whether rejection is recorded and known tracking cookies remain after verified refusal. |
Each path uses a fresh browser session. The chosen location reflects configured browser egress. The report records the URL that was checked; changing your site’s address later does not rewrite that evidence.
Read coverage and check status separately
| Check status | Meaning |
|---|---|
| Queued | Saved and waiting for a worker. |
| Checking | A worker is capturing evidence. |
| Check complete | All three consent paths have complete coverage. Findings may still need attention. |
| Incomplete evidence | At least one path could not be fully measured. Available evidence can still be useful. |
| Check interrupted | The check did not produce usable completed coverage. Review the interruption and retry when its cause is addressed. |
Coverage describes how well a path was measured. A successfully measured consent action that produces the wrong stored choice can have complete coverage and a high-priority finding. Missing cookies, screenshots, an unsuccessful control interaction, or an unreadable consent record can limit the conclusion.
Use findings to decide where to start
Findings collect a specific observation, its consent path, priority, suggested fix, and verification steps. The Findings view puts higher-priority work first and lets you filter by site, location, and review status. Its current queue uses the latest finished evidence for each active site’s current URL and location; older evidence remains in its saved reports.
- Inspect the exact cookie names and domains, rather than treating a title as the whole diagnosis.
- Read screenshots alongside the stored consent state: a button can appear to work without saving the requested choice.
- Prioritize observed tracking before consent or after verified rejection, and consent controls that fail to produce the requested state.
- Check the latest report for each visitor location you care about. Different locations can show different consent behavior.
Understand the limits of a check
CookieTrail records known cookie identities and selected analytics and advertising request endpoints during a bounded browser visit. Expand Measured requests under each path to see scripts, collection endpoints, response codes and timing. Failed attempts are distinguished from responses. Older reports may have no request capture. Unknown endpoints, first-party proxies and server-side activity are not covered.
Cookie presence after rejection does not prove a fresh write. A collection request receiving a response does not establish its payload or a consent violation; consent-mode cookieless pings can be intentional. Inspect the request's consent signals, payload and initiator before changing the site's configuration. Request evidence excludes bodies, headers and query values.
The supported rules treat initial known tracking cookies in Germany and the UK as pre-consent findings. Initial cookie presence in other locations is not automatically treated as a failure. A report is browser evidence to support investigation, not legal compliance certification.