Public databases catch as little as
15%
of the cookies actually running on a real website
Cookie and Tag Database
Built from billions of real cookie observations over 10+ years, our human-curated database gives privacy teams trusted answers for every cookie and tag, not just what it is, but whether it belongs, how it should be categorized, and what to do next.
Trusted by the World's Most Trusted Brands
0
Years of Real Scans
0
Cookies Scanned
0
Tags Identified
0
Human-Curated Database
Every Unknown Cookie and Tag Raises Another Question.
What Is It?
Identify the vendor, purpose, and data it collects.
How Should It Be Categorized?
Use trusted, human-reviewed definitions.
Who Owns It?
Track ownership, approvals, and review history.
Should It Still Be Here?
Make informed decisions with removal guidance and organizational context.
See What's Actually on Your Site
Get a DemoHow the Cookie and Tag Database Works
Step 1
Run or view an existing ObservePoint scan
1
Step 2
Every cookie and tag is automatically matched against the Cookie and Tag Database
2
Step 3
Get the consent category, risk level, vendor, and references instantly, plus a place to record your own approval history
3
Already running ObservePoint audits? Cookie and tag definitions appear automatically. No new setup required.
This Tool Answers Questions Like:
Get a Demo
Which team is responsible for it?
What kind of data does it carry?
Do we still need it on our site?
Was this cookie approved by legal?
What does this cookie or tag actually do?
Who is the cookie vendor?
What Our Customers Discover
An average of
14
rogue cookies are uncovered per site.
An average of
22
rogue vendor scripts (tags) are uncovered per site.
Frequently asked Questions (FAQs)
- How is this different from Cookiepedia or the Open Cookie Database? keyboard_arrow_down
- It's built into ObservePoint and connected to your data, so definitions appear right where you're already working. And it captures your context: who owns a cookie, who approved it, your internal notes. An external database can't do that.
- Who maintains the definitions? keyboard_arrow_down
- ObservePoint curates and maintains a default set. You can add custom fields to OP definitions and create your own, but you can't change OP matching criteria.
- What happens when a cookie or tag matches more than one definition? keyboard_arrow_down
- Every item resolves to exactly one definition. If a definition has negative criteria that match, it's ruled out. After that, the most specific definition wins; if two are equally specific, yours beats OP's, and the oldest one settles any remaining tie.
- Can Free or Sample accounts use it? keyboard_arrow_down
- They see in-context definitions. The full library, definition detail screens, and matching criteria are for Contract accounts.
- Does this replace Consent Categories? keyboard_arrow_down
- No. We're not replacing Consent Categories. Instead, consent category information now appears on definition pages, and matching definitions show up inline when you edit a consent category.
- Can I bulk-edit definitions? keyboard_arrow_down
- Yes. Bulk editing is part of Phase 1.
Stop Guessing What's Running on Your Site
No credit card required. Just clear answers.