You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The consent default is now pushed by the loader, before the tag manager starts, instead of by the banner
after two fetches and a DOM insert. A tag manager reads consent when it loads, so the old order meant the
banner gated nothing.
The loader reads data-debug, data-config-url and data-cookies-url from its own script tag. The
bundle published at 0.0.4 read three different names and so ignored every one of them.
The source is TypeScript and has a test suite. The published files are unchanged in shape: the same UMD
bundle, the same loader, at the same paths under dist/.
Tag Manager route: the template now sets the consent default itself, read from the cookie, before it
loads the banner. It used to set none at all, so on that route the container had already read consent by
the time the banner arrived. Install the new version of the template alongside this release.
Tag Manager route: the banner's wording is now chosen with one Text source field - built-in English,
your own text in fields that arrive already filled in, or any Tag Manager variable. The separate Consentio Tag - Texts variable template is gone; its strings are on the tag.
Your stored answer is now kept as {"version":1,"consents":{...}} rather than with the categories beside
the version. Everyone who has already answered is asked once more, because a value in the old shape
reads as no answer.
🛠️ Fixed
Consentio.version is taken from package.json at build time. It was written by hand in a second place
and could disagree with the release it shipped in.