Izini with Google Tag Manager
Load the Izini consent banner from Google Tag Manager with the Izini tag template, set Google Consent Mode defaults, and have Google tags follow each visitor's choice.
About 10 minutes
If your site's tags are managed in Google Tag Manager, the Izini Consent Banner tag template adds the banner from there, with no code in your pages. It also sets Google Consent Mode for you.
You need: an Izini account with a project for the website, and permission to edit and publish your Tag Manager container.
What the tag does
- Sets the Consent Mode defaults on the Consent Initialization trigger: advertising and analytics denied, functional and security granted, out of the box. You can change each one in the tag. Google tags wait up to 500 milliseconds for the banner before sending data.
- Loads your banner from
cdn.izini.ngfor your project. Its wording, categories, languages and colours stay in Izini. - Passes each choice to Google. When a visitor accepts or refuses, the tag updates Google's consent state with their choice, so Google tags in the container follow it.
1. Add the template to your container
Download the template from Consent > Installation in Izini (the GTM and Consent Mode tab). In Tag Manager, go to Templates > Tag Templates > New, open the ⋮ menu, choose Import, pick the file, and Save.
When Izini updates the template, download it again and import it over the old one the same way.
2. Create the tag
- Go to Tags > New, choose Tag Configuration, and pick Izini Consent Banner.
- Paste your project code from Consent > Installation in Izini.
- Keep the Consent Mode defaults, or change them for your site.
- Under Triggering, choose Consent Initialization - All Pages: Google's guidance for consent templates is to set the default consent states on this trigger.
- Save the tag.
3. Remove any pasted Izini script
If the Izini script tag was pasted into your site's pages, or your site uses the Izini WordPress plugin, use only one of them. Two copies would load the banner twice.
4. Publish and check
Preview the container, then Submit to publish it. Open your site in a private window: the banner should appear. Then, in Izini, run the health check under Consent > Installation.
Options
Under Advanced in the tag:
- Redact ads data while ad_storage is denied sets Google's
ads_data_redaction. - Pass ad click information through URLs sets Google's
url_passthrough.
Both are off unless you switch them on. Google's own documentation explains what each does.
What the tag sends
The tag loads the banner from Izini. The banner then records each visitor's choice with Izini: a random ID kept in the visitor's browser, the choices, the time, the language, the browser family and operating system, and the country and region worked out from the connection. No name or email address. The tag itself stores nothing in your container but your project code, which is public: it appears in your pages anyway.
More guides
- Keep consent records in your own databaseReceive each consent choice with a signed webhook and store it next to your own users, so your systems can check consent without calling Izini.
- Send subject requests from your backendLet signed-in users ask to see, correct or delete their data from inside your app, and open the case in Izini for your DPO.
- Stop a release until its privacy review is approvedAdd one step to your CI/CD pipeline that fails unless the release passed its privacy-by-design review in Izini.
- Send Izini events to Slack, Teams, Jira or Google SheetsReady-made n8n workflows and Make scenarios that check each webhook is really from Izini, then post it to a channel, open a Jira issue or add a row to a sheet. No code.
- Izini on WordPress and WooCommerceAdd the consent banner to a WordPress site with the Izini plugin, hold back tracking scripts until visitors agree, and see consent totals and cookie scans in wp-admin.