The QookieQloud audit report provides an objective, legally grounded, and technical baseline of how your website handles cookies, tracking pixels, and visitor consent in real time.
Here is how to interpret each section of the report—from the overall compliance score to the deep V3 load timing timeline.
1. Score Panel & Compliance Score
At the top of the report, overall website compliance is summarized in a score from 0 to 100 points, calculated from three foundational pillars:
- GDPR Tag Blocking: Requires all non-essential scripts to be withheld until positive consent is granted.
- Google Consent Mode v2: Verifies that standard signals (
ad_storage,analytics_storage, etc.) initialize properly. - Cookie Declaration & Storage: Ensures cookies have clear purpose descriptions, proper categories, and compliant expiration limits.
In the widget above, toggle between sample scenarios to see how the score panel adapts. A score above 80 indicates solid compliance, while scores below 60 reveal pre-consent leaks.
2. The Four Audit Pillars
Below the score card, findings are structured into four actionable categories:
Pre-consent leaks
Scripts that make network requests immediately on page start before the visitor interacts with the cookie banner.
Post-reject activity
The scanner simulates clicking "Reject All" to verify that marketing and analytics pixels cease data transmission.
Unclassified cookies
Cookies missing purpose descriptions or category tags. QookieQloud uses AI to suggest categorization automatically.
Google Consent Mode v2 signal health
Confirms that standardized consent states reach Google Tag Manager, essential for Google Ads and GA4 modeling in Europe.
3. V3 Deep Analysis & Load Timing Timeline
From any base report, you can trigger a V3 Deep Consent Scan. The V3 engine launches a real headless browser session, timestamps every network request down to the millisecond from page start (0 ms), and executes physical banner interactions.
Key Milestones on the Timeline
- 0 ms (Page Start): The exact moment the browser begins retrieving the initial HTML document.
- Consent Manager (CMP, e.g. 63 ms): When your Consent Management Platform renders the banner on screen.
- Pre-consent Trackers (e.g. 208 ms): Trackers firing here violate privacy rules because the user has not yet consented.
- Consent Interaction (Click, e.g. 920 ms): The precise millisecond the user clicks a choice. Only after this milestone may consented tags run.
Under GDPR, simply loading a banner quickly is not enough. Non-essential tracking must be halted until the visitor actively clicks "Accept". The V3 timeline provides irrefutable millisecond proof.
4. Running On-Demand V3 Audits from the Dashboard
Open Customize → Mode for the selected domain. The V3 scanner is at the bottom, below the mode selector and any regional overrides shown in Auto mode. Save your changes before starting a scan and check your remaining scan allowance. Expand the latest result to open its report.
Quotas & Resets
Free accounts receive 3 on-demand scans per month (resets on the 1st). Paid Pro plans receive 3 on-demand scans per week (resets every Monday).
Smart Background Queue
Scans are safely queued in the background with real-time UI status updates until your full V3 report and score are ready.
5. Zooming & Horizontal Pan
Modern sites often load multiple tags in close succession. The timeline includes zoom controls (100% – 250%) to expand the horizontal track and inspect clustered requests effortlessly.
6. Concrete Action Recommendations
At the bottom of the report, QookieQloud provides precise instructions for each identified tracker: which script triggered the request, which trigger in Google Tag Manager to modify, and which consent condition to require.
Already have a report? Start with cookies and trackers that load before consent. If you are setting up QookieQloud, create an account and follow the guide for your platform. Then test before a choice, after rejection and after acceptance, and run a new scan to check your changes.
