Feature
Cookie Categorisation
Classify observed cookies by purpose so visitor choices can be meaningful and consistently applied.
A discovered cookie name alone does not tell a visitor or site team how it should be treated. Visitor choices may be too broad, misleading, or disconnected from actual technologies.
What Cookie Categorisation does
Cookie categorisation assigns cookies or related technologies to a purpose-based category used by a website’s consent design.
A discovered cookie name alone does not tell a visitor or site team how it should be treated.
It reviews technology attributes, assigns categories, and maintains the mapping used by cookie controls.
Why Cookie Categorisation matters
A discovered cookie name alone does not tell a visitor or site team how it should be treated.
Visitor choices may be too broad, misleading, or disconnected from actual technologies.
Teams may apply informal labels with no shared reasoning or consistent treatment.
How Cookie Categorisation works
- Review a discovered technology.
- Collect available purpose and behavior context.
- Assign a category under the chosen taxonomy.
- Approve or flag the mapping.
- Use the category in visitor-choice configuration.
Key capabilities
- Purpose-based categories
- Technology-to-category mapping
- Mapping review
- Category taxonomy
- Change tracking
Configuration & controls
Define the category taxonomy, review owners, criteria for assignment, vendor or technology metadata, and re-review triggers.
Workflow & architecture
Categorisation translates discovered technologies into a choice model; it does not discover items or provide the preference interface.
Categorisation maps known technologies into a choice taxonomy. It does not discover technologies or provide the banner or preference interface.
Integrations
It can receive findings from a scanning process and supply mappings to a banner or preference centre. Classification remains subject to human review and organizational policy.
Security & audit
Review technology identifier, category, rationale or metadata, mapping owner, change date, and downstream use.
Implementation
- Define a clear taxonomy.
- Triage baseline findings.
- Assign owners for ambiguous items.
- Map categories to controls.
- Revisit mappings after site changes.
Related features
Product context
Cookie Categorisation 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 cookie categorisation?
Cookie categorisation assigns cookies or related technologies to a purpose-based category used by a website’s consent design. It reviews technology attributes, assigns categories, and maintains the mapping used by cookie controls.
How are website cookies categorized?
It reviews technology attributes, assigns categories, and maintains the mapping used by cookie controls. Categorisation maps known technologies into a choice taxonomy. It does not discover technologies or provide the banner or preference interface.
What are common cookie categories?
Cookie categorisation assigns cookies or related technologies to a purpose-based category used by a website’s consent design. It reviews technology attributes, assigns categories, and maintains the mapping used by cookie controls.
How should cookies be classified by purpose?
Define the category taxonomy, review owners, criteria for assignment, vendor or technology metadata, and re-review triggers. It reviews technology attributes, assigns categories, and maintains the mapping used by cookie controls.
Why is cookie categorisation important for consent?
A discovered cookie name alone does not tell a visitor or site team how it should be treated. Visitor choices may be too broad, misleading, or disconnected from actual technologies. Without a defined control, teams may apply informal labels with no shared reasoning or consistent treatment.
Who should own cookie categorisation?
Ownership usually sits with the team accountable for the affected journey and policy, with privacy operations providing governance oversight. Define the category taxonomy, review owners, criteria for assignment, vendor or technology metadata, and re-review triggers.
What should be configured first for cookie categorisation?
Define the category taxonomy, review owners, criteria for assignment, vendor or technology metadata, and re-review triggers.
Does cookie categorisation guarantee DPDP compliance?
No. cookie categorisation can support operational implementation of cookie categorisation, but it does not by itself guarantee DPDP compliance because legal obligations depend on the organization’s processing context and controls.
See cookie categorisation in your consent operations
Discuss how web, marketing, and privacy teams can use cookie categorisation to address a discovered cookie name alone does not tell a visitor or site team how it should be treated.
Book a Demo