This guide explains how to research cookies that are not clearly identified during a scan or that still appear as unknown, uncategorized, or undocumented in your review process.
Use this process when you want to understand what a cookie does, where it comes from, and how it should be classified inside Cookiedad.
When to use this guide
Follow these steps if:
- a cookie appears in your browser or scan results but has no clear description
- the cookie is marked as unknown or uncategorized
- you want to confirm whether a cookie is necessary, functional, statistical, or marketing
- you need stronger evidence before adding it to your internal documentation or policy
Step 1: Copy the exact cookie name
Start by copying the cookie name exactly as it appears.
Do not simplify it and do not remove prefixes, numbers, or special characters unless you are intentionally testing a variation later.
The exact name matters because many cookies look similar but belong to different tools or services.
Step 2: Check where the cookie appears
Before searching the web, confirm the context in which the cookie is loaded.
Ask yourself:
- on which page did the cookie appear
- did it appear before or after consent
- was there an embedded video, map, form, chat, analytics script, ad tool, or payment element on the page
- is the cookie first-party or related to a third-party service
This step is important because the page context often tells you more than the cookie name alone.
Step 3: Search the exact cookie name in a search engine
Search for the full cookie name using quotation marks.
Example:
"_ga""test_cookie""IDE"
Using quotation marks helps you find results that match the exact cookie name instead of unrelated pages.
Start with the exact search first before trying broader variations.
Step 4: Look for reliable sources first
Focus on sources that are more likely to be accurate.
The most useful sources are usually:
- official vendor documentation
- official support articles
- platform documentation
- privacy or cookie documentation from the service provider
- well-maintained cookie reference databases
Do not rely immediately on random forum posts or low-quality lists if you can find a direct source from the service itself.
Step 5: Search the vendor name together with the cookie
If the exact search is too broad, combine the cookie name with the tool or provider you suspect is using it.
For example, search the cookie name together with terms such as:
- Google Analytics
- YouTube
- Meta Pixel
- Stripe
- PayPal
- HubSpot
- Hotjar
- Cloudflare
This usually gives you more targeted results and helps confirm ownership faster.
Step 6: Search by cookie prefix if needed
Some cookies use dynamic names and change slightly from one site to another.
For example, a cookie may contain a fixed prefix and a variable ending. In that case, search the stable part of the name.
This is useful when the cookie looks like it belongs to a family rather than a single exact identifier.
Be careful not to guess too quickly. A similar prefix does not always mean the same provider.
Step 7: Check what the cookie is used for
When you find a likely match, verify the purpose.
Try to confirm:
- what service sets the cookie
- whether it is first-party or third-party
- what function it supports
- whether it stores session, preference, analytics, or advertising data
- whether it is persistent or session-based
Your goal is not only to find a name match, but to understand the cookie’s practical role.
Step 8: Verify whether the result fits your website
Do not classify a cookie only because a website online says it belongs to a certain service.
Make sure that same service is actually present on your site.
For example, if a page says a cookie belongs to HubSpot but your site does not use HubSpot at all, that result may not apply to your case.
The classification must match both:
- the research result
- the real tools active on your website
Step 9: Confirm with browser and page behavior
If needed, go back to the site and test again.
Check whether the cookie appears:
- only on specific pages
- only after consent
- only after clicking an embedded element
- only when a third-party service becomes active
This practical check helps you confirm whether your research result makes sense in a real session.
Step 10: Assign the most appropriate category
Once the source and function are reasonably clear, assign the cookie to the most appropriate category in Cookiedad.
A practical approach is:
- Necessary if the cookie is essential for core site or service functionality
- Functional if it supports preferences or non-essential features
- Statistical if it is used for analytics or measurement
- Marketing if it is used for advertising, tracking, profiling, or retargeting
If the purpose is still unclear, keep it under review instead of forcing a weak classification.
Step 11: Document your findings
After identifying the cookie, save the result in your workflow or internal notes.
Record at least:
- cookie name
- provider
- purpose
- category
- duration if known
- page or feature where it appears
- source used for verification
This makes future reviews faster and keeps your compliance process more consistent.
What to do if you still cannot identify it
If the cookie is still unclear after research:
- test the site again in a clean browser session
- isolate the page or feature that triggers the cookie
- review the active plugins, scripts, tags, and embedded services on that page
- check whether the cookie may be custom or site-specific
- keep it temporarily marked for manual review
Not every cookie can be identified instantly. Some are custom, temporary, or generated by specific integrations.
Common mistakes
Relying on the first result too quickly
A search result may mention the same cookie name but refer to a different context.
Ignoring the website’s actual tools
A cookie classification is only useful if it matches the services really active on your site.
Classifying by guesswork
If the purpose is unclear, do not force a category just to finish faster.
Forgetting that some cookie names are dynamic
Some cookies belong to a known family even if the full name changes between sessions or sites.
Final result
You have successfully researched an unknown cookie and built a more reliable basis for classification inside Cookiedad.
This process helps you move from a raw cookie name to a documented, reviewable result that is much easier to manage during compliance checks.