topic Cookie conbanner not showing for EU users, script loads but no UI (debugged extensively)sent in GDPR

Cookie conbanner not showing for EU users, script loads but no UI (debugged extensively)sent

didulaj — Fri, 27 Mar 2026 01:49:49 GMT

Hi everyone,

I’m troubleshooting an issue with the HubSpot cookie consent banner in a GDPR / EU setup, and I’m stuck despite fairly deep debugging.

Here’s how the banner is configured:

Set to EU countries only (Tried with "all countries" as well but the banner still didnt appear)
Published and active
Assigned to the correct connected domain(s)
Targeting all pages (no URL restrictions)
Advanced settings like “Allow all cookies” and “Deactivate cookies” are disabled

Important context:

👉 This issue happens on both:

a HubSpot-hosted subdomain (using HubSpot CMS)
and the main external domain (connected to HubSpot)

So it doesn’t seem isolated to one hosting setup.

Testing conditions:

Testing from an EU IP
Also tested in a brand new browser profile (no prior cookies)

Technical verification:

HubSpot tracking is loading (window._hsq present)
Cookie banner script loads (js.hs-banner.com/.../banner.js)
Location detection call (cf-location) fires correctly
HubSpot banner runtime exists (window._hsp, hsCookieBanner)
No prior consent cookies (__hs_opt_out, etc.)

However:

👉 No cookie banner UI is ever rendered

No banner elements appear in the DOM
It’s not a CSS issue (nothing hidden)
It’s not rendered in an iframe either

Additional context:

Pages include HubSpot forms with legal consent enabled
Other scripts are present (analytics, chat), but none explicitly managing cookie consent
HubSpot support confirmed that form legal consent does not suppress the global banner

So effectively:

👉 The banner script loads and initializes
👉 But HubSpot never injects the banner UI

Given that this happens across both HubSpot-hosted and external pages, it feels like a portal-level configuration or internal condition, rather than a page-level issue.

Has anyone seen this behavior where everything looks correct, but the banner simply never renders for EU-targeted visitors?

Any ideas on what could prevent rendering at this stage?

Thanks

Re: Cookie conbanner not showing for EU users, script loads but no UI (debugged extensively)sent

STierney — Fri, 27 Mar 2026 02:17:49 GMT

Hey @didulaj,

Thanks for posting in the Community - all of this context is extremely helpful to getting you some support!

I'd like to tag in a few Community experts to see what insight they may have for us. @Josh, @RomyFuchs1, and @Alex_Elborn - any thoughts here?

Shane, Senior Community Moderator

Betreff: Cookie conbanner not showing for EU users, script loads but no UI (debugged extensively)sen

RomyFuchs1 — Fri, 27 Mar 2026 07:54:30 GMT

Hi @didulaj

Yes — if banner.js loads, geo detection runs, and there are no prior consent cookies, but HubSpot never injects any banner DOM at all, that usually points to a rule/configuration mismatch rather than a frontend rendering bug. Based on the documentation and the fact that it happens on both HubSpot-hosted and external pages, I’d focus on these causes first:

The exact hostname doesn’t match the domain configured for the banner on the external site. For external domains, HubSpot requires the domain/subdomain to be added in Privacy & Consent > Cookies , and if the root redirects to www, you must add www explicitly rather than only the apex domain. This is a common reason the script loads but no UI is injected.
A path rule mismatch. Even if you believe it targets all pages, HubSpot’s docs explicitly call out that if the external page URL does not match the configured domain/path rules, the banner won’t display.
Country targeting logic is excluding the visit. HubSpot determines display by the visitor IP’s detected country, and if specific countries are selected, VPN/proxy/location tooling can prevent display. Since you already tested “all countries,” this is less likely now, but it remains one of HubSpot’s documented suppression conditions.
The banner may be configured in a way that intentionally suppresses the UI. If either “Allow all cookies” or “Deactivate cookies” is enabled for that banner, HubSpot says the banner will not display. You said both are disabled, which is good — but I would still re-open the exact live banner and confirm the published version, because this setting is one of the few documented conditions where runtime exists but no banner appears.
A third-party consent/CMP/custom script is interfering before render. HubSpot documentation notes that external consent tools or script blockers can prevent HubSpot scripts/widgets from behaving normally, and for third-party cookie banners HubSpot often requires a custom integration via the Cookie Banner API or coordinated JS/CSS behavior. Even if no tool is “visibly” managing consent, a tag-manager rule or CMP bootstrap can still suppress banner initialization.

What makes your case unusual

Because it fails on both HubSpot CMS and the external connected domain, I agree with your conclusion that this is unlikely to be a simple page-level CSS/DOM issue.

My best-priority checks

I’d validate these in this order:

Create a brand-new test banner in Privacy & Consent > Cookies with:
- no country restriction
- no path restriction
- no advanced suppression options
- a clearly unique label/text
  If that renders, the issue is in the existing banner rule set, not the portal.
Re-check external domain registration exactly as served in the browser
- test example.com vs www.example.com
- test language subdomains separately
- test any redirect target domain, not just the originally entered one
Review whether multiple banners/rules exist for overlapping domains/paths. The docs emphasize domain/path targeting, and overlapping policies can create behavior that looks like “nothing renders” if the active rule is not the one you think.
Temporarily disable all non-HubSpot consent-related scripts via GTM / CMP / site-wide JS and retest. HubSpot explicitly documents that third-party consent tooling may require custom handling.
Check the banner type / consent model
- if the policy is effectively notification-style or otherwise not requiring opt-in, behavior may differ from what you expect

Regards