Three Ways to Install the Cookie Banner

You can deploy the GetCookies banner in minutes with three approaches. Pick the one that fits your stack and how much control you need.

Option 1: Simple install (script tag) — fastest

Best for most sites. Drop one script in <head> and you’re done.

When to use: Marketing sites, landing pages, or any stack where you can edit templates.

Steps:

1. Copy your Domain ID from Dashboard → Domains → Widget Configuration.
2. Add this to your site’s <head>:

<!-- GetCookies - Cookie Banner -->
<script src="https://app.getcookies.co/api/v1/widget/loader.js"
        data-domain-id="YOUR_DOMAIN_ID"
        async></script>

1. Publish and test in an incognito window to confirm the banner shows and blocks trackers until consent.

Option 2: Google Tag Manager template — best with Consent Mode

Great if you manage tags in GTM and want built-in Google Consent Mode v2.

When to use: Sites already running GTM; you need strict consent gating for GA/Ads/Meta. Why choose this over others: Gives you centralized control if (and only if) your trackers are in GTM. If you have hard-coded scripts outside GTM, either move them into GTM or use the hybrid approach so everything is covered.

Steps:

1. In GTM, import the GetCookies CMP template (see “GTM Template Installation Guide”).
2. Create a GetCookies tag, set your Domain ID, and set the trigger to Consent Initialization - All Pages.
3. For each tracking tag, require consent types (e.g., analytics_storage, ad_storage).
4. Preview/publish and verify tags stay blocked until consent.

Option 3: Hybrid blocker + GTM — strict control

Use our synchronous blocker plus GTM for maximum pre-consent blocking and granular tagging.

When to use: Regulated sites, heavy ad stacks, or when you must block everything before any tag fires. Why choose this over others: If some scripts are hard-coded outside GTM (e.g., in your theme) and others live inside GTM, the blocker catches the hard-coded ones before they run, while GTM + Consent Mode controls the rest. Use this when you can’t (or don’t want to) migrate all scripts into GTM.

Steps:

1. Add the blocker script first in <head> (before GTM):

<script src="https://app.getcookies.co/api/v1/widget/blocker.js"></script>

1. Load GTM after the blocker; then load the GetCookies loader via GTM (custom HTML) with your Domain ID.
2. Set your GTM GetCookies tag to Consent Initialization - All Pages.
3. Require consent on all marketing/analytics tags; test with GTM Preview to confirm nothing fires before consent.

Quick checklist

• Always use your real Domain ID.
• Test in an incognito window and with GTM Preview if using GTM.
• Ensure trackers are blocked until consent; confirm categories toggle tags correctly.
• Keep your privacy notice aligned with what you load by default.

Troubleshooting

• Banner not showing? Check Domain ID and console errors; ensure the script is in <head>.
• Tags firing before consent (GTM)? Verify trigger is Consent Initialization - All Pages and each tag has consent requirements.
• Meta/ads still firing? Add consent types ad_storage, ad_user_data, ad_personalization to those tags.
• Hybrid flicker? Make sure blocker.js is the very first script in <head>, before GTM.