> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dqlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Tableau Overview

> Connect Prizm to Tableau Cloud or Tableau Server to ingest workbook metadata, track lineage, monitor freshness, and surface data quality signals directly in Tableau.

<script type="application/ld+json">
  {`{
            "@context": "https://schema.org",
            "@type": "TechArticle",
            "headline": "Tableau Overview",
            "description": "Connect Prizm to Tableau Cloud or Tableau Server to ingest workbook metadata, track lineage, monitor freshness, and surface data quality signals directly in Tableau.",
            "url": "https://docs.dqlabs.ai/sources/tableau/overview",
            "publisher": {
              "@type": "Organization",
              "name": "DQLabs Inc",
              "logo": "https://media.brand.dev/332adc35-5bc4-4d2b-bf78-256aa4a5e414.svg"
            }
            }`}
</script>

The Tableau integration enables Prizm to connect to Tableau Cloud or Tableau Server as a downstream consumer of your data. Unlike database connectors, Tableau is a **BI/pipeline integration** — Prizm ingests Tableau metadata to extend lineage from warehouse tables through to workbooks, worksheets, and dashboards, and propagates quality scores, alerts, and issues downstream to the reports that depend on your data.

## What Prizm Connects To

Prizm supports both Tableau deployment types:

| Deployment         | Details                                                                                  |
| :----------------- | :--------------------------------------------------------------------------------------- |
| **Tableau Cloud**  | All regions; Connected Apps (OAuth) recommended                                          |
| **Tableau Server** | Version 2023.3 or later recommended for Connected Apps; older versions supported via PAT |

## Supported Tableau Objects

Prizm ingests the following object types from Tableau. The hierarchy reflects how objects are organized in Tableau:

```text theme={null}
Site
 └── Project
      ├── Workbook
      │    ├── Dashboard
      │    └── Worksheet
      └── Published Data Source
           └── Field / Calculated Field
```

| Object                    | What Prizm Captures                                                                        |
| :------------------------ | :----------------------------------------------------------------------------------------- |
| **Site**                  | Name, site ID                                                                              |
| **Project**               | Name, description, owner, hierarchy, created/updated timestamps                            |
| **Workbook**              | Name, description, owner, URL, project hierarchy, created/updated timestamps               |
| **Dashboard**             | Name, owner, URL, project hierarchy, created/updated timestamps                            |
| **Worksheet**             | Name, URL, project hierarchy, created/updated timestamps                                   |
| **Published Data Source** | Name, description, owner, upstream tables/databases, certification status, extract details |
| **Datasource Field**      | Name, description, data type, role (dimension/measure), formula, upstream columns          |
| **Calculated Field**      | Name, description, data type, role, formula expression                                     |

<Note>
  Tableau Metrics (the native Tableau Metrics feature) are deprecated in Tableau and are not ingested by Prizm.
</Note>

## Observability Metrics

Prizm computes the following out-of-the-box metrics for Tableau assets:

<Tabs>
  <Tab title="Operational">
    | Metric                   | Level                 | Description                                                                                                                                                                                                          |
    | :----------------------- | :-------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
    | **Freshness**            | Data Source, Workbook | Time elapsed since the last successful extract refresh. Calculated from `last_successful_refresh_time` via the Extract Refresh Tasks API. Dynamic threshold = expected refresh interval ± 3× average execution time. |
    | **Refresh Duration**     | Data Source           | Time taken to complete each extract refresh job                                                                                                                                                                      |
    | **Consecutive Failures** | Data Source           | Number of consecutive failed refresh jobs                                                                                                                                                                            |
    | **Refresh Success Rate** | Data Source           | % of refresh jobs completed successfully over the monitoring window                                                                                                                                                  |

    <Info>
      Freshness alerts are time-sensitive. The Operational/Refresh job runs **hourly** so SLA breaches surface quickly.
    </Info>
  </Tab>

  <Tab title="Performance">
    | Metric                          | Level          | Description                                                                                               |
    | :------------------------------ | :------------- | :-------------------------------------------------------------------------------------------------------- |
    | **Hits (last 14 days)**         | Workbook, View | Number of views in the last 14 days                                                                       |
    | **Hits (last 30 days)**         | Workbook, View | Number of views in the last 30 days                                                                       |
    | **Hits (last 90 days)**         | Workbook, View | Number of views in the last 90 days                                                                       |
    | **Hits (last 365 days)**        | Workbook, View | Number of views in the last 365 days                                                                      |
    | **Daily Active Users**          | Workbook       | Distinct users viewing the workbook per day                                                               |
    | **Usage-Weighted Health Score** | Workbook       | Quality score weighted by usage frequency — high-traffic workbooks with quality issues are surfaced first |

    Usage metrics feed **zombie dashboard detection** — workbooks with no views in 90+ days can be automatically flagged for deprecation review.
  </Tab>
