Compliance
Scripts wait for a yes
A banner that only asks is not enough: the page must not set cookies before the answer. CookieForever's blocker runs first on your pages and holds back what needs consent.
How the blocker works
Runs before everything else
The blocker is the first script in <head>, loaded synchronously on purpose: a tag that has already run has already set its cookies.
Holds known tags
Tags that match a rule — from our curated library of trackers, or one of your own — are held until their category is granted, then released without a reload.
Guards the cookie jar
First-party cookies in a category that is not granted are refused when a script tries to write them.
Clears on withdrawal
When a visitor withdraws or narrows their consent, cookies from the refused categories are cleared and the page is reloaded, so no tag that was let through keeps running.
Rules per site
Each site gets its own ruleset: our curated rules plus your own. Suggestions from a language model or from other customers never block anything on your site.
Works with your tag manager
If your tags are managed in Google Tag Manager with Consent Mode, the script can run in signal-only mode and leave the holding to your tag manager.
What it does not cover
- A script that matches no rule is not held back. The scan shows you what runs on your site, so a rule can be added for it.
- Scripts written directly into the page's HTML must be marked with
type="text/plain"and their category to be held. - Cookies set by another domain, or marked HttpOnly by your server, cannot be deleted from the page.
Questions about compliance?
Write to us — we answer questions about how the platform works before you commit to anything.