Widget not showing
If the Chatevo chat bubble does not appear on your site, work through these checks in order.
Checklist
Section titled “Checklist”| # | Check | How to verify |
|---|---|---|
| 1 | Script tag present | View page source — search for widget.chatevo.ai/chat.js |
| 2 | Correct deployment ID | Matches Deployments → Embed exactly |
| 3 | Script not blocked | Browser devtools → Network — chat.js returns 200 |
| 4 | Domain allowlisted | Origin matches allowed domains |
| 5 | No JS errors | DevTools → Console — no Chatevo errors |
| 6 | Deployment active | Status is Active in dashboard, not archived |
Embed code
Section titled “Embed code”Confirm your snippet matches:
<script src="https://widget.chatevo.ai/chat.js" data-deployment-id="YOUR_DEPLOYMENT_ID" data-api-base="https://api.chatevo.ai" async></script>Place before </body>. A single instance per page is sufficient.
Network debugging
Section titled “Network debugging”Open DevTools → Network and filter by chatevo:
| Request | Expected | If failing |
|---|---|---|
chat.js | 200, < 500 ms | Ad blocker or CSP blocking script |
widget/config | 200 JSON | Domain not allowed |
widget/messages | 200 or SSE stream | Rate limit or auth issue |
Content Security Policy
Section titled “Content Security Policy”Add to your CSP if you restrict scripts:
script-src https://widget.chatevo.ai;connect-src https://api.chatevo.ai;Common causes
Section titled “Common causes”| Symptom | Cause | Fix |
|---|---|---|
| Nothing in DOM | Script not injected | Add embed to theme footer / GTM |
| Flash then disappear | 403 on config | Add domain to allowlist |
| Bubble behind content | CSS z-index conflict | Chatevo uses z-index: 2147483000; check transform on parents |
| Works locally, not prod | localhost only on staging deployment | Add production domain |
| Slow load (> 2s) | Heavy page JS | Defer other scripts; load Chatevo with async |
CMS-specific guides
Section titled “CMS-specific guides”| Platform | Guide |
|---|---|
| WordPress | WordPress |
| Webflow | Webflow |
Still stuck?
Section titled “Still stuck?”Gather before contacting support:
- Page URL
- Deployment ID
- Screenshot of Network tab (
chat.js+configrequests) - Console errors