Skip to content
Bluestars Docs

Troubleshooting

A checklist for the most common integration questions. When in doubt, open your page with ?bs=1 and watch the console — preview mode logs the resolved segment and every content swap.

The assistant isn’t showing

Section titled “The assistant isn’t showing”
  • Is it live? In Test mode the assistant only renders with ?bs=1. Set the Test/Live switch to Live and publish. See Test vs. Live.
  • Did you publish? Draft changes don’t reach visitors until you click Publiceren.
  • Does a placement match? The assistant mounts at the first matching placement selector. If no selector matches the page, nothing renders. Verify the selector exists in the page’s DOM.
  • Late-rendered target? The widget retries for ~10 s, but if your element appears after that, pick a selector that exists earlier.

Content isn’t being swapped

Section titled “Content isn’t being swapped”
  • First visitor sees the original. Variants are self-warming: visitor #1 triggers a warm-up and sees the original; visitor #2 gets the swap. Reload, or use ?bs=1 to bypass the cache.
  • Is BSR content live? It has its own Test/Live switch, and must be enabled and live for real visitors.
  • Selector match? Confirm your CSS selector actually matches the element(s) you intend on that page.

The segment looks wrong

Section titled “The segment looks wrong”
  • Many visitors resolve to a fallback / unknown segment (no location, non-NL, privacy tooling). That’s expected — see How BSR works.
  • Force a segment for testing with ?bsr-color=<slug> — see URL overrides.

A flash or layout jump when the class applies

Section titled “A flash or layout jump when the class applies”
  • The segment class is added ~200 ms after load. Give elements a neutral default and a CSS transition, and avoid changing layout dimensions (to prevent CLS).

Search returns nothing (on these docs)

Section titled “Search returns nothing (on these docs)”
  • Documentation search is built at deploy time. In local development it may be empty; it works on the deployed site.

The analytics event isn’t firing

Section titled “The analytics event isn’t firing”
  • It’s consent-gated (Google Consent Mode analytics_storage or your consent hook) and off if your tenant disables analytics. It also fires after load, once the segment resolves — trigger on the event name, not on page-ready. See Analytics & GTM.

Still stuck?

Section titled “Still stuck?”

Reach out to Bluestars with your tenant, the page URL, and a screenshot of the ?bs=1 console output — that’s usually enough to pinpoint the issue.