Widget configuration
Use supported script attributes and dashboard settings for the installed widget.
Use the site embed identifier
Copy your current snippet from https://app.message.com/settings/chats/installation. Replace YOUR_EMBED_ID with the data-site-id value from that snippet. It is the site’s public embed identifier, not the workspace database ID or a secret API key.
Install once in the persistent page or application shell. The bundle renders its own launcher and panel inside Shadow DOM.
<script async src="https://app.message.com/widget.js"
data-site-id="YOUR_EMBED_ID"></script>Supported script attributes
data-site-id is required. data-server optionally overrides the server origin; omit it for the standard hosted installation. data-ga4-id supplies a GA4 measurement ID for consent-controlled event forwarding.
Appearance attributes such as data-color, data-position and data-no-launcher are not supported by the current bundle. Extra attributes do not override the dashboard configuration.
Configure the selected site
The data-site-id value selects the site. It is not derived by matching the page hostname to a workspace ID. Use https://app.message.com/settings/chats/customization for appearance, https://app.message.com/settings/chats/welcome for welcome content and https://app.message.com/settings/chats/pre-chat for fields.
Verify the published installation
Test the published page in a separate browser session. Confirm widget.js loads, the launcher opens, a visitor message reaches Inbox and an agent reply returns. Test with your site’s actual content security policy, consent controls and mobile layout.
The script connects to its own origin by default. With the standard snippet, allow the relevant script and HTTPS/WSS requests to app.message.com. Check image, media and injected-style requirements separately. Do not put an agent JWT or integration secret in the page.