Topic starter
24/10/2026 8:49 pm
TL;DR: Coverage, not page count, is the measure that reveals changing cookies, long-tail trackers, and third-party hops in cookie scanning, according to Ketch. Privacy teams need sampling that matches site structure, or inventories and disclosures can drift away from what is actually running.
Editorial analysis by NHI Mgmt Group, based on content published by Ketch: “Why cookie scanning is broken (and how Iris fixes it)”.
Key questions
Q: Why does in-page monitoring miss some third-party cookies?
A: Because code running inside the page can only observe what the browser exposes in that page context.
Q: How do privacy teams know if scanner coverage is good enough?
A: They should look for coverage across structurally distinct cohorts, not just a high URL count.
Q: What breaks when cookie scanning relies on page count instead of coverage?
A: Page-count scanning breaks when teams assume volume equals visibility.
Practitioner guidance
- Define tracker coverage as the primary KPI Replace page-count reporting with a coverage metric tied to distinct tracker signatures, site cohorts, and observable cookie sets.
- Map the site into operational cohorts Group URLs by template, platform, geography, and visitor state so that scanning samples represent structurally different tracker footprints.
- Test scanner visibility against known third-party flows Use checkout paths, campaign pages, and embedded vendor redirects to check whether the scanner sees downstream cookies and hop distance correctly.
Bottom line: Page-count metrics can hide serious discovery gaps when tracker behaviour varies by template, user state, and vendor chain.
Glossary terms: Tracker Coverage, Cohort-Based Scanning, Cookie syncing, Third-Party Cookie
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
25/10/2026 11:13 am
Coverage is the control objective, not crawl volume: page scanning in privacy programmes fails when teams confuse effort with evidence. A site can be heavily scanned and still remain poorly understood if the sampling model ignores site cohorts, visitor states, and vendor chains. Practitioners should treat coverage as the measurable outcome and page count as an input cost, not the reverse.
A question worth separating out:
Q: Should organisations prioritise random sampling or cohort-based scanning?
A: Cohort-based scanning is the better default when the site has multiple templates, vendor chains, or regional experiences. Random sampling can be economical, but it is weak at finding rare trackers that cluster at structural seams. The decision should hinge on whether the site’s tracker footprint is uniform enough for sampling to be trustworthy.
👉 Read our full editorial: Tracker coverage matters more than page count in cookie scanning
This post was modified 7 days ago by NHI Mgmt Group