Widget troubleshooting

The launcher does not appear

Confirm Widget is on and saved.
Inspect the deployed page and confirm the complete generated snippet is present.
Check whether the style is Hidden or Inline. Inline needs <span data-toado-launcher></span>.
Confirm Show on mobile is enabled at the current width.
Check the console and Network panel for CSP, loader, or blocking errors.
Check whether another fixed overlay covers the launcher.
Disable content blockers for the test and retry.

The status is “On, not detected”

The project is enabled, but Toado has not recorded a recent load using the current key. Open the deployed public URL, confirm the loader succeeds, clear stale caches, and verify the key was updated after rotation. Privacy extensions and network rules can block detection.

The site is detected but reports are rejected

Compare the exact scheme, host, and port with the allowed origin.
Approve staged origins and save.
Confirm the widget remains enabled and the workspace still has Team access.
Check CAPTCHA and network requests for failures.
Check the workspace’s current ticket allowance in Billing.

Copy the generated sources and merge them into the existing response header. Check script-src, connect-src, style-src, and img-src; external icons may need their own origin. Test the effective header, not merely a repository file or meta tag, and clear caches.

The screenshot is blank or incomplete

Cross-origin iframes, video, WebGL, protected content, and some canvas implementations cannot be reproduced reliably by DOM rendering. Isolate the element on a simpler route, check CSP errors, ask the reporter to describe the missing region, attach another image, or use the Chrome extension.

The page changes after enabling Deep capture

Return to Standard and save immediately. Retest login, checkout, challenge, and API flows. Deep capture wraps network functions and can trigger bot-protection or anti-tampering systems.

The wrong project received the report

The destination comes from the project-specific key. Search layouts and tag-manager configuration for an old key and confirm the intended snippet is the only one loaded.

Reports do not include email or identity

Set email collection to Optional or Required, and confirm the reporter supplied it. A visitor signed in to your product is not automatically known to Toado. Team-mode identity requires the supported window.Toado.identify() integration.

This is expected: rotation invalidates the old key immediately. Replace every old snippet, redeploy, and repeat installation detection.