When the banner doesn’t show, the cause is almost always configuration, connection, or script order. Work through the checks below from top to bottom—you’ll usually fix it in minutes.

1) Confirm the app is active for your domain

• Publish now: Log in to the Cookie Compliance application → Configuration → click Publish Now. Publishing activates the current settings for the selected domain.
• WordPress handshake: In WordPress, open Compliance. On a connected site, click Pull latest settings in the Domain Info card (the classic settings screen has the same button) to refresh the connection; the card shows Protection: Active. If it shows Not Connected, connect the site as in step 2.

If the banner still doesn’t appear, continue with the connection check.

2) Verify the WordPress connection

• In the application, open Integrations and copy your App ID and App Secret Key for this site.
• In WordPress, open Compliance. On a site that isn’t connected yet, open the Protection tab, enter them in the App ID and App Secret Key fields and click Connect Your Site. On a site that is already connected, use the App ID and App Secret Key fields in the Domain Info card and click Save and Connect (classic settings screen: Save Changes).
• Reload the site in a clean browser session (logged out, site data cleared) and check again.

3) Make sure our scripts load first

For autoblocking and signaling to work, the Cookie Compliance code must run before any tag manager, analytics, or ad pixels.

What to look for at the top of <head> (in this order):

1. Inline init block with your configuration (short inline <script>).
2. Loader from //cdn.hu-manity.co (typically the hu-banner loader), followed by companion assets (hu-consent, hu-display, hu-style).
3. Network calls to our endpoints (e.g., //designer-api.hu-manity.co) and the placeholder iframe //cdn.hu-manity.co/empty.html.

If any other script appears above these (GTM, analytics, optimizers), move Cookie Compliance to the very top of <head>, clear caches, and retest.

4) Check caching/optimization plugins

Aggressive JS optimizations can delay, combine, or minify the banner script, which prevents it from initializing in time.

• In your caching plugin (e.g., WP Rocket, W3 Total Cache, WP Super Cache, WP Fastest Cache), turn off and test one by one:
  • Defer / delay JavaScript execution
  • JavaScript aggregation/combination
  • JavaScript minification/compression
• Turn on Caching compatibility in Cookie Compliance for WordPress so the plugin clears your caching plugin’s cache whenever your banner settings change. (The plugin already tells supported optimizers such as WP Rocket, Autoptimize and LiteSpeed Cache not to defer or combine its script, with or without this toggle.)
• If needed, exclude Cookie Compliance scripts from deferring/combining, keep them first in <head>, purge caches (site/CDN), and retest in a clean browser session.

5) Geolocation can hide the banner by design

If Geolocation (Managed or Manual) sets Banner Display to Off for the visitor’s region (e.g., US, EU, UK, CA, BR, Other), the banner won’t show. Open Configuration → Laws, go to the Geolocation section and confirm Banner Display is On for the regions you expect.

6) Logged-in users

Test while logged out. Cookie Compliance for WordPress doesn’t block scripts for users who can manage the banner (administrators with the manage_options capability, by default); other logged-in users, such as customers or members, get blocking as usual. Sites also often run different stacks for members/admins. A clean, anonymous session reflects what real visitors see.