Embedding Conversational Analytics

Preview

This product or feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA products and features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

You can embed Conversational Analytics in a website or an application using an HTML iframe tag just as you can with other Looker content types. Conversational Analytics supports both private embedding, where users are authenticated using their Looker login, and signed embedding, where users are authenticated through your own application.

This page describes how to embed Conversational Analytics into an iframe.

Learn how and when Gemini for Google Cloud uses your data.

As an early-stage technology, Gemini for Google Cloud products can generate output that seems plausible but is factually incorrect. We recommend that you validate all output from Gemini for Google Cloud products before you use it. For more information, see Gemini for Google Cloud and responsible AI.

Before you begin

To embed Conversational Analytics, keep in mind the following requirements and limitations:

• To embed Conversational Analytics, your instance must be on Looker 26.2 or later.
• Your Looker admin must enable the Embed Conversational Analytics Labs feature.
• Users will need the same permissions that are required to use non-embedded Conversational Analytics.
• During the preview, there are the following additional limitations:
  • Embedding Conversational Analytics is supported only on Looker (original). Looker (Google Cloud core) is not supported.
  • Embedded themes are not supported.
  • The Embed SDK is not supported for signed embedding of Conversational Analytics.

Creating the Conversational Analytics embed URL

The process to create an embed URL for Conversational Analytics is the same as for embedding other content types, such as dashboards or Looks, where you add /embed/ after the instance name and before the content folder and content ID.

For Conversational Analytics, find the non-embedded URL of the conversation or agent, and add /embed/ before the conversations or agents folder. For example:

• For the conversations page, the embed URL will look like https://my_looker_instance.looker.com/embed/conversations.
• For the agents page, the embed URL will look like https://my_looker_instance.looker.com/embed/agents.
• For a specific conversation, the embed URL will look like https://my_looker_instance.looker.com/embed/conversations/c9f370ac830b4669aeb494396422004c. In this example, c9f370ac830b4669aeb494396422004c is the conversation ID.

Private embedding of Conversational Analytics

For private embedding, create an iframe and use the Conversational Analytics embed URL as your iframe source, as shown in the following example:

  <iframe
      src="https://my_looker_instance.looker.com/embed/conversations/c9f370ac830b4669aeb494396422004c"
      width="1000"
      height="2000"
      frameborder="0">
  </iframe>

Then embed the iframe in your web page or application.

Signed embedding of Conversational Analytics

The process for signed embedding of Conversational Analytics is the same as for other content types. Use the Conversational Analytics embed URL when coding the signed embed URL.

Note: For the preview, the Embed SDK is not supported, so the signed embed URL must be manually coded.

Embed users will need the proper permissions to use Conversational Analytics, such as chat_with_explore. As a result, you will have to add those permissions to the signed embed URL.