Open navigation menu
RTB cookie syncing: what it means and how to review it
Trace possible identifier sharing back to the request chain that caused it. CertScore.ai helps DPOs, agencies and developers identify the tag or vendor to investigate and compare behavior before and after consent.
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. Follow the request chain
An illustrative chain might run from sync.vendor-a.example to match.vendor-b.example with an identifier-shaped parameter. These example domains explain the pattern; they are not scan findings.
Inspect the initiator, redirects, vendor, timing and consent state. Two advertising hosts appearing together do not by themselves establish identifier sharing.
2. Find the implementation owner
Identify the tag, plugin or embed that started the chain. Ask its owner to review consent categories, tag triggers and vendor settings. Compare the observed destination with the site’s disclosures.
3. Retest the affected behavior
After an approved change, compare fresh sessions under matching page and region conditions. Share evidence references with sensitive values removed so the developer, agency and DPO can review the same observation.
What the evidence can establish
Cookie storage, network requests and identifier sharing are separate observations. A stored cookie does not prove it was transmitted; an endpoint name does not prove matching or downstream use. Inspect the retained chain and coverage before drawing conclusions.
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.