Skip to main content
Iframe embedding is available on Premium and Enterprise plans.
Embed Analytics Chat into your application using an iframe. Let your users ask questions in plain language and get trusted answers powered by your semantic layer — without leaving your product. Analytics Chat can be embedded with either authentication mode:

​
Embed with private embedding

The embed URL for Analytics Chat is always the same:
Users will be prompted to sign in with their Cube credentials when accessing the embedded chat. See Private embedding for details on the auth model.

​
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:
See Signed embedding for the full session generation flow, API key setup, and a complete working example.

​
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.
These hide chrome only. Whether the session may use AI at all is decided when you generate it (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: