Tableau Data Lineage: Column-Level, From the Warehouse Out to the Workbook
Tableau Catalog does genuine field-level lineage inside Tableau, if you pay for the Data Management add-on. The moment the trail leaves Tableau, into the dbt models and warehouse tables that built the data, it goes dark. Datatrail reads the warehouse read-only and maps that upstream path at column level.
Read-only connection. Datatrail never moves or mutates your data.
In short
Tableau's data lineage comes from Tableau Catalog, part of the paid Data Management add-on for Tableau Server and Tableau Cloud. It provides column-level lineage: pick a field or a column and Catalog shows the upstream databases and tables it came from and the downstream workbooks, sheets, and dashboards that depend on it, with impact analysis and the ability to email the affected authors. Its limits are that it requires the Data Management license, it is anchored to Tableau content, and connections that use custom SQL break its column lineage. Datatrail connects to the warehouse read-only and parses query history into column-level lineage that covers the full path from the raw source through dbt out to Tableau, in one graph that also spans your other BI tools.
Why it fits
Tableau teams who need column-level lineage through the warehouse and dbt behind their data sources, beyond what Catalog maps.
Catalog is column-level but Tableau-scoped
Tableau Catalog does real field-level lineage, upstream to tables and downstream to workbooks, but it needs the Data Management add-on and is anchored to what Tableau itself connects to.
Covers the transformations before Tableau
Datatrail traces the column from the raw warehouse table through every dbt model to the Tableau data source, the stretch of the path Catalog treats as one opaque upstream table.
One graph across every BI tool
If you run Tableau alongside Power BI or Looker, Datatrail maps them all from the shared warehouse layer instead of leaving you one lineage silo per tool.
How Tableau Catalog builds lineage
Tableau's lineage is a feature of Tableau Catalog, which ships as part of the Data Management add-on for Tableau Server and Tableau Cloud. It is a paid license on top of Tableau itself, and without it you do not get this lineage. With it enabled, Catalog indexes the databases, tables, and columns your Tableau data sources connect to and links them to the Tableau content built on top.
The useful part is that it is genuinely column-level. Select a field in a data source or a column in a table and Catalog filters the lineage to show only the upstream inputs that feed that field and the downstream assets that depend on it: the workbooks, sheets, and dashboards. That makes real impact analysis possible inside Tableau. Before you change or retire a column, you can see which workbooks would be affected and email the impacted authors directly from Catalog. For a shop where Tableau is the BI layer and Data Management is already licensed, this is a strong, tightly integrated feature and worth turning on.
Where Tableau Catalog's lineage stops
Catalog is excellent at what it is scoped to, and the scope is the limit.
It is anchored to Tableau. Catalog's world starts at the tables your Tableau data sources connect to. It can show that a table is upstream of a workbook, but the transformations that built that table, the dbt models, the staging and intermediate layers, the raw source it all came from, live in the warehouse, outside Tableau, and Catalog does not map them. When a number on a dashboard is wrong because a join changed three models upstream in dbt, the Tableau lineage points you at the final table and stops.
Custom SQL breaks column lineage. This is a documented gap: when a connection uses custom SQL, the lineage may be incomplete, and Catalog does not show column information for tables it only knows about through that custom SQL. Teams that lean on custom SQL data sources, which is common, end up with holes exactly where the logic is most complex.
It is one tool's view. Catalog maps Tableau content. If part of your reporting is in Power BI or Looker, that work is invisible to Tableau Catalog, so you get a lineage silo per BI tool rather than one picture of how the warehouse feeds all of them.
How Datatrail complements Tableau Catalog
Datatrail works from the warehouse rather than from Tableau. It connects to Snowflake, BigQuery, Redshift, Databricks, or Postgres with a read-only role and parses the query history the warehouse already records into a persistent column-level lineage graph. Because it reads the SQL that actually executed, it maps the whole upstream path Catalog treats as an opaque source: every dbt model, every intermediate table, back to the raw column, including the custom-SQL logic Catalog cannot resolve.
That upstream graph is where before-you-ship impact analysis comes from. Change or drop a warehouse column and Datatrail names every downstream dbt model and, through your BI connection, the Tableau data sources and workbooks that read it, so you fix the root cause on purpose instead of triaging a broken dashboard after the fact. The dbt lineage lines up with your project graph, and if you run more than one BI tool the same warehouse graph covers Power BI lineage too.
The two are complementary. Keep Tableau Catalog for field-level lineage and author notifications inside Tableau. Use Datatrail for the warehouse-to-workbook path at column level, across every BI tool, without a per-tool add-on. The wider landscape is in our comparison of data lineage tools.
Questions people ask
Tableau lineage, answered
Does Tableau have data lineage?
Yes, through Tableau Catalog, which is part of the Data Management add-on for Tableau Server and Tableau Cloud. Catalog maps the databases, tables, and columns your Tableau data sources connect to and links them to the workbooks, sheets, and dashboards built on top, with impact analysis and author notifications. It is a real, column-level lineage feature, but it requires the paid Data Management license and it is scoped to Tableau content.
Is Tableau lineage column-level?
Yes, when you have Tableau Catalog through Data Management. Select a field or a column and Catalog shows the upstream inputs that feed it and the downstream workbooks and dashboards that depend on it. The main exception is custom SQL: for connections that use custom SQL, Catalog does not show column information for the tables it only knows through that SQL, so column lineage is incomplete there.
Do you need Data Management for Tableau lineage?
Yes. Tableau Catalog, which provides the lineage and impact analysis, is included in the Data Management add-on, a paid license on top of Tableau Server or Tableau Cloud. Without Data Management you do not get Catalog lineage. If you want lineage without adding that license, or you want to map the warehouse and dbt transformations upstream of Tableau, a warehouse-native tool that connects read-only is the usual route.
Why is my Tableau lineage incomplete?
The most common cause is custom SQL. Tableau Catalog documents that when a connection uses custom SQL, the lineage may be incomplete and it will not show column information for tables it only knows about through that custom SQL. The other gap is scope: Catalog maps what Tableau connects to, so the dbt models and warehouse transformations that produced your tables sit upstream of its view and do not appear.
How do I trace Tableau data back to the warehouse?
Map it from the warehouse side. A warehouse-native tool like Datatrail connects read-only, parses query history into column-level lineage, and follows each column from its raw source table through the dbt models to the table your Tableau data source reads. That covers the upstream path Tableau Catalog treats as an opaque source, including custom-SQL logic, and gives you before-you-ship impact analysis on warehouse changes that would otherwise surface as a broken workbook.
More use cases
Related features
Map your lineage, end to end
Connect your warehouse read-only and see your lineage map in minutes. Datatrail never moves or mutates your data.