Use Message chat in a mobile web experience
Validate the browser widget before planning a native embedding.
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>Native embedding requires device testing
The customer-facing iOS and Android embedding SDKs are not released as supported installation packages. They are separate from Message’s own agent apps. Do not install guessed package names or assume WebView parity with a desktop browser.
Test your actual device
For a web or WebView implementation, test storage persistence, network connections, file selection, microphone permissions where used, keyboard layout and background behavior. A page that renders is not proof of working push notifications or reliable calling.
Identity and private data
The shipped widget does not provide a public identify, signout or userHash login API. Browser continuity and a pre-chat email are not proof of account ownership. Use the connector’s supported customer-verification flow before disclosing private order information.