Iframe embedding is available on Premium and Enterprise plans.
- Private embedding — for internal users with Cube accounts
- Signed embedding — for external/customer-facing applications using server-generated sessions
Embed with private embedding
The embed URL for Analytics Chat is always the same:Embed with signed embedding
To embed Analytics Chat for external/customer-facing applications, generate a session on your backend and pass the session ID into the iframe:Voice input
Users can dictate messages in the embedded chat when the iframe’sallow attribute includes microphone,
as in the examples above. Without it, the chat shows no dictation control. The
host page’s own Permissions-Policy header, and any parent iframe, must allow
microphone too. The browser still asks the user for microphone access the
first time.
Personalize chat with user attributes
When using signed embedding, you can pass user attributes during session generation to personalize chat responses for each user — for example, scoping answers to a specific region, department, or tenant.Customize the chat
Add these query parameters to the embed URL to hide parts of the chat UI:
Only the exact literal string
false hides a control, the same rule every other
embed parameter follows — see Show and hide
features.
These were originally
hideNewChat=1, hideChatInput=1, and hideHistory=1.
Those spellings still work, with both 1 and true, so existing embed URLs keep
working — but they are no longer the documented form, and the show… parameter
wins if you send both.settings.allowAi).
By default, the chat header shows a Chat history button that lists the
user’s past conversations (matched by externalId under signed embedding) so
they can resume one instead of always starting fresh.
To deep-link directly into a specific past conversation, pass its ID as
chatId alongside sessionId on the short embed URL: