Overview
The Cookie & Tag Database is an in-app reference for the cookies and tags ObservePoint sees on your sites. When you don't recognize a cookie or tag, you can look it up here instead of leaving the app, and see its vendor, purpose, category, how to remove it, and more.
Each entry is called a definition, and it has two parts:
Matching criteria: how ObservePoint recognizes a cookie or tag (for example, "cookie name is _ga").
Fields: the information the definition provides about anything it matches, such as vendor, purpose, category, owners, and notes.
ObservePoint maintains a curated set of default definitions for well-known cookies and tags. You can add your own fields to those, and create your own definitions for anything we don't cover.
Screenshot: Cookie & Tag Database library home
How to Access
Sign in to ObservePoint.
Go to Cookie & Tag Database (app.observepoint.com/xxx). This is the "library."
Use the tabs to switch between Cookies and Tags.
The full library and definition detail screens are available to contracted customers. On Sample and Free accounts you'll still see definitions in context, for example inside a report, but not the full library.
How to Use
Look up a cookie or tag
Open the library and choose Cookies or Tags.
Search by name. You can look up an entity even if it has never appeared in one of your reports.
Select a result to open its definition detail page (app.observepoint.com/data-dictionary/definition/{definitionId}).
Review the fields. For an ObservePoint-curated cookie, you'll usually see vendor, purpose, category, data classification, prevalence, risk, and reference sources, plus any custom fields your account has added.
Screenshot: Definition detail page
See Definitions Where You Already Work
Definitions show up throughout ObservePoint, not just in the library:
Reports: definition fields show up as columns you can filter, sort, group, search, and export.
Audit reports: Cookie Inventory, Tag Inventory, and Cookie Privacy Compliance, etc, and on Page Details
Journey reports: the cookie and tags tabs.
HAR Analyzer and LiveConnect reporting.
Tag rules and consent categories: definitions appear inline as you configure them.
If a cookie or tag has no matching definition, you'll see its basic attributes (name, domain, party type) and a note that it needs classification. Create a definition to fill in the rest.
Pull "your" Cookies and Tags Into a Report
There's no separate "my cookies" filter. Instead, build a grid report for the entity, add the columns you care about (entity attributes plus the Matched Definition column and any fields), and group by them. That gives you an account-specific view of everything matched to a definition. Here is an example report.
How Matching Works
Every cookie or tag matches exactly one definition. When more than one could match, ObservePoint breaks the tie in this order:
The most specific definition wins.
Your definitions beat ObservePoint's.
The oldest definition wins.
So a definition you create for a specific site or domain shows instead of the general ObservePoint default.
Best Practices
Search before you create. ObservePoint may already define the cookie or tag, so you only need to add your own fields rather than start from scratch. Hint, always add definitions directly from a report, this way you'll already know if a defintion exists.
Use page domain in your matching criteria to tell apart cookies that share a common name, especially third-party cookies.
Make custom definitions only as specific as they need to be. Over-specific criteria can stop matching when a value changes slightly.
Record owners and approvers as fields, so the "who do I ask about this?" question always has an answer.
Common Questions
How is this different from Cookiepedia or the Open Cookie Database?
It's built into ObservePoint and connected to your data, so definitions appear where you're already working. It also holds your own context: who owns a cookie, who approved it, your internal notes. An external database can't do that.
Who maintains the definitions?
ObservePoint curates and maintains a default set. You can add custom fields to those and create your own definitions or make copies of ours, but you can't change ObservePoint's definitions.
Does this replace Consent Categories?
No. Consent category information now appears on definition pages, and matching definitions show up inline when you edit a consent category.