Diagnostics: What Was Measured
Read observed findings, unknowns and partial verification correctly.
Content and code last checked 2026-10-06 by ConsentEase product documentation. This is a review of the written content and code, not a test on a live third-party platform.
Run a diagnostic for the selected website
Open Diagnostics, inspect the most recent run, and run a new check when the live installation changes. A queued/running/failed record is not measured evidence. Check timestamps and the tested URL before relying on an older result.
Read the scope
Diagnostics inspect a bounded page load and any explicitly reported verification steps. Findings reflect what the browser observed in those windows, not every route, geography, device, authenticated state or future visit.
Interpret results
Green/verified results need measured supporting evidence. Unknown, skipped, partial and failed checks must not be interpreted as passes. “Banner detected” is different from “all optional tags obeyed consent.”
Runtime verification
Where choice transitions are measured, examine before/after states and uncertainty. A request seen before/after an action needs context; a timing window does not always establish causality. Advanced Consent Mode can send denied/cookieless Google requests.
Follow up
Inspect the site's real network and GTM/provider configuration, fix confirmed issues and rerun. Keep observations separate from inventory classifications and legal conclusions. Scanner scores, stored status labels and an empty finding list are not legal certifications.