Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

Google AI - Gemini analytics source

Use the Google AI - Gemini analytics connector to communicate with large language models (LLMs) that are available from Google's Gemini API, enriching your Qlik Sense apps with contextual and analytical depth.

With the Google AI - Gemini analytics connector, you can send data from app consumer input, or from data loaded in your script, to Gemini. You can connect to this analytics source from the Create page in the Analytics activity center, the Script, or within an app.

Prerequisites

To work with this connector, you must be a Google AI Studio user with access to the Gemini API.

Enabling ML endpoints in Qlik Cloud

To work with this connector, machine learning endpoints must be enabled in the Administration activity center. The switch is located under Feature control in the Settings section.

For more information, see Enabling analytic connections for machine learning endpoints.

Limitations

  • This connector has a request limit of 25 rows per request, with a maximum batch size of one row being sent at a time.

  • The resources available on the services where the model has been deployed will impact and limit performance in the Qlik Sense reload and chart responsiveness.

  • In a scenario where an application is regularly reloaded, it is best practice to cache the machine learning predictions using a QVD file and only send the new rows to the endpoint. This will improve the performance of the Qlik Sense application reload and reduce the load on the model endpoint.

  • If you are using a relative connection name, and if you decide to move your app from a shared space to another shared space, or if you move your app from a shared space to your private space, then it will take some time for the analytic connection to be updated to reflect the new space location.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!