Choose a route
There are two ways to install Consentio and they do not do the same things. This page is the comparison; each route has its own page with the steps.
The container covers only what it loads. A script pasted into the page is outside consent on either
route until you mark it, and marking works on both. What decides between the two is where you can make a
change: the <head> of every page, or the container.
🧭 Side by side
| Put it in your HTML | Use Google Tag Manager | |
|---|---|---|
| What you add | one <script> tag in <head>, and two files you host |
one template in your container, on one trigger |
| What tells Google what the visitor allows | the script tag, blocking, before anything is fetched | the template, on the Consent Initialization trigger, before it loads anything |
| What it costs the first paint | one blocking file, around 5.4 KB, before the page paints — what it weighs | nothing in the page; the container’s own cost |
| What it can stop | every script you mark with type="text/plain" data-consentio and every iframe you mark with data-consentio data-src, held until its category is granted — and nothing you do not mark. Hold a script until consent |
tags in that container, through its own consent settings, and the same marked scripts and iframes — the banner releases them on both routes. A script pasted into the page and not marked is outside consent |
| Where the words come from | the built-in English; a language file at any URL — one of your own, or a published pack; or data-language="el" for the published pack at the CDN |
the built-in English; the same file in a variable; or a published pack the tag loads from the CDN |
| Where the cookie table comes from | a file at any URL | the same file in a variable, or nothing |
| Where the settings come from | a JSON file the script tag fetches | the same file in a variable, or nothing |
| What you edit to change a word | a file on your site | the pack in a variable, then publish the container |
| What can rename the cookie | data-cookie-name on the tag |
nothing — it is consentio |
| Where the version is set | data-version on the tag |
version in the settings file |
| What happens when the CDN is down | nothing, unless you serve the files from one. A pack chosen with data-language comes from the CDN, and if it does not load the banner is in English |
the template still tells Google what the visitor allows; the banner does not load |
| Who is told a new version exists | nobody — your site runs the files you put there | nobody — a container runs whatever .tpl was last imported, with the banner version it pins |
🚀 Put it in your HTML
For a site whose <head> you can edit. The answer is on the page before any tag manager reads it, and a
script you mark waits for consent. Four steps.
🏷️ Use Google Tag Manager
For a site where everything already runs through one container. Nothing is pasted into the HTML and nothing is hosted by you; what the container does not load, the banner does not reach. Four steps.
🚫 Pick one
Install both and the tag stands down on any page where the script tag ran, and says so on the console. A page with the template and no script tag runs the template. Both read and write the same cookie, so a visitor who answered on one is remembered on the other — as long as the version matches on both.
The two routes do not share configuration. A site that runs both has two copies of each file — the ones
the script tag fetches, and the variables in the container — and keeps them equal by hand, version
above all: a version that differs is an answer honoured on one route and discarded on the other. This
site runs both, on one page, and does exactly that.