Data lineage maps the journey of your data from origin to destination. It visually shows where data comes from, how it's transformed, and where it's used.
In depth
Data lineage gives you a complete picture of your data's lifecycle, so you can answer "where did this number come from?" before you act on it. It starts at the source, such as spreadsheets, services, or databases, and continues as the data is retrieved, modelled, and visualized. Your team can see exactly how raw values become the numbers in your dashboards and reporting.
On a technical level, data lineage captures metadata about each process that touches your data. It records transformation rules, joins, filters, calculations, and movement between systems. Whether data moves manually or automatically, through ETL pipelines and API connectors, lineage keeps a log of every change.
Lineage falls into two types:
- Business lineage: shows high-level flows, such as which metrics depend on which data sources.
- Technical lineage: drills into the code or formulas behind each step.
As data environments grow, tracking lineage by hand becomes error-prone. Automated tools collect metadata, visualize complex networks, and flag potential issues. They keep your lineage accurate as new sources and transformations are added.
Pro tip
Document key data transformation steps as you build your reporting. A record of how raw data is cleaned, joined, or aggregated can save hours when you need to trace an unexpected number.
Why data lineage matters
Builds trust in your numbers: When your team can see exactly how a number is calculated, everyone works from the same answer.
Speeds up troubleshooting: Follow the lineage trail to find where an error started, instead of guessing which process broke.
Supports compliance: Auditors and regulators often require proof of data origin and handling. Lineage provides a clear audit trail.
Reduces waiting: Business users can check where a number came from without waiting on IT, so decisions move faster.
Data lineage in practice
Imagine your marketing team notices a sudden drop in customer sign-ups. Before changing the campaign, they trace the number back and find that a recent change in the CRM schema broke a field mapping. They fix the mapping, refresh the data, and restore accurate numbers without scripting or lengthy tickets.
Or consider a finance team that needs to verify the source of quarterly revenue before closing the books. Lineage lets them review each transformation step, confirm the right exchange rate was applied, and sign off on reports with confidence.
What to look for in data lineage
Good lineage keeps the answer to "where did this number come from?" close to the number itself. Look for these details on every metric you rely on:
- Source: which tool, spreadsheet, or database the data comes from.
- Refresh status: the refresh schedule, any errors, and the last updated time.
- Transformations: the modelling steps and calculations applied between raw data and the final number.
With these in view, leaders can trust that dashboards are accurate, audit-ready, and built on consistent definitions.
Related terms
What is a dimension?
A dimension is a descriptive attribute that provides context for your metrics. Dimensions are the categories or labels, like date, region, or product line, that you use to group, filter, or slice your data.
What is a knowledge graph?
A knowledge graph is a structured network that represents real-world entities (people, places, products, metrics) and the relationships between them. It adds context to data, so leaders and systems can make better-grounded decisions. This entry explains how knowledge graphs work, why they matter, where they are used, and what to consider before building one.
What is data quality?
Data quality measures the reliability of your data for making decisions. High-quality data is accurate, complete, timely, consistent across systems, valid, and free of duplication. When leaders trust the numbers, meetings move from debating whose number is right to deciding what to do next.