Troubleshooting installation

If nothing shows up after installing Hubbo, work through this checklist from top to bottom. Most problems are one of the first five items.

1. Is the script loaded?

Open DevTools, then Network, then reload. Filter by embed. You should see GET https://api.hubbo.io/embed?key=... with status 200 and a JavaScript response.

• No request at all: the snippet is not on this page, or it is stripped by a template/CMS. View the page source and search for hubbo-embed-script.
• Request blocked: a Content-Security-Policy or an ad blocker is blocking it. See HTML snippet for CSP values.
• Status 4xx/5xx: copy the snippet again from Settings → Get Embed and compare.
• Script 200 but no bell: the key may be wrong or the project deleted. Hubbo still serves the bundle, but it does not mount the widget shell without a valid project. Confirm the key in Settings → Get Embed. With cookieOnly=1, a missing project returns 404.

2. Is the snippet exactly right?

The script element needs id="hubbo-embed-script", async, type="module" and crossorigin="use-credentials". A missing id or a different spelling of key breaks the widget silently.

3. CORS or cookie errors

If the Console shows an error like “blocked by CORS policy” on api.hubbo.io/graphql:

• Check that the origin in Settings → General is exactly the origin of the page (scheme, host and port).
• Check you are not testing from an origin you did not register, such as a local dev server or a staging domain.
• Make sure no proxy or extension strips cookies or headers.

4. Is there anything to show?

• Notifications must be published and between their start and end dates.
• NPS and surveys must be enabled in their settings.
• A published roadmap is only available on its public URL or through its embed, not automatically on every page.
• Notifications, NPS and surveys: URL rules must match the actual page (whitelist / blacklist). See URL matching.
• If you applied a saved audience, confirm the copied rules still match the page you are testing.
• Device toggles (desktop / mobile / tablet) must include the device you are testing with.
• Timing rules such as show delay, first-time delay and “show again” delay can hide a widget you already saw. Test in a fresh private window.
• A widget can be mounted but covered by your own overlay (modal, banner, sticky header) with a higher z-index. See stacking order.

5. Plan limits

If your page-view allowance for the billing period is used up, usageAllowed is false and the embed does not mount any widgets. Check usage in the admin app and see Plans and limits. NPS responses have their own monthly limit.

6. Still stuck?

Email support@hubbo.io and include: the URL where you expect the widget, your account key, the browser, and any Console or Network errors (a screenshot of the failing request is perfect).