The widget is not visible

Diagnose in order: publishing, domain, access, browser

An invisible widget may result from missing script, token tied to another domain, inactive subscription, consent, CSP, cache or CSS overlap. Editing avatar or recreating assistant does not fix these causes.

Work in a private window with developer tools. Record exact URL and time: they allow matching test with logs and prevent comparing staging to production.

Do not regenerate token immediately
Unnecessary rotation may make diagnosis more confusing. First identify whether browser calls Wavize and what error it receives.

Prove code is actually published

Editor content is not enough: inspect delivered page.

1. Page source

   Search Wavize domain or identifier. If absent, republish theme/plugin/custom code and clear site, CDN and cache.

2. Single installation

   Check script is not present in both plugin and tag manager. Double loading can create inconsistent states.

3. Correct page and theme

   Shopify may have App Embed on unpublished theme; Wix code limited to some pages; WordPress a different visitor cache.

Verify domain, token and subscription

Script may load while service does not authorize display.

1. Final host

   Compare URL after all redirects with token domain: HTTPS, www and subdomain. Do not use staging token on production.

2. Active plan

   Check Subscription. Cancelled, expired, failed payment or blocking quota may hide public widget even with correct code.

3. Complete token

   Recopy block from Assistant > Installation without removing characters, attributes or signature. Do not reconstruct token manually.

Read browser blocks

Open Console and Network, reload and filter Wavize.

• CSP

  Content Security Policy error identifies missing script-src, connect-src, img-src or frame-src. Add only necessary Wavize domains to policy.

• 401 / 403

  Check token, domain, account status and subscription. Attach status and redacted endpoint to support, not full token.

• Blocker or DNS

  Test without extension, on another network and after DNS resolution. Do not bypass local blocking by randomly renaming resources.

• Consent

  Accept configured category then reload. Also test Reject: behaviour should follow policy and explain reporting differences.

Find a present but hidden widget

Inspect DOM when requests succeed but no button is visible.

• Position and z-index

  Cookie banner, cart or menu may cover button. Change left/right or fix competing component layer.

• Mobile viewport

  Look for overflow hidden, zoom and fixed bars. Test on real phone and portrait/landscape rotation.

• Closed campaign vs button

  Proactive bubble may be limited by cooldown without removing main button. Distinguish both before concluding Wavize is absent.

Minimum support package

These elements allow diagnosis without exposing secrets.

• URL and time — Exact public page, timezone and test time.
• Console / network — Message and HTTP status with sensitive parameters hidden.
• Wavize state — Plan, domain, installation method and where script was copied.