Docs menu

Getting started

From zero to a working CMP in ~5 minutes: account, domain, first scan, banner configuration, installation, consent test and Google Consent Mode verification.

From zero to a working CMP

This guide takes you from creating an account to a verified consent banner with Google Consent Mode v2. Expected time: about 5 minutes (not counting cache propagation on your site).

Step 1 — Create an account

Sign up at app.cookiehug.com — all you need is an e-mail address and a password (you can also sign in with Google, Apple or Facebook). Panel sign-in is confirmed with a one-time code sent by e-mail.

The Free plan does not require a payment card.

Step 2 — Add your website

In the panel, add the domain the banner should run on. Each domain gets its own license key — you will find it in the domain details. You will need it in the installation step.

A subdomain (e.g. shop.yourdomain.com) counts as a separate domain for plan limits; the number of subpages within a website is unlimited.

Step 3 — Run your first scan

Run a cookie scan from the domain panel. The scanner visits your website with a real browser, collects cookies and third-party scripts, and classifies them into consent categories (necessary / analytics / marketing / preferences). The results feed the cookie declaration in your banner.

More: Cookie scanner.

Step 4 — Configure the consent banner

In the domain settings, pick the banner look (ready-made style templates or your own colors), languages and copy. The default configuration meets Google Consent Mode v2 requirements: signals start as denied and the banner requires an affirmative decision from the visitor.

More: Banner and cookie declaration.

Step 5 — Install CookieHug

Choose one of three installation paths:

  • JavaScript snippet — paste one line into your site's <head>: instructions,
  • WordPress plugin — installation without touching code: instructions,
  • Google Tag Manager template — if you manage tags in GTM: instructions.

Whichever path you choose, the snippet should load before any other scripts — that way blocking works from the very first visit.

Step 6 — Test consent

Open your website in an incognito window:

  • the banner should appear on the first visit,
  • before a decision, analytics and marketing scripts must not load,
  • after acceptance the scripts start and the choice is remembered (first-party cookie CookieHugConsent),
  • after rejection, necessary scripts keep working and the rest stays blocked.

You will see the decision record in the panel — see Consent logs.

Step 7 — Verify Google Consent Mode

If you use Google services (GA4, Google Ads, GTM), check in Tag Assistant that consent signals are set correctly: first denied as the default, then granted as an update after acceptance.

Full checklist: Verify Consent Mode.