Verify the Cookie Compliance banner is actually blocking

Skill View raw markdown (for agents)

A banner that is merely visible has not been verified. Verification means proving trackers do not run before the visitor consents, in a region whose rule requires consent first (GDPR and UK PECR by default. In Managed mode on the New banner, with region detection on (Professional), it also holds in further places from our country research, such as Brazil and Quebec; every other place is opt-out by default. On the New banner with region detection on, a visitor whose location is not known yet is asked first), then proving they do run once the visitor allows them.

0. Status check first #

Open https://designer-api.hu-manity.co/api/designer/user-design-live/?AppID=YOUR_APP_ID (public, no sign-in; it is the same request the banner makes from each visitor's browser).

A 200 only means the configuration is live. It is not a pass of any check below and never replaces them, including when you cannot run a browser.

If the script path does not match WidgetVersion, first find out how the banner was installed, then fix it that way. A WordPress site with the Cookie Compliance plugin active (for example wp-content/plugins/cookie-notice in the code, or the plugin listed in wp-admin) uses the plugin route. Anything else is a pasted snippet: by hand, from the dashboard, or from install.getSnippet. If unsure, ask the person once.

How it was installed Fix
WordPress plugin Update the plugin to the current version, run Pull latest settings, then purge the page cache (the plugin offers this in a notice when the engine changes; see "Banner engine" in the WordPress cookbook). Otherwise a cached page keeps the old script path. Never add the manual snippet to a site that runs the plugin.
Pasted snippet, MCP connected Call install.getSnippet again and replace the snippet on every page.
Pasted snippet, no MCP After publishing, copy the snippet again from Integrations → Manual Integration and replace it on every page.

1. Browser checks #

Use a fresh browser profile or private window. If you drive a browser with automation, hide navigator.webdriver and use a normal desktop user agent, because the widget deliberately doesn't run for automated or headless browsers, and you'd wrongly conclude the banner is missing.

Location matters: with region rules on, the visitor's region decides whether the banner shows and whether it blocks. Test from a region under the strictest rule (for example the EU), or confirm region rules are off. Otherwise a missing banner may be correct, and a pass may not hold for EU visitors. In a region whose rule does not require consent first, trackers running before a choice can be correct; confirm the region's rule before treating a pass or a failure as final.

On the New banner with region detection on, a visitor whose location is not known yet is asked first, so a first load that is still waiting for the location answer holds trackers whatever the region. For a site on the New banner that uses the Manual method, a place the owner set to Opt-out or No banner behaves differently from the default; account.explainRegion (AppID plus a place such as DE or US-CA) says what a visitor from that place gets.

# Check Pass
1 Screenshot the page on first load (desktop and mobile width) The banner is visible. No badge reading "Hu-manity PREVIEW — not active consent management".
2 Page source The snippet is the first script in <head>, without async/defer, on the homepage and an inner page. No previewMode, forceShow or cnPreview anywhere: these are preview-only keys, and a page that carries one can stop the visitor's choice being saved. For a v2 app, the script src contains /v2/hu-banner.min.js.
3 Before any click No tracking cookies (for example _ga, _gcl_au, _fbp). A tracker's script file in the HTML may still download (the browser starts fetching <script src> files it finds ahead in the page); it runs only after the visitor allows it. Confirm with typeof google_tag_manager === 'undefined' and typeof fbq === 'undefined' || !fbq.getState, both true. Repeat this check on an inner page in a fresh profile.
4 Allow everything: choose the most permissive option (for example the highest level). On a Classic banner, then click Save. The New banner has no Save button: each choice saves on click, and if the app has the Reloading setting on, the page reloads once after the choice Trackers run at once, with no reload needed: their cookies appear and data hits go out. After a reload the banner stays closed and a hu-consent cookie exists.

Consent Mode exception to check 3: when Google, Meta or Microsoft Consent Mode is on, their loader scripts (for example googletagmanager.com/gtag/js, connect.facebook.net) load before consent by design, and they are sent a "denied" signal. With Google Consent Mode, cookieless pings to google-analytics.com carrying the denied state are expected too. That is correct; don't "fix" it. Judge check 3 by cookies only.

Lowering a choice (optional): after check 4, reopen the banner with the Update consent icon, choose the lowest level (for example Private), and save it (Classic: click Save; New: the click saves). Pass: the stored choice drops to the essential level and trackers stay held from the next page load. Cookies set earlier (for example _ga) stay unless the app has Reset Cookies on (Professional, off by default). Withdrawing or lowering consent doesn't stop scripts that already ran until the page reloads. That is how the banner behaves. With Reset Cookies on, every recorded choice (raising, lowering, closing the banner on a first visit, and on the New banner an automatic Global Privacy Control record) deletes every cookie the page can read except the banner's own cookies, including the site's own login and cart cookies; HttpOnly cookies are not touched. Do not switch Reset Cookies on just to make this check pass: whether to use it is the site owner's decision. If they do, turn on Reloading as well, so the page reloads after the choice and trackers that are now held do not start again; a tracker already running can still set cookies until the reload. Verified in a real browser on a test page, on both banners (2026-11-07): the stored choice drops to the essential level, earlier cookies stay with Reset Cookies off, and with it on they are all removed except the banner's own.

Blocked iframes: a blocked iframe shows a notice in its place with an Accept button, and Accept allows the whole category, not just that embed. Not yet browser-verified.

Banner or revoke icon missing? Open the browser console. With or without debug mode, the widget prints short status lines saying what it showed and why, for example [hu] status banner-hidden:gpc (the browser sends Global Privacy Control, so the banner is correctly not shown). That is expected behaviour, not a broken install: re-test in a fresh profile without Global Privacy Control. On the New banner, when Banner display when GPC is honored is left at its default (passive), a small notice saying the signal was honoured shows once, pinned to the bottom of the screen, on the page view where the signal saved the choice. It closes on its X, on Esc while it has keyboard focus, or after 8 seconds (the count stops while you hover over or focus it, and starts again from 8 seconds when you move away); until then the console shows [hu] status revoke-off:gpc-notice and the revoke icon is hidden. Later pages show no notice, only the revoke icon if it is switched on. Not yet browser-verified. [hu] status revoke-off:no-choice-yet is normal on a first visit.

If you can't run a browser, give the owner this table. A row counts only when the owner checks it now against its Pass column and tells you what they saw; a bare "it works" is not a confirmation. Report those rows as "owner-confirmed, not verified by me". They do not make the install verified.

Report #

Tell the owner: the status check result and its WidgetVersion, the result of each check (with screenshots if taken, and which rows are owner-confirmed), the region you tested from, which banner engine URL was installed (v1 root path vs /v2/), and that design, wording and regions are managed in the Cookie Compliance dashboard, not in the page.