A cookie declaration that stays synced — and tells you when it drifts
A cookie declaration is only useful if it lists the trackers actually running on your site. The problem is they change — new apps, new tags, new pixels — and a static list silently goes out of date. ConsentPixel's declaration syncs to your real scans and flags exactly what changed: "new trackers found since last sync." No guessing whether your list is still true.
Creates your ConsentPixel account · 14-day free trial · no credit card · from $8.99/site per month after. Prefer to look first? The site scan needs no account.
A cookie declaration is a disclosure, not protection — it lists what's running, it doesn't block anything or make you compliant on its own. Its entire value is accuracy: a declaration that's out of date is worse than useless, because it tells visitors something untrue about your site. That's why syncing and drift-flagging matter more than the generating.
flagged
What is a cookie declaration?
A cookie declaration is the itemised list of the specific cookies and trackers running on your site — each one's name, who provides it, what category it falls in (analytics, advertising, functional), and what it's for. It's the factual inventory a visitor sees when they open your cookie settings and look at exactly what's being used.
The key word is factual. A declaration isn't an explanation or a promise — it's a list of what's actually there. Which means it has one job: be accurate. And that's exactly where most declarations fail, because the thing they're listing doesn't hold still.
Cookie declaration vs. cookie policy — what's the difference?
These two get mixed up constantly, and the distinction is simple once you see it:
| Cookie Policy | Cookie Declaration | |
|---|---|---|
| What it is | A written document explaining how & why you use cookies | A live, itemised list of the specific trackers running |
| Form | Narrative — paragraphs and sections | A table — name, provider, category, purpose |
| Where it lives | A policy page, usually linked in the footer | Usually inside your cookie/consent settings |
| How fast it dates | Slowly — updates when your practices change | Fast — every new tracker changes it |
Put simply: the policy explains, the declaration inventories. Most sites need both — and the declaration is the one that goes stale fastest, because it's tied to the specific trackers on your pages, and those change every time you add an app or a tag. ConsentPixel generates both, plus three more documents, from the same scan.
Why your cookie declaration goes stale (and why that's a problem)
Here's the lifecycle almost every site goes through. You set up a cookie declaration once — maybe from a scan, maybe by hand. It's accurate that day. Then, over the next few months:
- Marketing installs a new email or ads app — it drops a pixel.
- Someone adds a tag through the tag manager — a new tracker, invisible in your page's raw code.
- You swap analytics tools, or add a reviews widget, or a chat box.
Every one of those changes your real tracker list. None of them updates your declaration. So the list visitors see quietly diverges from what's actually running — and a declaration that claims you use four trackers when you're really running seven isn't just incomplete, it's inaccurate. It tells people something untrue about your site, which is the opposite of what a disclosure is for.
Most tools that auto-scan just silently update the list — so you never actually know when something changed. ConsentPixel syncs to your latest scan and explicitly flags the drift: "3 new trackers found since last sync." You see the change, decide, and re-sync. The declaration stays true, and you stay aware of what your own site is doing — instead of trusting a list you haven't looked at in six months.
How the cookie declaration generator works
- It syncs to your latest scan. Rather than asking you to maintain a list by hand, it builds the declaration from the trackers ConsentPixel actually detects on your site.
- It categorises what it finds. Each tracker is grouped — analytics, advertising, functional — with its provider and purpose, so the declaration reads clearly.
- It flags drift. When a newer scan finds trackers your declaration doesn't list, you get an explicit "new trackers since last sync" prompt — not a silent change.
- You publish and embed. Push it to a hosted page and add it to your footer or cookie settings with a link or embed snippet. Re-sync, and the hosted version updates at the same URL.
How this compares to a typical auto-scanning tool
| Typical auto-scan declaration | ConsentPixel | |
|---|---|---|
| Syncs to a scan | Yes | Yes |
| Shows you what changed | Silent update | Explicit drift flag |
| Part of a document suite | Often standalone | 1 of 5 documents, same scan |
| Honest about the sync gap | Rarely | Tells you trackers added since last scan aren't listed yet |
The middle row is the one that matters. Silently updating a list looks convenient, but it means you never actually know what your site started doing. Surfacing the drift keeps you in the loop about your own tracking — which is the entire point of the exercise.
Build a cookie declaration that stays true to your site
Sync it to a real scan, see the drift when trackers change, and publish it to a hosted page you embed once. Plus four more documents from the same scan.
Start free trial & generate →Creates your ConsentPixel account · 14-day free trial · no credit card · from $8.99/site per month. Information, not legal advice.
Cookie declaration FAQ
What is a cookie declaration?
It's the itemised list of the specific cookies and trackers running on your site — each one's name, provider, category (analytics, advertising, and so on) and purpose. It's the factual inventory a visitor sees in your cookie settings. Because the trackers on a site change over time, a declaration is only accurate if it's kept current with what's really running.
What's the difference between a cookie declaration and a cookie policy?
A cookie policy is the written explanation of how and why you use cookies — the narrative. A cookie declaration is the live, itemised list of the specific trackers actually running, usually shown in your consent settings. The policy explains; the declaration inventories. Most sites need both, and the declaration is the one that dates fastest because trackers change.
Why does a cookie declaration go stale?
Because your trackers change — a new marketing app, an added tag, a swapped analytics tool all introduce trackers your declaration doesn't yet list, and a static declaration silently falls out of date. ConsentPixel's declaration syncs to your latest scan and explicitly flags drift ("new trackers found since last sync"), so you can see when it needs updating rather than assuming it's current.
Can I embed the cookie declaration on my site?
Yes. Publish it to a hosted ConsentPixel page and add it with a copy-paste link or embed snippet in your footer or cookie settings. When you re-sync to a newer scan, the hosted version updates at the same URL, so you don't re-paste it. Generation is included from the Starter plan; you can also run a free scan without an account first.
Disclaimer: ConsentPixel — Privacy · Verified provides information and tooling, not legal advice, and is not a law firm. A cookie declaration is a disclosure of the trackers on your site; generating or publishing one does not by itself make your site compliant with any law, and you remain responsible for the accuracy of your setup and for keeping your declaration synced. Verify your obligations with qualified counsel.