Use Google Tag Manager

You are adding one template to your container, on one trigger. Nothing is pasted into your HTML and nothing is hosted by you. There is a second, optional template for your cookie table.

🚀 Four steps

1. Import the Consentio template into your container.

Download consentio-tag.tpl from the latest release. In Tag Manager go to Templates → Tag Templates → New, open the ⋮ menu at the top right, choose Import, pick the file and Save.

There is nothing to search for and nothing that tells you when a newer one exists. It is provided as it is: what you import is what your container runs until you import a newer file.

2. Make a tag from it, on the Consent Initialization trigger.

Use the built-in Consent Initialization - All Pages. Not All Pages — Consent Initialization. Tag Manager guarantees that trigger runs before every other trigger in the container, and that guarantee is the only reason the answer arrives in time.

3. Fill in the fields. Everything has a working default, so you can publish first and come back.

The one that matters is Text source. Leave it at Built-in English and the banner uses its own wording. Set it to Custom and every string appears in a box, already filled in with that English — change what you want, or paste a translation over it. Set it to From a variable and the wording comes from a Language pack variable — any Tag Manager variable holding a language pack. A pack downloaded from a release (en.json, el.json) goes in unedited, and a Lookup Table keyed on the page’s language is how you switch wording by language.

For the cookie table, download consentio-tag-cookies.tpl from the same release and import it the same way - under Variable Templates rather than Tag Templates. Make a variable from it, fill in your rows, and pick it here. Settings lists every option.

4. Publish, then move everything else into the container. Anything still pasted into a page is not covered by the banner. On this route that clean-up is most of the work.

🧩 What the template does

Two things, in this order, every time a page loads:

1. It reads the cookie and tells Tag Manager what the visitor allows — before anything else in your container runs.
2. It loads the banner and hands it whatever wording you chose.

It does not use consentio-loader.min.js and it does not fetch settings files. There are none on this route; the fields are your settings.

The order is the whole point, and it is not something you can change from the Tag Manager screen — it is why the tag has to be on the Consent Initialization trigger. How it works has the sequence step by step, and the reason step 1 cannot be left to step 2.

🍪 Both ways use the same cookie

Consentio stores the answer in one cookie, and the template reads and writes that same cookie by the same rules. So a visitor who answers on a page using the HTML route is remembered on a page using this one, and the other way round.

One thing has to match for that to hold: the version. It is a field on the template and an attribute on the script tag in the other route. Set them differently and the same visitor gets asked twice.

The cookie’s name is always consentio on this route — a Tag Manager template has to name the cookie it reads when it is published, so it cannot be a field. If you changed the name on the other route, change it back before you run both.

How long it lasts and what it covers are fields: Cookie Lifetime (days), 90 unless you change it, and Share the answer across subdomains, off unless your site answers on more than one hostname. The banner writes the cookie on this route too, so they behave exactly as they do on the other one.

The cookie is the full description — what is in it, how long it lasts, and what it looks like when nobody has answered yet.

🔍 Checking it worked

Use Tag Assistant. Preview your container, load a page, and open the very first event in the list. The message about consent has to be there, and it has to be first — before any other tag in the container fires. Present but late is the same as absent.

What it tells Google walks through the screens.

There is also a page on this site with no script tag. It is for checking that both ways of installing agree about the same visitor — a mismatch there is silent, so it is worth looking for on purpose.