Open navigation menu
Pre-consent tracking: what it means and how to review it
Pre-consent tracking means classified tracking requests or non-essential cookies appear before a recorded consent choice. CertScore.ai treats this as an automated risk signal that should be reviewed against the underlying request, cookie, and consent evidence.
Run a free website behavior scan
Check observable tracking, cookies, consent, accessibility, and privacy risk signals.
What CertScore observes
CertScore.ai reviews the initial page-load window, consent surface signals, classified tracking requests, and cookie timing. The scan looks for activity that appears before a clear consent interaction has been recorded.
In recent CertScore benchmark scans, this signal appeared in roughly one in five scanned sites. That context is directional, not a legal conclusion about any specific website.
How teams should review it
Review the vendor names, request timing, cookie names, and consent interaction evidence before deciding whether the behavior is expected.
False positives can occur when a request is misclassified, a consent state already exists, a region-specific banner behaves differently, or a site blocks part of the automated scan.
Run a free website behavior scan
Check observable tracking, cookies, consent, accessibility, and privacy risk signals.