The usual reason: we do not recognise it
ConsentCook holds back the trackers it knows — the common analytics, advertising and chat tools. Something unusual, or built specially for your site, is not on that list.
Fix it by marking the script on your site with the purpose it serves. Once marked, ConsentCook keeps it inert until a visitor agrees to that purpose, and runs it the moment they do without reloading the page. Your developer can do this in a couple of minutes; the Developers page has the exact instructions.
The second reason: it loads before we do
If the ConsentCook line sits below other scripts in your page, those scripts have already run by the time it starts. Move our line as high in the <head> as you can.
The third reason: your platform sets it
Some hosting platforms set their own storage that no consent tool running in the browser can prevent. Where we spot one, we say so plainly rather than pretending we have handled it, and point you at what the platform itself lets you change.
Still stuck?
The live chat is on every page, or email support@consentcook.com. A person answers, on every plan.