Matia Now Connects to Omni: Full Column-Level Lineage From Source to Dashboard

Today, Matia is launching a new integration with Omni, an AI analytics platform, to bring end-to-end visibility from the data source through your warehouse and into every Omni document, dashboard, visualization, and field.

Most data teams can tell you where a dashboard lives. Far fewer can tell you, in one click, exactly where the numbers in that dashboard came from and what downstream impacts are in the same interface. The journey from a source system through the warehouse and into a business-facing chart usually spans several tools, and the lineage breaks somewhere in the handoffs.

Today we are closing that gap. Matia's Catalog now connects to Omni so you can trace any visualization back through your warehouse to the original source. This provides visibility into where numbers come from to help build trust.

Omni: The last mile of your data stack

Omni sits between the rest of the data stack and the stakeholders they serve. Data flows from sources into a warehouse like Snowflake or BigQuery, gets modeled and transformed, and then gets surfaced in Omni so business teams can act on it. Stakeholders rarely understand the full pipeline, but building trust means giving them visibility into where numbers came from and how they were transformed along the way.

That question gets sharper as teams put AI on top of the analytics layer. When users ask questions with AI, you need governance and traceability to build trust. Omni's built-in semantic layer ensures context and governance, and Matia's connector makes it traceable.

Because Matia already unifies ETL, reverse ETL, observability, and catalog in one platform, connecting Omni completes the picture. You can now follow data all the way from the point it enters your stack to the visualization a stakeholder is looking at, without stitching together separate tools to do it.

‍

What you get with the Omni and Matia integration

Full asset visibility. Once you connect Omni, the Catalog surfaces the entire hierarchy: folders, documents, workbooks, visualizations, and query fields. Your BI assets become as discoverable and governed as the rest of your stack.

Column-level lineage from source to BI. This is the core of it. Lineage runs source to warehouse to BI, so you can trace a single column from an Omni visualization back through the Omni models, a Snowflake data mart, back through the staging tables, and all the way to where it originated. In practice that origin might be a Salesforce integration, a sessions table in MongoDB, a user feedback report in Google Sheets, or a financials table in your warehouse. You can also start from the data store and go forward to see every Omni asset a given source feeds.

Full SQL coverage. Lineage works whether a workbook was built with standard queries or with user-edited SQL, so there are no gaps in coverage. Mapping holds up against the way real teams actually build in Omni.

Complete lineage across the whole stack

Most lineage tools draw a single line: this dashboard, back to that source. Matia and Omni together map the full web of dependencies across your stack, so you can see everything an asset touches in both directions.

Trace in both directions. Start from an Omni visualization and work backward to the source, or start from a source or warehouse table and work forward to every Omni asset it feeds. The same view works either way, so you can answer "where did this come from" and "what breaks if I change this" from the same place.

Surface indirect relationships. A single visualization is often fed by more than one path. Matia shows the full set, including a second data mart or a separate Google Sheet feeding the same Omni asset, so dependencies that normally live in someone's memory become visible in the platform.

Lineage that accounts for observability. Because catalog and observability sit in the same platform, column-level lineage carries anomaly detection along the path. You are not just seeing how data connects, you are seeing where it is at risk.

This is what full end-to-end lineage is supposed to mean. Without a unified platform underneath, the trail keeps breaking at the seams between tools. Matia traces the journey across ingestion, the warehouse, and back out to BI in a single click. That matters more as AI moves into the analytics layer. When an AI tool answers a question off your Omni data, Matia is the foundational infrastructure that put the data there, monitored it for anomalies, and lets you follow that answer back through every step to the source.

How teams are already using it

David Protein, which runs its stack on BigQuery, is an early user of the Omni integration.

"Seeing the lineage connect end to end means when something breaks, we trace it in one place instead of digging across tools. Less complexity, faster debugging, pipelines that are easier to maintain. The Matia and Omni integration ties it together, from the data moving through to the dashboards and semantic layer we build on top of it."

Ari Azbel, Senior Data Analytics Engineer, David Protein

Now available

The Omni integration is available now. If you are already on Matia, connect your Omni workspace from the catalog and your assets will start surfacing automatically, with lineage mapped back through your stack.

View the omni docs

To learn more about Omni’s AI analytics platform, visit Omni.co