Overview
Tableau is a data visualization platform owned by Salesforce, widely used for creating interactive dashboards and analytical reports. On websites, Tableau's embedded views allow organizations to publish interactive charts, maps, and data explorations on public pages, investor relations portals, and internal dashboards. Tableau Public, the free tier, is commonly used to embed data journalism visualizations and open data explorations on media and government websites.
What This Script Does
Tableau's embedded views load scripts from public.tableau.com or a customer's Tableau Server/Cloud instance. The scripts render interactive data visualizations within an iframe or JavaScript API integration, supporting user interactions such as filtering, drilling down, hovering for tooltips, and selecting data points. Cookies set by Tableau include session identifiers for maintaining visualization state, user preference cookies for persisting filter selections, and workbook cache identifiers. The JSESSIONID cookie manages the server-side session. Tableau's usage analytics module tracks user interaction events within the visualization — filter changes, view selections, dashboard tab switches, and time spent on each view — transmitting this telemetry to the Tableau platform for usage reporting.
Consent & Compliance
Tableau scripts span analytics and functional categories. The interactive visualization itself serves a functional purpose — it is the content the visitor came to see. However, the interaction tracking and usage analytics layer collects behavioral data about how visitors engage with the visualization, which constitutes analytics processing. Under GDPR, the analytics telemetry requires a legal basis. For public-facing embedded views, consent is the appropriate mechanism. The ePrivacy Directive requires consent for non-essential cookies; the session cookie for rendering the visualization may qualify as strictly necessary, but usage tracking cookies do not. Under CCPA/CPRA, the interaction tracking data must be disclosed, and consumers must have access and deletion rights.
Should You Block This Without Consent?
Conditional. If the Tableau visualization is the primary content of the page (e.g., a public data dashboard), blocking it would remove the page's purpose. In this case, the visualization rendering should be allowed, but the analytics and usage tracking layer should be suppressed if possible. For supplementary visualizations on content pages, the entire embed can be blocked until consent is provided. Evaluate whether Tableau's embedding API supports a mode that disables usage telemetry while preserving interactive functionality.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
tableau.comAnalyticsFrequently Asked Questions
Does Tableau require consent?
Conditionally. The visualization itself serves a functional purpose, and the session cookie for rendering may qualify as strictly necessary. However, Tableau's usage tracking layer — filter interactions, time-on-view, dashboard tab switches — is analytics data collection requiring consent before that telemetry activates.
What cookies does Tableau set?
Tableau sets JSESSIONID to manage the server-side visualization session, user preference cookies for persisting filter selections, and workbook cache identifiers. The usage analytics module transmits interaction events — filter changes, drill-downs, view switches, and time-on-view metrics — back to the Tableau platform for usage reporting.
How does ConsentStack handle Tableau?
ConsentStack can split Tableau into functional (visualization rendering) and analytics (usage telemetry) layers. The embedded dashboard loads freely while ConsentStack gates the interaction tracking behind analytics consent. This preserves the data visualization experience without activating usage telemetry until the visitor agrees.
Related Vendors
Manage consent for Tableau
ConsentStack automatically detects and manages Tableau trackers so your site stays compliant with global privacy regulations.