Embed analytics

Embedding analytics can mean many things, in this section you'll find information about the various ways you can embed the Qlik platform in external solutions.

Embed Qlik Sense client visualizations as-is

The easiest way, and by far the most common, is to simply embed a visualization from a client sheet onto a website. This enables you to quickly share a visualization with other users in your tenant. Note that this requires anyone that accesses the embedded visualization to be signed in to your tenant, and that the app the visualization belongs to is accessible by that user, otherwise the visualization can't render.

To start using this capability, simply head over to a sheet, right click a visualization, and choose "Embed chart" from the context menu.

Embed Qlik Sense client visualizations using Capability APIs

A more flexible approach to embedding analytics is to use the Capability API. This API allows you to create web solutions using the web technology stack from the Qlik Sense client. It allows for a lot more customization than the embed chart option, and is also the recommended way if you plan on embedding multiple visualizations from the Qlik Sense client on an external website.

Embed analytics using the enigma.js library

A more barebones option is to use the enigma.js library. This gives you complete control in your web or backend solution and allows you to interact with the Qlik Associative Engine in a more raw manner compared to the previous options.

This allows you to build complete custom analytics solutions, from presenting simple KPIs to creating advanced visualizations using nebula.js. Note that this option has limited capabilities when it comes to reusing Qlik Sense client visualizations.

Other ways of embedding analytics

This option can be used if you have other needs than what's covered in the other options. If you want to interact with the Qlik Associative Engine using Golang, you may use the enigma-go library to do so. If you'd like to work with the Qlik Associative Engine in its most raw form, which means handling websocket connections and the JSON-RPC traffic, you'll find these concepts described under the JSON-RPC API section.

Was this page helpful?