Try it on this page

The banner on this site is not a screenshot. This page loads consentio-loader.min.js as a blocking script in <head> — route 1, the same markup the documentation gives you. On the published site every other page gets the banner from a Tag Manager container instead — route 2 — and the container page is where to look at that one.

It also runs with consentRequired: true, which is the hardest setting to get right: a full-screen blocking overlay that a visitor has to answer before they can reach the page. If you have already answered, clear the cookie below and it comes back.

🍪 Your answer, and how to change it

Reading…

🖼️ A held embed

An OpenStreetMap frame with its address on data-src, marked preferences_functionality. It is empty until that category is granted and loads in place when it is — on this visit, or as the page loads if you granted it on an earlier one; the caption under it says which — hold a script until consent is the page for it. Revoking leaves it loaded until the next page load.

Empty until preferences_functionality is granted.

🔍 What to look at

The bar and the settings modal are rendered inside a closed shadow root, so nothing on this page can style them and nothing on this page leaks into them.
Tab through it with the mouse untouched. With consentRequired: true the overlay is a dialog: Tab stays inside it, and Escape from the settings goes back to the bar.
The cookie is named consentio here, because this site does not rename it. The readout above is its value, decoded — the cookie explains what is in it.
window.ConsentioDefault in the console holds what the very first message to Google was built from, before anything had been downloaded.
Open the settings panel above is an ordinary page button calling window.ConsentioInstance.openSettings() — the same link a site adds to its footer. It works whether or not you have answered, and pressing it twice leaves one panel with focus where you put it.

🏷️ The other route, on the same site

Try it through a tag manager is the page that never has the script tag, whatever the build. It is where the two ways of installing are checked against each other: answer the banner on this page, then open that one and see whether it agrees about you.

📡 Watching what it sends

Open the console and read window.dataLayer before and after you answer. The first entry is the consent default — what you were allowed before answering. Answering adds a consent update with all seven permissions named again. What it tells Google sets out both.

              document.addEventListener('consentio:consent-update', (e) => console.log(e.detail));

            