Overview
How CookieWall applies consent
Learn how inventory categories, stored preferences, script mappings, and native consent signals determine browser behavior.
Last reviewed September 12, 2026
CookieWall publishes a categorized inventory and a map from observed script URLs to consent categories. On the website, the engine loads the project configuration, restores any saved preference, and evaluates mapped browser activity against that preference.
Runtime decision model
Use the following table to understand how each area supports the task.
| State | Outcome |
|---|---|
| Strictly Necessary | Allowed regardless of optional-category choices. |
| Mapped optional category granted | Allowed. |
| Mapped optional category denied or no choice yet | Blocked by the consent evaluator. |
| Unmapped resource | Allowed by default; investigate and classify it. |
| Supported tracker with its native signal integration enabled | The tracker can load and receives the corresponding consent signal instead of relying only on URL blocking. |