Complete Banner Setup Guide

Sign up for a CookieBeam account at cookiebeam.com/sign-up. The free tier includes everything you need to get started.

Open Banners in the dashboard and create a banner for your website. In the banner designer, the layout labels are Box, stacked; Box, horizontal; Box wide; Cloud; Cloud, horizontal; Bar, stacked; Bar, horizontal. Position is a separate setting: Box and Cloud use a nine-position grid, while Bar uses top or bottom.

Customize the appearance, text, categories, and regional consent behavior. Enable the integrations you use, save your changes, and preview accept, reject, and preference choices.

Publish the saved configuration to production before installing it. Publishing prepares the public Banner ID and loader URL for the live configuration. After later configuration changes, republish to update the live banner. See the quickstart publishing sequence.

Open Install for your banner and copy the production loader script. Add it once near the start of <head> in your shared site template, before Google tags, Google config or event commands, and other managed trackers. Do not add async or defer to the CookieBeam loader. Publish or deploy this site change. Follow the full script installation instructions.

Hardcoded non-essential scripts must remain inert until consent: use type="text/plain", data-category, and data-src for external scripts as explained in Script blocking. Consent signals cannot undo an earlier request.

If you install through Google Tag Manager instead, follow the GTM template instructions and its Consent Initialization trigger. Use one installation method per page; do not add a second direct loader.

<script id="CookieBeam" src="https://cdn.cookiebeam.com/banner/PUBLIC_BANNER_ID/default/loader.js" type="text/javascript"></script>

Replace PUBLIC_BANNER_ID with the public Banner ID from Install, not an internal site or account ID. The copied dashboard snippet already contains the correct ID.

Open a private browsing window with storage cleared. Confirm the published banner appears without console errors. Test accepting and rejecting optional categories, inspect cookies and network requests, and verify that non-essential services stay blocked after rejection. Reopen preferences, withdraw consent, and confirm the stored choice and integration signals change. Check both desktop and mobile. If the banner is missing, verify the published Banner ID, loader URL, and content-security policy.