Open navigation menu
How to check third-party cookies before consent
Find which cookies and services appear before a visitor makes a choice. Use the timing and vendor evidence to review CMP categories and tag triggers, then retest the affected page.
By CertScore.ai · Updated
Website privacy scanner. See the evidence.
Review cookies, trackers, consent behavior and privacy disclosures. Give your DPO, agency or developer retained evidence for GDPR/ePrivacy and CCPA review.
1. Start with a fresh session
Record the URL, region, time and browser settings. Inspect cookie storage and network activity before making a banner choice. Prior consent and privacy extensions can change the result.
2. Match cookies to service activity
Review cookie name, domain, path, lifetime and first-seen time alongside request evidence. Keep sensitive values out of shared notes. A third-party service can use first-party storage, so domain ownership alone does not establish purpose.
3. Review the category and trigger
Give the CMP or tag-manager owner the observed vendor and timing. Check whether the category and trigger match the intended behavior. After a change, compare a fresh baseline and eligible choice sessions.
Read storage and requests separately
Blocked third-party cookies do not mean that no requests occurred. An unchanged cookie does not prove active use. Unsupported classifications, missing timestamps and inaccessible frames remain coverage limits.
Related CertScore.ai pages
Website privacy scanner. See the evidence.
Review cookies, trackers, consent behavior and privacy disclosures. Give your DPO, agency or developer retained evidence for GDPR/ePrivacy and CCPA review.