Install with Google Tag Manager
Find CookieBeam in the Community Template Gallery, configure your Banner ID, and publish the consent tag.
Use the approved CookieBeam Consent Mode template from the Google Tag Manager Community Template Gallery in your GTM web container.
Add the template from the gallery
- Open the correct GTM web container and workspace.
- In the left navigation, select Templates.
- Under Tag Templates, select Search Gallery and search for CookieBeam.
- Select CookieBeam Consent Mode, review its requested permissions, and click Add to workspace.
You can also view CookieBeam in the Community Template Gallery. Review future template updates through GTM's normal template update flow.
Configure the tag
- Go to Tags → New → Tag Configuration.
- Choose CookieBeam Consent Mode from your custom templates.
- Paste the public Banner ID shown on the banner's CookieBeam installation page.
- Select Consent Initialization – All Pages as the trigger.
- Save the tag.
Configure the consent settings for each downstream tag. Consent Mode can allow cookieless requests while consent is denied; it does not automatically block every tag. Hardcoded non-essential scripts outside GTM may still need inert markup. See script blocking.
Preview and publish
Use GTM Preview before publishing. Test a fresh visitor session, acceptance, rejection, and withdrawal. Check the consent state reported for downstream tags and the requests they send. Then submit and publish the container version.
Alternative: import a container file
If you cannot use the gallery, the CookieBeam installation page offers a web container JSON download with a prefilled consent tag. Use Admin → Import Container, choose the file and workspace, then select Merge and review the import preview. Verify the banner ID and Consent Initialization – All Pages trigger before publishing.
Use either the gallery setup or this fallback to avoid duplicate consent tags. The JSON download is a container file, so it belongs in Import Container, not the template editor's import menu. Manual imports need to be updated when a new template version is released.