Qlik

Overview

Qlik is an enterprise business intelligence and data analytics platform that enables organizations to embed interactive dashboards, charts, and data visualizations on internal portals, customer-facing applications, and partner sites. When detected on a website, Qlik's embedded analytics components are rendering interactive data visualizations that users can explore — filtering data, drilling into details, and viewing real-time metrics. The platform supports both Qlik Sense (modern, web-based) and QlikView (classic) deployment models.

What This Script Does

Qlik embeds interactive analytics dashboards on websites through its embedded analytics capabilities.

• Dashboard embeds: Interactive visualizations load via iframe from the organization's Qlik Sense server or Qlik Cloud, rendering charts, tables, maps, and KPI tiles that users can interact with
• Mashup API: For tighter integration, the Qlik Sense Mashup API loads JavaScript from the Qlik server, enabling developers to embed individual chart objects and handle events within the host page
• Scripts loaded: Dashboard embeds load from the organization's Qlik deployment (self-hosted or {tenant}.qlikcloud.com). The Capability APIs and Nebula.js libraries render visualization objects.
• Cookies set: Session cookies for maintaining the dashboard's filter state, user selections, and authentication context. These are scoped to the Qlik server's domain.
• Data collected: User interactions with the dashboard — filter selections, drill-down paths, bookmark actions, and export events. This interaction telemetry serves analytics on how the dashboard is used, not marketing.
• Authentication: Embedded dashboards may require user authentication through the host application's SSO integration with Qlik, using tokens or session cookies for access control.

Consent & Compliance

Qlik falls under the analytics consent category.

Under GDPR and ePrivacy, embedded Qlik dashboards serve an analytics and reporting purpose. Session cookies maintaining dashboard state and authentication are functional for the requested data visualization service. The interaction telemetry (filter selections, drill-down activity) constitutes usage analytics, but this is typically internal product analytics rather than advertising-oriented tracking. The ePrivacy assessment depends on whether the cookies serve the user's explicit request (viewing the dashboard) or additional analytics purposes.

Under CCPA/CPRA, dashboard interaction data and any personally identifiable data displayed within the visualizations constitute personal information governed by the organization's data practices.

Should You Block This Without Consent?

Yes. While Qlik dashboards serve a functional data visualization purpose, the analytics classification means they should be managed under analytics consent for consistency. The dashboard interaction tracking goes beyond strictly necessary session management. For internal-facing dashboards accessed by authenticated users, the authentication flow itself may serve as the consent mechanism. For public-facing embedded dashboards, gate the Qlik embed behind analytics consent.