Tracker detection accuracy
These rates come from checked-in HTML fixtures, not an independent lab corpus. They are not a field false-positive/false-negative rate on the live web.
On this page
1Fixture summary
Scored cases (excluding documented gaps): 6/6 passed (100%). Documented known gaps in this corpus: 1 false-positive class, 1 false-negative class.
Covered: known analytics/ad pixels, a clean page, CMP banner markup, iframe pixels, delayed inline loaders, first-party GTM proxy paths. Known gaps: consent-gated tags that keep a tracker src in the DOM (over-report); CNAME cloaking with no known analytics path (miss).
2Cases
- Known Google Analytics + Meta pixelPass · expected Google, Meta · found Google, Meta
- No trackersPass · expected none · found none
- Consent banner markupPass · expected none · found none
- Iframe trackerPass · expected Meta · found Meta
- Delayed script still in HTMLPass · expected Google · found Google
- Consent-gated tag that keeps tracker src in the DOMFail · known false positive · expected none · found Google
- CNAME cloaking without a known analytics pathPass · known false negative · expected none · found none
- First-party GTM proxy pathPass · expected Google · found Google
3What this is not
We have not published an independent measurement of false-positive or false-negative rates on a labeled live-web corpus. Headless scans can still miss tags that load only after a click, after geo/consent APIs, or behind bot defenses. See the methodology page for browser behavior.
PrivBeacon leverer automatiske privatlivsscanninger og dokumentskabeloner til informationsformål. Dette er ikke juridisk rådgivning. Rådfør dig med kvalificeret juridisk rådgiver, før du stoler på genererede politikker eller overholdelsesresultater for lovmæssige beslutninger.