Try it through a tag manager
This page never has the Consentio script tag. Try it on this page always has one. This one is left to a Google Tag Manager container instead — the other way of installing — and on the published site so is every page but that one.
It exists because there is one failure that never fails loudly — the two routes disagreeing about the same visitor. Answer the banner on Try it on this page, 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.
The container is GTM-K6V53LMT. No banner here means the Consentio template is not imported into it.
A banner that forgets an answer given on another page means the template’s version field and this site’s
disagree, and a mismatch discards the whole stored value.
🔍 What to compare
| Try it on this 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 three files, fetched by the script tag | variables in the container holding the same files - kept equal by hand |
| 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…