D-ID AI Widget blurs and freezes when embedded in Wix Custom Code

Ask the community
, ,
1

I’m having trouble with An external AI avatar widget that renders on the screen but instantly gets blurred/blocked and stops functioning.

Working in Wix Editor (using the Settings > Custom Code tool).

Site link https://www.automatechexpo.com/

What I’m trying to do I am trying to embed a floating AI agent widget from D-ID (using a native <script type="module"> snippet provided by their platform). The goal is to have the interactive avatar load smoothly at the bottom-right corner of the website.

What I’ve tried so far

  • Placed the raw HTML script inside Settings > Custom Code at BodyEnd and categorized it as Functional.

  • Attempted to inject it via Dev Mode (Velo) using alternative DOM manipulation methods, but Wix blocks direct document interaction, and the Velo frontend API threw TypeError: insertCustomCode is not a function. (Dev Mode is now completely turned OFF to avoid conflicts).

  • Forced a server-side cache clear on Wix by publishing a minor text change.

  • Tested the live site on Google Chrome, using Incognito Mode, across multiple physical machines and completely different network connections (cellular data) to rule out local browser/ISP caching.

  • Double-checked the D-ID dashboard to ensure the production domain (https://www.automatechexpo.com) is correctly whitelisted on their end.

Extra context The script successfully injects and initiates because the widget UI physically appears on the page. However, the stream instantly freezes and goes blurry. It feels like Wix’s container for Custom Code might be interfering with scripts of type="module", or there is a Content Security Policy (CSP) / HTTP header restriction on the domain level blocking the incoming real-time streaming data. Any insights on how Wix handles module scripts or streaming data via Custom Code would be highly appreciated!

2

The important clue is that the widget appears first, then blurs/freezes. That usually means the base script has loaded, but one of the follow-up requests is failing. I would check the browser DevTools Console and Network tabs on the live site and look specifically for blocked requests, CORS errors, CSP errors, iframe permission errors, WebRTC/media errors, or failed requests to D-ID domains.