Web Embed: Iframe & Widget
Core Studio WorkflowPublish your assistant in DigitGPT Studio and deploy it on your website using either a responsive inline iframe or a floating JavaScript widget protected by domain allowlisting.
Prepare and authorize your embed
- Save your assistant’s instructions, avatar, voice and attached knowledge groups.
- Set the assistant status to Published in the studio.
- In Embed settings, register the exact website hostnames allowed to load the player.
- Select Inline Iframe or Floating Widget, choose your layout preferences and copy the generated snippet.
- Deploy the snippet on your HTTPS page and run a live test to confirm domain verification and audio permissions.
Inline iframe integration
Replace the organization and assistant placeholders with the identifiers generated in your studio Embed tab. Keep a standard referrer policy enabled so DigitGPT can verify the host domain.
HTML — inline player
<iframe
src="https://www.digitgpt.cloud/embed/YOUR_ORG_ID/YOUR_HUMAN_ID"
title="Talk with our AI assistant"
width="100%" height="620"
allow="microphone; autoplay; camera"
referrerpolicy="strict-origin-when-cross-origin"
loading="lazy"
style="border:0;border-radius:16px;max-width:480px"
></iframe>Floating JavaScript widget
The lightweight widget script can render inline or as a floating launcher pinned to the bottom-right, bottom-left, top-right or top-left of the viewport. Closing the floating panel cleanly terminates the active conversation.
HTML — floating widget
<script
src="https://www.digitgpt.cloud/widget.js"
data-org-id="YOUR_ORG_ID"
data-human-id="YOUR_HUMAN_ID"
data-mode="floating"
data-position="bottom-right"
data-initial-state="minimized"
data-cta="Talk with our AI assistant"
defer
></script>Troubleshooting embed startup
- Confirm that the assistant is published, has a valid avatar and voice, and belongs to a workspace with available monthly quota.
- Verify that your website’s Permissions-Policy header and iframe allow attribute include microphone and autoplay.
- Ensure your page does not strip the HTTP Referer header (avoid referrerpolicy="no-referrer").