Guides
Getting started
Banner & appearance
Scanning & cookies
Consent & compliance
Records & privacy

Quickstart: a live banner in 5 minutes

AdminUpdated Sep 15, 2026

Quickstart: a live banner in 5 minutes

This is the fastest path from a fresh sign-in to a real, blocking consent banner on your site. Work through the checklist top to bottom — each step takes under a minute. For the "why" behind any of these, see the Overview; for deeper detail on any single step, follow the linked guide.

The checklist

1. Confirm your organization. Cookie Munch creates a default organization the moment you sign in — you don't need to set one up. If you belong to more than one, check the organization switcher at the top of the sidebar and make sure the right one is active.

2. Add a property. Go to Properties in the sidebar → Add property.

  • [ ] Enter the Domain (e.g. acme.com) — no https:// needed, Cookie Munch normalizes it.

  • [ ] Pick a Platform: Web, iOS, Android, AMP, or Other.

  • [ ] Click Add.

You'll see a new property card with a generated site ID (cbid) like acme-com-9f3k.

3. Copy the install snippet. On the property card, click Install. Copy the <script> tag shown — it's already filled in with your cbid. Don't retype it by hand; copy it as generated (some setups include an extra data-api attribute you'd otherwise miss). Full attribute reference: Installing the script.

4. Paste it on your site. Put the tag as early as possible in <head>, before any analytics, ads, or embed scripts. This ordering is what makes prior-blocking actually block things — a tracker that loads before the tag runs is invisible to it.

5. Verify domain ownership. Back on the property card, click Verify if it's still showing Pending. Pick whichever of DNS (TXT record), meta tag, or file upload fits how you manage the site, follow the on-screen instructions, then click Verify now. (If you've already installed the script and it has beaconed home from your domain, this step may already be satisfied automatically.)

6. Check it's live. Open your site in an incognito/private window. You should see the banner render on first load. Make a choice, reload, and confirm it's remembered instead of re-prompting.

7. (Optional) Adjust the banner. A brand-new org starts with a polished default banner, so step 6 already shows something presentable. If you want to change colors, copy, or categories, open Banner Studio from the sidebar, edit, and click Publish — changes go live to every property using that design within seconds.

You're live

That's it — your site now shows a compliant banner and blocks third-party scripts until visitors consent. From here:

If the banner doesn't show up

  • Open dev tools and confirm the <script> tag is actually present in the rendered HTML (not stripped by a builder or CSP).

  • Make sure you copied the snippet after adding the property — an old/wrong cbid won't match any config.

  • Check you pasted it in <head>, not buried after other scripts.

  • Give it a few seconds — the runtime script polls its config on load, and CDN caches briefly.

If it still doesn't appear, Installing the script has a fuller troubleshooting checklist.

Was this page helpful?