Try it through a tag manager
This page has no Consentio script tag. Every other page here has one. This one is left to a Google Tag Manager container instead — the other way of installing.
It exists because there is one failure that never fails loudly — the two routes disagreeing about the same visitor. Answer the banner on any other page here, then come back to this one. Both routes read the same cookie by the same rules, so the answer has to survive the trip. If it does not, one of the two readers is wrong, and the cookie contract says which.
There is no container configured, so this page currently shows nothing at all. Once one is set and it carries the Consentio template, the banner appears here through the tag manager instead of through a script tag.
🔍 What to compare
| Every other page | This page | |
|---|---|---|
| What runs first | the Consentio script tag, in <head> |
the template, on the Consent Initialization trigger |
| Who tells Google what is allowed | the script tag | the Tag Manager template |
| Where settings come from | the two settings files | fields in Tag Manager |
| The cookie | consentio |
consentio — the same one |
window.ConsentioDefault is set by the script tag and by nothing else, so it is missing here. That is the
quickest way to tell which of the two a page is using.
Reading…