</Tabs>

## Quality Propagation

Prizm can propagate data quality signals from upstream warehouse tables to the Tableau workbooks and dashboards that consume them. This is configured per connector at setup time.

| Signal     | Propagation Options                |
| :--------- | :--------------------------------- |
| **Score**  | Based on associated table, or none |
| **Alerts** | Based on associated table, or none |
| **Issues** | Based on associated table, or none |

When propagation is enabled, a quality issue on a Snowflake or Databricks table automatically surfaces on every Tableau workbook that queries that table — giving report consumers visibility into upstream data health without leaving Tableau.

## Data Quality Warnings

<Note>
  Data Quality Warnings require **Tableau Enterprise** (Server or Cloud), **Tableau+** (Cloud), or the **Data Management add-on** purchased prior to September 16, 2024. Tableau Catalog must also be enabled.
</Note>

When a quality alert fires on an upstream table, Prizm can push a **Tableau Data Quality Warning** to the affected Tableau Data Sources. Warnings:

* Appear on Tableau Data Sources and are overlaid on views consuming those sources
* Are editable directly in Tableau
* Automatically expire approximately **24 hours** after being set or updated
* Apply only to **Tableau Data Sources** — not to Workbooks or Views directly

To apply a warning, navigate to the affected table asset in Prizm → **Downstream Reports** → click the downstream report count → apply the warning.

## Chrome Extension

Prizm provides a Chrome Extension for Tableau that surfaces quality context without leaving Tableau. Once installed, the extension shows — for any open Tableau report:

* Associated Prizm asset
* Number of active issues and alerts
* Current quality score
* Alert and issue detail summaries
* Link to open the asset in Prizm

## Supported Features

| Feature                                | Supported                                  |
| :------------------------------------- | :----------------------------------------- |
| Tableau Cloud                          | ✅                                          |
| Tableau Server                         | ✅ (2023.3+ recommended)                    |
| Connected Apps (OAuth)                 | ✅ Recommended                              |
| Personal Access Token                  | ✅                                          |
| Username / Password                    | ✅                                          |
| Workbook / Dashboard ingestion         | ✅                                          |
| Datasource field lineage               | ✅                                          |
| Freshness monitoring                   | ✅                                          |
| Usage analytics                        | ✅                                          |
| Quality score propagation              | ✅                                          |
| Data Quality Warnings                  | ✅ (Enterprise / Data Mgmt add-on required) |
| Chrome Extension                       | ✅                                          |
| Authoring or modifying Tableau content | ❌ Out of scope                             |
| Running or refreshing Tableau extracts | ❌ Out of scope                             |

## Next Steps

<CardGroup cols={2}>
  <Card title="Setup" icon="plug" href="/integrations/tableau/setup">
    Connect Prizm to Tableau Cloud or Server — step-by-step authentication and configuration.
  </Card>

  <Card title="What We Collect" icon="database" href="/integrations/tableau/what-we-collect">
    Full breakdown of every job, object, and field Prizm ingests from Tableau.
  </Card>

  <Card title="FAQ" icon="circle-question" href="/integrations/tableau/faq">
    Common questions about authentication, scoping, lineage, and propagation.
  </Card>

  <Card title="Glossary" icon="book" href="/help/glossary">
    Definitions for Prizm terms used throughout this guide.
  </Card>
</CardGroup>