Install Consentics with Google Tag Manager

If your site already runs Google Tag Manager, use GTM to add Consentics instead of pasting the direct snippet into your site's code.

You'll need edit access to your GTM container, and a GTM container already installed and firing on every page you want Consentics to cover. Install one way, not both, or you risk double-counting: adding the direct snippet as well as the GTM tag.

Go to your Consentics install page (Account, Properties, your site, Install) and copy the GTM Custom HTML tag script from the "Install with Google Tag Manager" panel. See the install basics for why you should always copy your exact script from there rather than reusing an example.

1. In GTM, go to Tags, then New. Click Tag Configuration and choose Custom HTML.
2. Paste the script from your Consentics install page into the tag's HTML field.
3. Set the trigger to All Pages (or Initialisation - All Pages).
4. Save the tag, then Submit and Publish your container.
5. Go back to your Consentics install page and check the waiting-for-first-event status. It turns green once Consentics receives your first page view. If it's still waiting after a few minutes, confirm the container was published, not just saved, and clear any cache in front of your site.

If you'd rather not build the tag by hand, your Consentics install page also offers a Download GTM container file link, which saves a file named consentics-gtm-<your-site-id>.json.

1. Download the container file from your Consentics install page.
2. In GTM, open Admin, then Import Container.
3. Click Choose container file and select the file you downloaded.
4. For the workspace, choose New. For the import option, choose Merge, not Overwrite: Overwrite removes every existing tag, trigger and variable in your container. GTM then asks how to handle conflicting tags, triggers and variables; that only matters if your container already has items with the same names as the imported ones.
5. Click Continue to review the changes, then Confirm. The import adds one tag named "Consentics analytics tag", firing on All Pages.
6. Review the new workspace, then Submit and Publish your container.
7. Go back to your Consentics install page and check the waiting-for-first-event status, as in step 5 above.

The consent banner and Google Consent Mode v2 are built into this tag. No extra GTM consent configuration is needed.

Consentics also works alongside Google Analytics 4 and Google Ads conversion tracking through Consent Mode v2, and there's one Google-specific gap we're direct about. See Google compatibility for what works today and what doesn't yet.

A dedicated Consentics template for the GTM Community Template Gallery is in development, so GTM users will eventually be able to add Consentics the way they already add other consent tools, rather than using the Custom HTML tag above. See Google compatibility for the current status.

Do I still need to paste the direct snippet as well? No. Install one way, not both, or you risk double-counting. If you've already installed the direct snippet, remove it before adding the GTM tag.

Which trigger should I use? All Pages, or Initialisation - All Pages if your container has one. Either fires the tag on every page load, which is what Consentics needs.

Can I add my own data-icva-* attributes to the script? No. Copy the script exactly as your Consentics install page provides it. It already carries everything the tag needs for your site.