Three controls can affect the result

The storefront must load the installation correctly, the visit must match the configured domain and page visibility, and any required consent must be handled. A hidden widget is not always a broken script.

Review the actual storefront address

Compare the public URL with the domains allowed in your widget settings. Include the intended hostname when the UI requires it. A preview theme, www hostname, alternate market domain, or staging domain can differ from the main shop address. Add only domains you intend to support.

Test both consent states

Use a fresh private session. Check what happens before consent, after the relevant consent choice, and after it is withdrawn where your integration supports that. Follow the installation and consent controls offered by the widget; do not bypass your site's privacy choices to make an icon appear.

Check page and device rules

Review any include or exclude paths, device rules, and visibility settings. Test a page that should display the widget and one that should not. If it appears on direct load but disappears after navigation, inspect the single-page application or tag-manager setup.

Configure consent and conversation privacyTag Manager and single-page applicationsWidget JavaScript controls and eventsThe widget does not appear or load