Feature
Cookie Scanner
Discover cookies and similar web technologies on selected properties so teams can review what is present.
Website changes can introduce new technologies that are not reflected in a team’s inventory. Teams may rely on a stale manual inventory while the site changes.
What Cookie Scanner does
A cookie scanner examines configured web pages to identify observed cookies and related tracking technologies.
Website changes can introduce new technologies that are not reflected in a team’s inventory.
It visits selected pages or journeys, records observed technologies, and presents findings for review.
Why Cookie Scanner matters
Website changes can introduce new technologies that are not reflected in a team’s inventory.
Teams may rely on a stale manual inventory while the site changes.
New cookies may only be discovered after an issue, vendor review, or manual inspection.
How Cookie Scanner works
- Choose a site or page scope.
- Run the scan against the configured journey.
- Observe cookies or technologies encountered.
- Record findings.
- Review and triage findings with site owners.
Key capabilities
- Property scanning
- Observed-technology inventory
- Page or journey scope
- Finding review
- Repeat scan support
Configuration & controls
Set domains, paths, scan conditions, authenticated or public scope where applicable, ownership, and review cadence.
Workflow & architecture
Scanning discovers what is observed; classification and visitor-facing choice presentation occur in separate steps.
The scanner discovers what appears on selected web journeys. Categorisation classifies those findings, while the banner presents visitor choices.
Integrations
It examines the configured web property and produces findings for internal review. Discovery coverage depends on the pages, conditions, and journeys included.
Security & audit
Keep scan time, scope, observed item, source page, and review disposition available to explain inventory changes.
Implementation
- Choose representative journeys.
- Run a baseline scan.
- Assign finding owners.
- Compare after releases.
- Review coverage as the site evolves.
Related features
Product context
Cookie Scanner is a capability withinConsentifyAI Cookie Consent. Use the product page for commercial evaluation; this page explains the operational capability.
Solution context
See how this capability can support a broader business or compliance problem on therelated solution page.
Industry context
For sector-specific journey patterns, explore therelated industry page.
DPDP context
This feature page explains the product capability. Related DPDP glossary pages own the legal and regulatory explanation. The capability can support operational implementation; it does not by itself guarantee legal compliance.
FAQ
What is a cookie scanner?
A cookie scanner examines configured web pages to identify observed cookies and related tracking technologies. It visits selected pages or journeys, records observed technologies, and presents findings for review.
How does a cookie scanner work?
It visits selected pages or journeys, records observed technologies, and presents findings for review. Typical sequence: 1) Choose a site or page scope; 2) Run the scan against the configured journey; 3) Observe cookies or technologies encountered; 4) Record findings; 5) Review and triage findings with site owners.
How can I scan a website for cookies?
Set domains, paths, scan conditions, authenticated or public scope where applicable, ownership, and review cadence. It visits selected pages or journeys, records observed technologies, and presents findings for review.
How do you identify third-party cookies?
It visits selected pages or journeys, records observed technologies, and presents findings for review. Typical sequence: 1) Choose a site or page scope; 2) Run the scan against the configured journey; 3) Observe cookies or technologies encountered; 4) Record findings; 5) Review and triage findings with site owners.
How often should a website scan for cookies?
It visits selected pages or journeys, records observed technologies, and presents findings for review. The scanner discovers what appears on selected web journeys. Categorisation classifies those findings, while the banner presents visitor choices.
Why is cookie discovery important?
Website changes can introduce new technologies that are not reflected in a team’s inventory. Teams may rely on a stale manual inventory while the site changes. Without a defined control, new cookies may only be discovered after an issue, vendor review, or manual inspection.
Who should own cookie scanner?
Ownership usually sits with the team accountable for the affected journey and policy, with privacy operations providing governance oversight. Set domains, paths, scan conditions, authenticated or public scope where applicable, ownership, and review cadence.
What should be configured first for cookie scanner?
Set domains, paths, scan conditions, authenticated or public scope where applicable, ownership, and review cadence.
See cookie scanner in your consent operations
Discuss how web, marketing, and privacy teams can use cookie scanner to address website changes can introduce new technologies that are not reflected in a team’s inventory.
Book a Demo